On a Scrum board we're using Swimlane by Story, which is exactly what we need. There is one problem however; standard issue types without any sub issues is push down to the bottom to the "Other Issues" swimlane, ignoring the rank of the issue in question. This is a problem because issues are easily forgotten in the heat of the battle from time to time, and before you know the sprint is over and this important issue was never done.
Of course the qiuck fix for this is to give every standard issue type a sub issue, this is all very good for Story (and the like) where you can add a "Test"-task or "Write doc"-task etc. For non-programming tasks like (self defined) "Investigation" or something similiar, this approach doesn't seem like the right way.
How can we keep the Story-swimlane, and at the same time get those standard issues without sub issues up from the "Other Issues" swimlane, so that their ranking is displayed correctly in the Work-view?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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