[Feature request] New due-date time entry is slow
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 50/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- frontend
Research direction
No file or test is named. Start by locating the due-date time-entry UI and checking how its current input handles separators and scrolling. Done means users can enter times such as 1230 without typing a colon, with the resulting due time preserved correctly; wheel scrolling is an additional requested improvement.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
The new time entry which came in version 0.17 is in my opinion an usability regression.
When creating a new tasks, before I could set time by clicking on pulldown, scrolling to time I wanted using mouse wheel and clicking again. This was far from ideal, but significantly better than current state.
When I want to schedule task for 12:00, I need to click once to display the new GUI and then 12 times to get to 12:00. It would be even worse if I wanted to select 12:30.
Describe the solution you'd like
Previous version was better, because the current one is just slow.
What would improve things significantly would be if the new GUI reacted to wheel scrolling, which would make it much faster.
But the best and fastest way is in my honest opinion how Google calendar does it. If I want to schedule something for 12:30, I just type 1230. This is super fast and comfortable. I believe this can be added easily to the existing solution.
Current solution allows for typing the time, which I use often and frankly is the only viable way in 0.17 for me, but the problem is that I MUST type the ":". That makes it significantly slower and annoying.
Describe alternatives you've considered
Described above.
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