As you know, the workflow statuses are also displayed in the workflow dropdown.
In our case we have a status called Closed. The users would like, "when closed is available in the workflow", to also show Closed as a button as well as in the dropdown.
is there a way of doing this and not affect the other default buttons that JIRA shows?
1 - We have to engage opsbar-sequence in the configutation first.
2 - If we do not use opsbar-squence for a different Status property, will that other status property still showup INSIDE the workflow dropdown.
3 - If we do not use opsbar-squence for a different Status property, will that other status property be hidden on the main screen.
1. Yes. 2. All unchanged status transitions will remain in the same order they are now. 3. See answer to 2 + You can also follow [https://confluence.atlassian.com/display/JIRA052/Configuring+Workflow#ConfiguringWorkflow-Changingthenumberoftransitionbuttons|this] to add the ops.bar.group.size.opsbar-transitions setting in the jira-config.properties file in your <jirahome> directory. This will set a default of workflow icons to show (not you are set to a default of 2, you can increase that to a larger number, thus showing more icons. 4. Yes. If your other transitions like Duplicate or Resolved have this value, they will still get ordered by this value. 5. Indeed. It's a dynamic status-based setting.
Peter, Attached shows an example of what we have. You will see that Close Ticket appears in the drop down.
That Close Ticket entry only appears when the ticket has been moved to the Resolved Status in our workflow.
What we want is away to ALSO show a button "Close Ticket" next to one of the other buttons (ie. In Progress, Workflow). Client wants to not have to click the dropdown to get to Close Ticket - they want a button.
Thus the new button must only be usable/visible when the Close Ticket option is available in the dropdown.ClosebuttonNeed.jpg
What you should do is go to the relevant workflow, click on the Close Ticket transition. Then go to the properties of this transition. Now you will set the order for this button on all screens it is relevant (since Close Ticket probably shows only when you are in Resolved status, this will be relevant for a specific button layout only).
The value you should insert for "Property Key" is "opsbar-sequence" and the value for "Property Value" will be something like 1. This will make the Close Ticket button show first (on the left, before Assigned).
If you want to set in between Assigned and In Progress, than you will have to set a relevant value for these buttons (transitions) too. For example: setting Assigned with opsbar-sequence = 10, Closed Ticket with opsbar-sequence = 20 and In Progress with opsbar-sequence = 30.
It is generally recommended to use these value differences of 10 so if you'll have more transitions added on later in your workflow lifestyle, you won't need to change the existing values, just set relevant values for new transitions (like 15, for a button in between Assigned and Close Ticket).
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs