JIRA Software : Kanban / Scrum reuse the old workflow if the new project key is the same as the old project key
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When you create a new Kanban/Scrum project, the new project is associated with an old Kanban/Scrum workflow.
Diagnosis
Environment
- JIRA Software projects (Kanban, Scrum)
Diagnostic Steps
- Check if there is any workflow existed in your JIRA with the name similar to your new project key at Administration > Issues > Workflows.
Cause
This problem is due to the new project and a deleted old project happens to have the same project key. When the old project is being deleted, the workflow is retained in the JIRA. Therefore when a new project is created with the same project key, JIRA didn't create a new workflow as JIRA thinks it would be duplicated if it creates another one. Instead, the JIRA associate the old workflow with the new project.
Resolution
Deleting the old workflow and then recreate the project will allow JIRA to create a new workflow for the new project. However, please ensure that the old workflow is not being used anymore by any of other projects.
Take note of the inactive workflows as well.