We use the standard JIRA issue types (Epic, Story, Task, Subtask,...). We have a custom workflow supporting a few thousand issues. Would like to carefully switch back to the default JIRA workflow for software projects.
In the process of switching, I selected in "Add Workflow" the default "Jira Workfow (jira)". In the "Assign issue types..." dialog for any issue type i select, such as "Epic" I see a little orange warning icon on the right. Before I proceed, what is that warning me of?
I have backup the JIRA cloud database.
If you hover over the warning sign do you get any text that alludes to what the error is?
In my instance when I create a new Workflow and associate it to a scheme I get an orange triangle and if I hover over it, the text begins with:
For a workflow to remain active in your project it must have at least one issue type assigned to it. If you assign this issue type to this workflow you will be de-activating another workflow and removing it from this project.
Hover over your warning and see what it says and let us know if you need further assistance.
Yes, thanks, that is the message. I am assuming I need to Add a new workflow (the Jira default) to the project. Will associate all the issue types to the new workflow (since they are all the standard Jira issue types). This will then perhaps deactivate the previous workflow, if a proceed?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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!
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