The idea is to mark issue status in red, i.e. new status category of BLOCKED, in case, a prerequisite to work on the issue is not given.
An example: The infrastructure team is not able to provide a required data base system to me yet, where I can reproduce and fix an application bug. Therefore, it is impossible to me to solve the issue even if I want to. In that case, we need JIRA to show issue status in red, signalizing, something is impeding the progress on that Issue, i.e. special attention is needed.
In other words:
I only know 3 status categories in JIRA. A status may be "TO DO" (gray), "IN PROGRESS" (yellow) or "DONE" (green). In addition, we need "BLOCKED" (red). How can we do that?
Creating a new status, working with workflows and workflow schemas is not the point: Each new status must belong to one of the mentioned 3 categories. We simply need a new one.
Thank you in advice for your time!
(PS: Some ideas I found, like this:
are unfortunately not what I am looking for.)
Thank you very much, Nic, for your quick answer.
Just to know: Supposing, I have my own JIRA server and I would spend some development work on it: Is there a "clean" way to implement new status categories / colors / red?
(Clean means to me: not changing the JIRA core source, i.e. with a plugin or similar approach.)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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