Hi Atlassian,
Question for you guys. I have created a custom workflow for my JIRA Board team. But I am having issued with it not displaying or working how I would like it. For example, how do I per say have a JIRA epic that is in say "plan/design" status and the next step would be "build/test" as a status. How do I make sure that Build/Test is the next status they can move an epic through? For example, an epic is in "plan/design" status but I only want the Build/Test status and maybe On HOLD and Cancelled as available to choose from vs all the statuses available to show. Thank you. I tried and set up conditions but it is not working properly. If someone could advise step by step would help greatly.
Hello @Tim Langdon
Welcome to the community.
Can you show us the workflow you have created? Show us diagram of the workflow please.
Are you working with a Company Managed project or a Team Managed project? My answer is for a Company Managed project.
I recommend that you try these changes with a test project, and after getting it worked out then make changes to your live project.
To restrict the moves between Statuses what you do is remove the All to <Status> transition. Where you see that, it is an indication that you can transition to the <Status> from any other Status in the workflow.
You would then add transitions that indicate explicitly the From Status and To Status that you want to allow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For example, as you can see I have all statuses being able to be transitioned. What I want to do Is I will remove that but I want a epic once its in "plan/design" status to only be able to then move to "build/test" and then from build/test I only want it to be able to be updated to "production approval" and so on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I want to keep requested, pending prioritization, roadmapped, on hold, and cancelled, all able to be allow statuses to be transitioned which is done. But once I get an epic to build/test, I only want these above to be available but only have Build/test" as their option. I do not want Prod approval, deploy to prod, stabalization period, and done to be able to display for them to choose.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yea it's the "All" transitions that are causing issues. @Trudy Claspill has sent you down the road to getting it the way you want. The all transitions mean you can go to that status from anywhere. You want to setup transitions from the status to status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Tim Langdon
Does this workflow apply only to your Epic issue type, or is it used for other issue types?
If the workflow is used for more than one issue type, and you want the change to affect only the Epic issue type, then you need to first make a copy of the workflow that you can then change. Let me know if we need to dive into that deeper.
If this workflow is already only applied to your Epic issue type, and the only transition you want to allow into the "build/test" status is from the "plan/design" status
1. Delete the transition (arrow) between All and BUILD/TEST.
2. It looks like you already have a transition between PLAN/DESIGN and BUILD/TEST, so you're done with that change.
If the only transition you want to allow into the "production approval" status is from the "build/test" status
1. Delete the transition (arrow) between All and PRODUCTION APPROVAL
2. Use the Add Transition option to add a transition From BUILD/TEST to PRODUCTION APPROVAL (example shown in my previous post).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tim Langdon
Would you mind posting a screen shot of the diagram view of your workflow? If I could I see it, I would have a better idea of what the issue might be.
Tim
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.