-
Suggestion
-
Resolution: Unresolved
-
2
-
37
-
Problem Definition
I have a workflow in Jira where each status has three to four outgoing transitions. JIRA only displays buttons for two transitions, hiding the others inside a "Workflow" dropdown. The choice seems really arbitrary.
Suggested Solution
In regular Jira, I could adapt the property ops.bar.group.size.opsbar-transitions (via Advanced settings) to fix this, but I currently cannot make it in the cloud.
Please consider adding UI for changing this.
It would also be beneficial if customers could change the Ops Bar Action icons in addition to the workflow transition buttons. I.E. be able to view 'clone' or 'attach files' as a button instead of in the list of it's a heavily used function.
Why this is important
The problem is that these transitions are easily overlooked by users not yet used to that workflow 
. Furthermore, those who do know that there are additional transititions have to make one extra click to trigger them.
Workaround
No workaround yet.
- is related to
-
- Closed
-
- Gathering Interest
- relates to
-
- Closed
[JRACLOUD-37873] Allow configuring "ops.bar.group.size.opsbar-transitions" in Jira Cloud
Does Atlassian take any of these feature improvements seriously? every one of these i see has been open and unresolved for YEARS
I commented on this last year. Recently though, we've started to see previews of a new Issue View from agile boards, in which the status transition is just a simple dropdown. If they are planning on eventually making that the "real" issue view, then this request becomes obsolete. I like the new view much better overall. They just need to refine it a little bit.
This has become a problem for us with not having control of how many buttons show. It is a little weird that you have to click the drop down to see additional work-flows and it is not very intuitive. I would love to have control over how many additional buttons can show.
This affects our cloud installation which has many teams (50+) with various workflows. We know how to control the order in which the transitions appear, but can't set the # of buttons like we could in JIRA Server. In general I think having some of the items top-level and others in a drop-down is mixing UI paradigms.
We have added support for this using our new add-on in tandem with a browser extension. Check it out at https://marketplace.atlassian.com/plugins/bandage-jira/cloud/overview
This should be much, much simpler... transition properties should have a 5th tab: Triggers, Conditions, Validators, Post Functions, and Actions Order. The new tab would show the number of buttons, defaulting to 2. The order would be sorted through a simple visual AJAX sorter which would set the opsbar.sequence values for each transition.
This should not be a property that users have to assign a value using the List. It's HIGHLY confusing because you cannot set the opsbar.sequence using the Diagram. The inability to use the Diagram View for opsbar.sequence is not documented anywhere. It's just assumed that users would understand, even though it's exactly the same when you get the general properties of the transition.
I get that there is a new issue view with only one transition button with a drop-down. That helps so that users see all transitions available. However, the ordering there cannot be influenced by Jira admins, it is just alphabetical within each status category. We would really like to have more flexibility there. For example, from status 'Waiting for support' we would like to offer the transition 'Wait', but this is clearly rather an exception than the standard use case, which is rather 'Start work'. So therefore it is rather cumbersome that the dropdown list starts with the transitions from the status category 'Waiting'.