[Feature Request] Relation Management #588

Open
opened 3 weeks ago by Gensokian · 5 comments

I have some small ideas for the relation management;

Firstly some more clarity what namespace the search results come from, it's quite hard if you have 5 Namespaces with simmilar lists and simmilar tasks in them to catch the right one.

adding a [NAMESPACE] > [LIST] > [TASK] to the dropdown would solve that issue

Also maybe add some sort of "Scope" to the search, hiding any non-relevant tasks

Solution 1; Radio buttons
image
Solution 2; Dropdown
image

Thirdly I noticed that "Duplicate of" and "Duplicates" doesn't actually "Duplicate". Something I'd love to see is, that if the "Duplicates" relation is given to a task, the "subtask" updates anything that was updated on the "Master Task". This would allow for a "Master tasklist" in which all tasks are copying down any changes to the relevant tasks in their lists.

I have some small ideas for the relation management; Firstly some more clarity what namespace the search results come from, it's quite hard if you have 5 Namespaces with simmilar lists and simmilar tasks in them to catch the right one. adding a **[NAMESPACE] >** [LIST] > [TASK] to the dropdown would solve that issue Also maybe add some sort of "Scope" to the search, hiding any non-relevant tasks Solution 1; Radio buttons ![image](/attachments/5432dc33-3a87-4b90-8e11-57949938d2f2) Solution 2; Dropdown ![image](/attachments/a4f1c74f-4813-427c-ae72-a77f52d92be6) Thirdly I noticed that "Duplicate of" and "Duplicates" doesn't actually "Duplicate". Something I'd love to see is, that if the "Duplicates" relation is given to a task, the "subtask" updates anything that was updated on the "Master Task". This would allow for a "Master tasklist" in which all tasks are copying down any changes to the relevant tasks in their lists.
Owner

Firstly some more clarity what namespace the search results come from, it's quite hard if you have 5 Namespaces with simmilar lists and simmilar tasks in them to catch the right one.

adding a [NAMESPACE] > [LIST] > [TASK] to the dropdown would solve that issue

Yeah I think that would make sense. Do you want to send a PR?

Also maybe add some sort of "Scope" to the search, hiding any non-relevant tasks

I think a checkbox "show all tasks" would make most sense in combination with showing the namespace of the task. IMHO a list of radio buttons would take up too much space and if you add another dropdown than you have two dropdowns. That's too many 🙂

Thirdly I noticed that "Duplicate of" and "Duplicates" doesn't actually "Duplicate".

That's intended. The task relation only tells you something about the relation between the tasks. It's not doing any logic related to it.
The duplicate relation is meant for cases where you have tasks that are about the same thing. This can happen if you have a bigger backlog of stuff and then someone adds a new task about the same thing. Usually you don't want to delete the new task but instead make it clear that there is some other task already doing the same thing.

> Firstly some more clarity what namespace the search results come from, it's quite hard if you have 5 Namespaces with simmilar lists and simmilar tasks in them to catch the right one. > adding a [NAMESPACE] > [LIST] > [TASK] to the dropdown would solve that issue Yeah I think that would make sense. Do you want to send a PR? > Also maybe add some sort of "Scope" to the search, hiding any non-relevant tasks I think a checkbox "show all tasks" would make most sense in combination with showing the namespace of the task. IMHO a list of radio buttons would take up too much space and if you add another dropdown than you have two dropdowns. That's too many 🙂 > Thirdly I noticed that "Duplicate of" and "Duplicates" doesn't actually "Duplicate". That's intended. The task relation only tells you something about the relation between the tasks. It's not doing any logic related to it. The duplicate relation is meant for cases where you have tasks that are about the same thing. This can happen if you have a bigger backlog of stuff and then someone adds a new task about the same thing. Usually you don't want to delete the new task but instead make it clear that there is some other task already doing the same thing.
konrad added the
kind/feature
label 3 weeks ago
Poster

Yeah I think that would make sense. Do you want to send a PR?

I can try this eve, shouldn't be too big of a problem. :)

That's intended. The task relation only tells you something about the relation between the tasks. It's not doing any logic related to it.

That does make sense

> Yeah I think that would make sense. Do you want to send a PR? I can try this eve, shouldn't be too big of a problem. :) > That's intended. The task relation only tells you something about the relation between the tasks. It's not doing any logic related to it. That does make sense
Poster

Alright, so I have to announce that "Learning how to vue" after only small programming experience might have been me taking more than I can chew. It's outa be somewhere here.

Alright, so I have to announce that "Learning how to vue" after only small programming experience might have been me taking more than I can chew. It's outa be somewhere [here](https://kolaente.dev/vikunja/frontend/src/commit/f0498fd767a9df1c1f89e21b2a2606377f455a0d/src/components/tasks/partials/relatedTasks.vue#L45).
Owner

@Gensokian Yup, pretty much. That line you highlighted gives you a list object which has a namespace Id. You can then use that to get the namespace title.
I'd reccoment moving that logic to a method and then maybe add some caching to it.

@Gensokian Yup, pretty much. That line you highlighted gives you a list object which has a namespace Id. You can then use that to get the namespace title. I'd reccoment moving that logic to a method and then maybe add some caching to it.
Poster

Just tried that, but it sounds easier than when I actually sit infront of the code. ^^
I think I'll rather support with translating, than with coding :)

Just tried that, but it sounds easier than when I actually sit infront of the code. ^^ I think I'll rather support with translating, than with coding :)
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.