[Feature Request] Relation Management #1807
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1807
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Solution 2; Dropdown
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.
Yeah I think that would make sense. Do you want to send a PR?
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 🙂
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.
I can try this eve, shouldn't be too big of a problem. :)
That does make sense
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.
@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.
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 :)
Resolved in vikunja/frontend#923. Please test with a new unstable build or on try once the CI released it (in ~30min).