Add task shows "quick add" when grouping by priority
See original GitHub issueWith Todoist v2145 on macOS Monterey (Firefox 101): when grouping by priority, adding a task pressing a
pops up the quick add window, rather than the inline add task view. I would expect it to work as in the regular Todoist (without extension) where it would open the inline add task view per section.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Create task priorities using Planner - Microsoft Support
In Microsoft Planner, you can add priority fields to tasks. With this feature, you can set a task's priority to Urgent, Important, Medium,...
Read more >How to use Tasks in Microsoft Teams (To Do + Planner)
... active or complete tasks 5:58 Filter tasks by date & priority 6:14 Differences with Microsoft To Do 7:14 Add a new list...
Read more >Priority | Obsidian Tasks - GitHub Pages
Tasks can have a priority. In order to specify the priority of a task, you can append one of the “priority signifiers”, shown...
Read more >Considerations for Using Tasks - Salesforce Help
When you use tasks, keep in mind these considerations for creating, updating, delegating, and managing your task items.
Read more >The Google Tasks guide—everything you need to build a ...
Or you can add more details to tasks from their Edit view. Press Shift + Enter when saving a task to see its...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for reporting! Fixed in version 150
@mdbraber Oops, sorry about the long delay on this. Fixed in version 152!
Thanks a bunch for digging into the code. Indeed falling back on
addToSectionContaining(task)
is better. For thewithUniqueClass
thing it should have beengetUniqueClass
. Not sure how that snuck through, I’m guessing it was a refactoring after initial testing…