I am creating a change request workflow. Throughout the workflow I notice there are about 3 status with similar names
- CAB Inital Review
- Pre-change CAB Review
- Post-change CAB Review
I read about this https://community.atlassian.com/t5/Jira-Core-questions/Two-of-same-status-in-workflow/qaq-p/108233 which suggesting to use single status name "Review" with different condition.
If I follow the suggestion above, means my review statuses will always be the same that is "Review". my questions:
1. CAB as reviewer, will he or she knows which kind of review he or she is currently at ?
2. In the dashboard and reporting. Can I differentiate between review statuses ? How to find out which review taking the most time ?
3. Should I just use 3 review statuses as I designed initally ?
Hi @Mustafa Abdat,
I've seen instances where 3 review statuses are made. As a JIRA admin, you want to stay away from making too many statuses. Depending on the number of statuses you currently have that is an option. But the reviewer will not know the kind of status with this option.
Another option could be to make 1 status called 'Review' and add a custom field to the screen. The custom field could be called 'Review Status' (for example) and have a drop down box that has Pre-change CAB Review and Post-change CAB Review.
The only caveat is that someone would have to choose from the drop-down box once it's transitioned/or in Review.
In your dashboard, when using a gadget or creating a report, you can create a JQL filter to pull issues in specific statuses.
It depends on where you would like to place the complexity.
Decisions are better or worse depending on your goals.
Both approaches have pros and cons.
I usually defend simplicity. However, if a requirement cannot be easily met but by increasing complexity, I'm open to making exceptions.
When a requirement increases configuration complexity, I usually ask questiions about why it is needed and analyse if it's really worth it.
How much value would a certain configuration add to the organisation?
How many billions do we loose if we do not implement it? (kidding)
How many people would take advantage of it?
Whose life would be easier with it? And whose life would be more difficult?
How would that change impact Jira? Does it need maintenance?
Who am I likely to disagree with depending on my decision?
What real monetizable actions could be triggered by having that setting in place?
Well, I could have focused just on the technical pros and cons, but that's either documented, or learnt through experience in an easier manner.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.