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; } } }

Locking the Requirements (Story) using Workflow - Impact on other workflows using same status

Athar Mushtaq_kpzf39

I understand we can add a property to a workflow status to disable editing. Our Jira instance is being used for hundreds of other projects as well. I have created a new workflow and only associated it with the relevant project.

My question is - If I add a restriction property to one of the status in the workflow (Let's say Inprogress) would it affect other projects / workflow where the same status is being used?

If yes, what would be the best way to implement this.

Thanks,

Accepted answers

Tessa Tuteleers

Hi @Athar Mushtaq ,

Welcome to the community!

Good news, setting a status property in a workflow only works on that particular workflow.
This should be mentioned more clearly in the documentation, now it's not really described.

- Tessa

All comments

Tessa Tuteleers

Hi @Athar Mushtaq ,

Welcome to the community!

Good news, setting a status property in a workflow only works on that particular workflow.
This should be mentioned more clearly in the documentation, now it's not really described.

- Tessa

Jack Brickey

And this can be easily confirmed by making your change then going to another project workflow and inspecting the same status. In short properties is associated with the workflow.

Athar Mushtaq_kpzf39

Thank you Tessa and Jack - Much appreciated

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