-
For few state transitions (which I guess is majority of the cases), current mechanism is convienent, otherwise you will need to operate from a drop down menu, even if there is enough screen estate.
Actions buttons are intentionally not to use state color, to distinguis itself from state badge.
-
This is more an issue on the mobiles, where even don't have a vertical padding between buttons. So you are saying that when we have more state transitions the buttons will render as dropdown? Is this a thing?
-
Hmm... can be a problem on mobile for many buttons.
-
Yes, yesterday I did a test and launched the form for creating a new issue on my fiancée's phone (so she could add bugs in our Smart Home) - the UI was not approved by my other half at all xD
-
Previous Value Current Value Open
Closed
-
For this rare case, proper margin will be added when state transition buttons are wrapped.
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Hi Robin,
I wonder if we could a bit improve the user experience for
issuestate management. It's not a big change in my opinion but I can drastically improve not only the UX but also simplify the UI.I have few
issuestatesconfigured in my system with configured colours:I also configured the
state transitionsfor the allissuesaccording to my needs. But when I'm onissuedetails page:issuestateare in the same colour - ignoring the configurationOpenstate which will renderdropdownlist with all possible state transition options.Best regards!