Ambiguity of list name when moving a task #1733

New Issue

Stedos · 2020-06-27T20:42:35Z

Stedos commented

2020-06-27 20:42:35 +00:00

When attempting to move a task to a different list, only the list names are displayed in the search, making it difficult to tell which namespace the task will be moved to.

An example format that would be clearer would be {namespace}/{list}

There could possibly be an option to be able to drag the task into the list you want to move it to, but that's out of the scope of this change.

PS: Thank you for your work on this! Looking forward to the future of this project.

When attempting to move a task to a different list, only the list names are displayed in the search, making it difficult to tell which namespace the task will be moved to. An example format that would be clearer would be `{namespace}/{list}` There could possibly be an option to be able to drag the task into the list you want to move it to, but that's out of the scope of this change. PS: Thank you for your work on this! Looking forward to the future of this project.

a.png

22 KiB

konrad commented

2020-06-27 20:53:25 +00:00

Hey there!

For related tasks in different lists I have adopted the form list > task title, I think we could do something similar here.

Hey there! For related tasks in different lists I have adopted the form `list > task title`, I think we could do something similar here.

👍 1

konrad added the

kind/feature

label 2020-06-27 20:53:30 +00:00

konrad referenced this issue from a commit

2020-06-27 21:13:31 +00:00

Show namespace name in list search field

konrad closed this issue

2020-06-27 21:13:31 +00:00

konrad commented

2020-06-27 21:15:30 +00:00

Implemented in d49cf5635b - I also needed to make a slight adjustment to the api to include the namespace in search results, so make sure to update both.

A release will be ready in something like an hour (pipelines here and here)

Implemented in https://kolaente.dev/vikunja/frontend/commit/d49cf5635b3b869ada5091047814ed7eb5f61887 - I also needed to make a slight adjustment to the api to include the namespace in search results, so make sure to update both. A release will be ready in something like an hour (pipelines [here](https://drone.kolaente.de/vikunja/api/1958) and [here](https://drone.kolaente.de/vikunja/frontend/835))

👍 1 ❤️ 1

konrad referenced this issue from a commit

2024-02-07 14:00:33 +00:00

chore(deps): update dependency happy-dom to v2.51.0 (#1733)

Sign in to join this conversation.