-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Rework priority handling #1128
Comments
I think it doesn't hurt to support all 10 priority levels specified by RFC 5545, but I don't have a too strong opinion on that. We only use four colors, since more would be hard to memorize and are not very meaningful. One still might like to have a finer priority setting than four. But if the majority of @nextcloud/designers likes to only have four levels I am fine with that. |
Part of my argument is that it's confusing and de facto unstandard, which I consider bad for the user experience if NC Tasks is synced with practically any other task manager. There's also the possibility for both 4 and 10 levels with a "Simplified Editor" toggle. Looking forward to hear what other designers say. :) |
It might help if the colour of the star next to the number would change when the slider is moved. As I move the slider, it'd be nice to know if the result is going to red, yellow or blue. Otherwise, it's kind of a guessing game. |
There was also another idea to change the priority handling in #1166. See my answer in #1166 (comment). Let's please use this issue here for discussing how to proceed with priority settings (since the ideas in #1128 and #1166 are a bit contradictory). |
Thank you @raimund-schluessler for recognizing that these two topics are related and bringing the discussion together. Simplifying useIn #1166 @raimund-schluessler said he think the issues are contradictory - to me they're both about simplifying the priorities interaction both when setting or checking priority levels. I see that I misinterpreted "Easily distinguish between priorities within the same color" as "Easily distinguish priorities", but first suggestions would fit nicely in with my proposal (thus the thumbs up) and the second doesn't interfere. @bgravato's #1166:
I interpret this as "Simplifying setting priority level". My suggestion for 4 levels is partly to avoid the trouble of hitting "5" when dragging the slider or even using keyboard arrows when you want medium, so to me it's a different approach to the same issue. A '+' and '-' system for a 4 level system (10 levels means too many clicks) would simplify this even more so thumbs up for that (at the cost of design and layout, which I didn't consider. Is there a visual design specification or manifest for NextCloud I could check out?). But I understand the general principle behind keeping it clean and why it's not an option.
I though it meant that priorities would correspond with the colours, landing on a 4 level system. Don't ask how I ended up with that, my bad. Still, it's about simplifying how to accurately check priorities - So a 4 level system that corresponds to the star color would "fix" this problem unless one actually needs all 10 level. I'm under the impression that the vast majority of CalDAV-task users only uses 4 levels when considering the de facto standard in most other task managers. @raimund-schluessler's reply in #1166, where he mentions an alternative to the slider:
What a great idea for both a 4 and a 10 level system! 10-level Star-based priority selectorIn the details pane I'd happily use 10 stars over the slider - so that's an improvement. 4-level Star-based priority selectorSame goes for a 4 star system, but it would nice instead of somewhat crowded! Quick AccessSpeaking of quickly setting priority in what is now a more general thread, I suggest changing what happens when one clicks the star in overview - Do away with the rather useless High/No priority toggle, a better function would be if it could open the details pane with the priority selector in focus. Even removing the functionality completely or creating an in-frame popup for properly setting priority is better in my opinion, currently it only adds a half-way functionality that is confusing and draws away attention from the details pane. But what about combining two of the suggestions we've discussed so far, quick access priority settings with stars? 4-level Star-based quick access priority selectorDoesn't look messy and crowded, even though it looks more crowded than the current design. What was the criteria for moving UI elements to sub-menus previously? |
Between 4 and 10 levels I think I prefer 10, but I can live with 4. My suggestion was to try to waste less time setting or adjusting priority levels. Two situations where this come into play on my usual workflow:
On both situations, clicking on a (sub-)task, dragging a slider, etc... and repeating for all tasks is a bit time consuming. It would be great to be able to change the priority directly from the task list, without having to open each task one by one. I too agree that clicking on the star in the task list to toggle between priority 1 or no-priority is a bit useless indeed... I suggested +/- buttons but a popping menu (or something else that allows to set any priority instead of just 1 or nothing) when clicking the star would be much more useful and time-saving. As for visual information on the task list, I agree it should be as simple as possible, but it would be nice to be able to tell the (exact) priority of a task just by looking at the task list. Currently it's impossible to distinguish from 1,2, 3 or 4, for example. Showing a number over the star would not occupy more space and would be more informative in my opinion (though it might be less appealing from a design POV). This is valid only if using a 10-level scale, if switching to a 4-level scale it doesn't make any sense, of course. I'd love to help with the coding, but my javascript skills are quite limited, sorry. |
Forgot to say... I love the idea of replacing the slider with a star-based selector. |
I often use tasks with both sidebars opened and in a 14''/13'' display, so the view is much shorter than what shown above. |
@Torenga Adding numbers will probably help the user under the 9-star view. Here's an example. |
From a user perspective, 10 levels are absolutely too much. Just like @Torenga said:
Sure the RFC is one thing, but we need to remember that RFCs are written by engineers and not by user researchers. While we can follow the RFC in the backend, we don’t need to implement all its nuances in the frontend. Especially not if basically all popular tasks app use way less complicated means – which makes those the de-facto standard, and any app following the RFC just plain confusing and/or complicated. :) References for priority systems in other task apps (short story: none gets more complicated than 4 levels, so we should neither):
|
As a new user switching from another task managing app, I would strongly support the request to simplify overall and the suggestion "4 Start" and "Quick Access" as described by @Torenga above If not showing 4 stars in the "Quick Access" option on the list, maybe a toggle trough the stages (high, medium, low, none) upon click could be an alternative!? |
RFC 5545 specifies 1-4 as High, 5 as Medium and 6-9 as high with 0 as "Undefined/No priority".
Most task managers, including all I've been able to sync with NC Tasks uses a four-level system; No Priority-Low-Medium-High instead of the full 10 levels defined in RFC 5545. This corresponds with NC Tasks own four colour scheme - Grey (No priority), Blue (Low priority), Yellow (Medium priority) and Red (High priority). The 10-level slider in Tasks is confusing when compared to it's own colour scheme and other task managers.
I request that the priorities slider is either changed to the defacto standard, RFC 5545-compliant four-levels; No priority Grey=0, High priority Red=1, Medium priority Yellow=5 and Low priority Blue=9 - Or have the option to toggle this feature akin to Calendars "Simplified Editor".
Thank you for your consideration and providing a great NC feature!
The text was updated successfully, but these errors were encountered: