Our developers work on a single board for our project. This board has both Bug tickets and Story tickets. We're running into an idiosyncrancy in our workflow that I could use your help with.
Story tickets represent steps of feature development. So the development of a feature might involve 4 or 5 different story tickets (actually, they're Improvement tickets, but I don't believe this matters).
Bug tickets represent individual bug fixes. Unlike features, bugs do not have multiple tickets. They just have a single ticket.
Story tickets have a fairly simple workflow. Basically, they just go from To Do -> In Progress -> Done. Bug tickets, on the other hand, have an additional workflow... they go from To Do -> In Progress -> Resolved -> Done. The extra "Resolved" state is used to indicate that the bug development is done and is ready for QA.
The problem is that because our board supports all 4 bug states (To Do, In Progress, Resolved, and Done), this is confusing our users when they transition our Story tickets. "Resolved" does not apply to Stories, but because it's there some users are using it instead of "Done".
What would be a good solution to this problem? Is there a way to prevent Story tickets from going into a Resolved state? Alternately, does anyone have an example of a good Bug workflow that doesn't involve a Resolved state? How would bugs get QA'd in a workflow like that?
If you have separate and distinct workflows in the background, the boards won't allow stories to be put in inappropriate states. In other words, have one "bug" workflow with four states, and another "story" workflow with three. Use the workflow schemes to apply each workflow to each type, make sure the columns are mapped on the board correctly, and you'll find the "resolved" column greys out when you pick up a story to drag.
Simplified workflows only allows one workflow for the project (and you can't put restrictions on them really).
You need more control than the simplified workflow can give you.
I would, however, use your simplified workflow as the starting point!
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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