In the scheme described here:
It sounds great for culling feedback down to actionable items. But what about important bugs filed by QA or developers -- seems likely they shouldn't start out as Raw and need to be shuttled through all 4 stages before appearing in sprint planning. That is, if a new feature has a crash, and I'm entering the bug for that crash, how do I expedite it so it will be included in the next sprint (or sooner). Is the person entering the bug allowed to set the status or how best to handle that?
Well, you could have a transition that allows users to quickly transition issues into the appropriate status. You can also have a swimlane (https://confluence.atlassian.com/display/GH/Configuring+Swimlanes) that marks out important issues.
I realize also just a filter on type Bug is nice, because then everything stays in it swimlane but bugs are highlighted. Also I think you just do want someone else to expedite the bug besides the creator, you don't necessary want anything filing bugs directly to the front of the line, so long as bugs that should be there are expedited quickly enough.
When we encounter this situation for a bug that blocks a story or the daily smoke test, we add a Blocker label which we keep an eye out for during our normal daily Triage sessions.
These items are also @mentioned to the QA manager or verbally escalated to make sure that they get a jump on as needed.
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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