JIRA 7.3 Server users.
I have a question - we want to use only 1 workflow for all issuetypes. . we have an audit requirement so, we want all stories to go through the status "UAT Done". but we have certain stories that are just back-end changes and not have user testing. we want to provide users the ability to move these from "IT Testing" to "Released". but we do not want users to use this as a loop hole.
Can i restrict the ability to move to a particular status based on issuetype ? this is without add-ons and without going to code. we want to use only 1 workflow for all issutypes.
If you have any suggestions for our used case, please let me know.
Without add-ons or code, no.
There's nothing wrong with having different workflows that - where did that "requirement" come from? Workflows can easily share the same status - just because "Bugs" have to go through the extra step of "regression tests" doesn't mean they can't use open, in-progress, ready for uat, uat done, done, the same as improvements.
I know a fast solution with (add-on) ScriptRunner:
>>Simple scripted condition
>>> For example: ScriptRunner workflow function - Simple scripted condition (condition apply).
issue.issueType.name == 'Task'
Hope this will be helpful!
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
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