Allow for alphanumeric or select-based priorities
Opened this issue · 8 comments
What would you like to be added?
Would it be possible to allow for priority fields that are not numeric? While emojis might be a slippery slope and something I don't personally use regularly, the ability to set a priority field that is text or select-based would be helpful. This is partly a friction concern, but also a disability access related feature request.
Why is this needed?
The ability to DND items from no status to a column to adjust the meta in files quickly would be appreciated and allow users that primarily use touched based inputs vs mouse or keyboard, to have greater and/or more equitable functionality. Current functionality requires a priority to unlock the DND feature, yet only numeric fields appear to be priority options.
The tricky thing is how you'd know which value to set when you move the card.
With a numeric Priority field, the plugin can just update the notes with the new order, or choose any number between the two card, really.
If you drag a card and drop it between 🐸 and 🐣, what value should the card have?
Related: #205 suggests allowing users to sort cards without a Priority field.
Isn't the value being set the category? That is how it appears on my end.
In your example it would have the value that isn't the frog (I can't visually decipher the emoji).
I am not seeing any priority column being updated when moving a note between lanes. It is why I think emoji cases would be a slippery slope and quandary. The current setup requires the user to have a yaml field that uses a numeric value, whether their note requires a numeric yaml field and hoping the plugin allows the numeric field to be selected as a priority. Selecting a priority does not appear to have any effect on the note's metadata itself.
Hmm. I suppose..., if priority field isn't updating anything in the notes, I'm now unsure the purpose of it? Is it all behind the scenes?
The Priority determines how cards are sorted. Here's how it works:
priority.mov
When the user moves a card, it writes the order of each card to the corresponding note.
If the user moves a card between two cards with priority set to 1 and 3, the card gets updated with a priority of 2.
seeing any priority column being updated
It sounds like you want to use emojis as the column title? In that case, you want to set the Status field instead of Priority.
Thank you for the video. Selecting my amount field as priority was not wise now I see it in action! HA HA. I wasn't seeing it because I didn't/don't have a field for prioritizing my cards, they were all in unprioritized, except one card, so the value never changed.
No, I do not want emojis. I just know that they are a common use case, just as a check for someday, another symbol for in progress or do next, etc. Others use text or tags for those priorities. I would use text. I suppose I could change my process on my end to accommodate the numeric value to use the feature properly.
to clarify, an example.
In a project for cleaning house, a category for location. This would populate for kitchen, living area, yard, etc with a priority of todo. someday/maybes might stay in unprioritized. prioritizing cleaning the stove before sweeping might have the priority field state do now, do next instead of numbers. One could do those adjustments for each cleaning area.
For those of us who can switch to numeric orders easily in our brains this might work. Other people think in pictures or words.
Oh, I see! 💡
Rather than sorting the cards, you're looking for more of a secondary grouping within each column.
Hm. You can already create text fields with predefined options by selecting Configure field in the column in the Table view, so we could potentially allow text fields with options configured, as a Priority. I'm worried that it might muddle the meaning of Priority.
I like the use case, but right now I'm thinking it's a separate field, something like "Group by category" or something.
I can see where you are coming from. I was watching one of Danny Hatcher's videos where folks who use a GTD, or similar productivity system, use priorities of high, medium, and low. This seems to be a common enough use case. That is still a specific priority, though I can envision how that might be considered a secondary grouping instead.
That type of use case may muddy the waters as a common use of "priority".
Hi fellows,
I saw your screen record here and get excited cause I thought this is not implimented for a long time
but when I am trying to do the same it wont work @marcusolsson
I also dont have anything called "priority" as I saw in your video but it doesnt work for my even with sort option.
could you please help me figure out what is wrong? I want to change the order (the weight2 value in the video) with drag and drop and not entering the values with hand
there is a video that i explain my case further more(the video has sound) (sorry for my English, I am not an English person)