Apply new workflow without affecting other JIRA boards

I went in and made a copy of a workflow that is shared across many workflow schemes in our Jira instance to create a new workflow. After copying the workflow I began making changes to the workflow and assigned it to a different scheme.

Those changes worked within my project and everything was running as expected. Over the past few days it seems like Jira has been populating out the new statuses that I created for my new ticket workflow to other unrelated projects. I have looked into finding the issue that I might have caused through a rogue linking somewhere but failed to find any.

Has anyone else had an issue similar to this and know how to fix it? It looks as though it is populating the new statuses that I added in the copied workflow to the older ones.

2 answers

1 vote

Hi Kyle,

  • What workflow statuses did you change?

I have seen issues when you try to change a default status where it will change throughout the instance no matter which workflow you do this on as it is tied to the status id in the database.  Here is an example:

  1. Here is the workflow I copied from a default Workflow:
    • Screen Shot 2017-10-13 at 3.25.22 PM.png
  2. Here is the change from In Progress to WasinProgress:
    • Screen Shot 2017-10-13 at 3.25.57 PM.png
  3. Here is a completely different workflow where the status has changed:
    • Screen Shot 2017-10-13 at 3.26.33 PM.png

In order to create statuses for the Workflow exclusively you would need to create new Statuses for that workflow per Define New Status or Steps in JIRA Workflow.



That was the issue. Thanks!

0 vote

It won't be doing that, it's a lot more simple.

Status are shared global objects.  There's a list of them under admin -> issues -> status, and I suspect what you've done is changed existing status, rather than create new ones for your new workflow.

You'll need to rename all the status back to what they were before, to fix the old workflows, then re-engineer the new workflows you've done, adding more status and replacing the  ones with the wrong names. 

Status name changes take effect instantly though, it's not "over the past few days"

You're right. That's exactly what I found after I posted this question. Thanks for the answer reaffirming my suspicion! I have changed the statuses back and learned from my mistake.


Thanks again!

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,323 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot