Adding a new workflow to an existing project with multiple workflows attached creating issues.

[Usha Sagaram]

I am trying to add a new workflow to an existing project for a specific issue type (Epic). I created a workflow for the issue type epic and tried to add it to the project, it is messing up the statuses of the existing issues of different issues types like stories, bugs etc. For example I have a status called QA in my new workflow for epic. When I attach the new workflow to the project, it is changing the Ready for QA status which is what we have for stories, bugs etc to QA status which is the new status I have in the epic workflow. Why is this happening and what is the fix for this? Thanks for any help that can be provided to fix this issue.

[Carlos Garcia Navarro · Accepted solution]

Hi @Usha Sagaram ,

Just to confirm, if you check the workflow under project settings, how many issue types are linked to that specific workflow that you linked to epics?

[Usha Sagaram]

@Carlos Garcia Navarro  Just one which is Epic

[Vikrant Yadav]

Hi @Usha Sagaram  As you are changing the workflow of EPIC issue type. Issues were created in EPIC which is using the older workflow status, now you are changing workflow, so you have to map the old status with the new status of the new workflow. EPIC issue status also get changes according to the mapping. Mapping of old status with new is the only solution. or you can use same status in new workflow which you are using in old workflow. So it will not ask for mapping.

https://confluence.atlassian.com/adminjiraserver/managing-your-workflows-938847410.html

[Usha Sagaram]

@Vikrant Yadav Thanks will try that.