Add context info to Tasks shown from Deck cards.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start in the Tasks UI where Deck task lists and task controls are displayed, and inspect the existing tooltips for the list name, disabled checkbox, and star action. Done means a clear read-only explanation is shown for Deck tasks in one of these locations, without implying that the controls can be used.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
TLDR: need tooltip to explain that tasks from the Deck app are read only in Tasks app
I installed Tasks as a recommended app and was curious how it integrated with Deck. Tasks was then populated with tasks from the boards in Deck. All very nice. But I could not understand what I had had done wrong since I couldn't edit any of the tasks. As I was helpfully told on the forum - that's by design. Okay, fine. But there's no way for a new user to know that's by design through the UI, and it's not at all obvious in terms of functionality.
Describe the solution you'd like
So my feature request is to add a little more information in the UI. For example:
In the list of task lists the current tool-tip has the name of the boards from Deck that have tasks. Perhaps add to this tool-tip the text "Tasks from Deck are read only"
Describe alternatives you've considered
Two other possible places to add this info:
- The check box for a task from Deck is greyed out. This was the first thing I noticed and tried to click on. Perhaps add a tool-tip text "Tasks from Deck are read only"
- Add a tool-tip when hovering over the star to the right of a Deck task. At the moment it says "Toggle Starred" (which is not possible). Make the text "Tasks from Deck are read only"
Those are my suggestions. Any one of those three would have cleared this up for me in the first minute of using the Tasks app.
Additional context
No response
- Dominant language
- JavaScript
- Stars
- 710
- Forks
- 125
- Avg merge
- 19h 37m
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nextcloud/tasks
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nextcloud/tasks#3240 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nextcloud/tasks#3111 · 1 comment ·
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nextcloud/tasks#122 · 9 comments · 25 reactions ·
Maintainers usually reply within 1 day
-
1. to develop
Difficulty 5/5 Over a week Newbie friendliness 39/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
remotion-dev/remotion#13341 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
svix/svix-webhooks#2808 ·
Maintainers usually reply within 1 day
-
enhancement should-have ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100