nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA workflows- Restricting Different Statuses

Tim Langdon

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.

Accepted answers

All comments

Tim Perrault

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

Trudy P Claspill

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.

Screen Shot 2022-11-14 at 11.09.43 AM.png

You would then add transitions that indicate explicitly the From Status and To Status that you want to allow.

Screen Shot 2022-11-14 at 11.13.08 AM.png

Tim Langdon

JIRA worklfow.JPG

Tim Langdon

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.

Tim Langdon

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud