If you are talking about making the workflow actions in the dropdown appear as buttons, check out https://confluence.atlassian.com/adminjiraserver071/advanced-workflow-configuration-802592741.html#Advancedworkflowconfiguration-customisingtransitionsonviewissue.
Hi, we're looking to add them to the Issue Detail view on the Backlog screen. There's an ellipsis on the top right and we'd like to add the workflow steps in that drop down rather than having to choose "more actions", then choosing from another drop down, workflow and choosing a step.
Agree, opening the detail page one at a time for each item you want to resolve or close or whatever takes forever, i can hear my team audibly sigh as I click through all the pages to have access to workflow transition buttons, to finally resolve them.
Dragging things around on the board only works when you have perfect column/state alignment. But who does? We have a dozen states, obviously it's not viable to have that many columns.
@Nic Brough _Adaptavist_ , curious why it is considered wrong to change an item's status from the backlog - that seems like not hearing what your users actually want to do?
A backlog issue, is, by definition, something that might need attention that you have not looked at properly. I'm not saying you won't look at it properly, or that you won't refine it, but your backlog really is just a list of stuff you might consider as "stuff that might need doing". Things you do do with backlog items are
What's the point in changing the status of a backlog item? Until there is a positive decision that you are either going to work on them or shut them down completely, there's no good reason for a change of status.
If you're going to work on them, then add them to the sprint. No status change.
If you are going to kill them, that is when, yes, a change of status is useful in the backlog, but you really should be opening them up and transitioning to "done" with a full analysis of why you're not going to do it
I can't see any reason to change the status from the backlog.
This mindset that there is only one correct interpretation/implementation of Agile software development and that any deviation is WRONG is totally closed minded. JIRA's raison d'être is to flexible and adapt to its users workflows rather than the other way around.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events