Bug: Jira issue type Workflow Updates is affecting other issue types that it shouldn't be

[peter]

I'm following instructions for creating seperate workflows for different issue types as per your own guidance, yet when I create a "To Do" Status for story issue types, it overwrites my "Requested" status for "Story" issue types, and vice versa. Why are these coupled when I'm trying to only edit a workflow for a specific issue type?

[Rilwan Ahmed]

Hi @peter ,

Check if your system already has the required statutes in https://<baseURL>/secure/admin/ViewStatuses.jspa and create any new status if required. 

2. Go to Admin settings --> Issues --> Workflows 
Search for required Workflow and see how many projects it is mapped in "Included in Project(s)" column

[Kristopher Perez]

I’m not 100% sure what happened, but I do have a good guess. One thing you want to be careful with is that Statuses are shared objects. What does this mean?

Lets say you have Workflow A:

• To Do
• In Progress
• Done

and Workflow B

• To Do
• In Review
• In Progress
• On Hold
• Done

Now, if you edit Workflow B, and specifically edit the name of the existing status “To Do”from To Do to Backlog, what you have done is affected a Global Object. Every Status is shared in a common area, so a change to the shared object changes every workflow that uses that shared object.

Instead, what you should be doing is adding a New Status and removing the old Status from a workflow. When you choose a Nee Status, it will provide you a list of all the shared Statuses, and if the one you are looking for doesn’t exist, it will offer you the option to create a brand new Status.

Hope this helps

Kris