Add status to active workflow? OR Bulk update the resolution field?

[Barbara Shaw]

Hi - we currently have an active workflow where we are tracking a number of bugs that have been fixed but not yet released. The status they are sitting in right now is "released" because a "ready for release" status was not included in the workflow when it was created. This workflow is shared by two projects.
1. The customer asked if I could add the status of "ready for release" but I can't edit an active workflow correct?
2. Is there a way to add a resolution of "ready for release" to the issues created by this workflow and bulk update all the issues that need to be in "ready for release" versus "released"?

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

You can edit an active workflow, there is a function for putting workflows into a "draft" mode.  The draft editor is limited in functions - you can't delete status from an active workflow, and there's a howling bug in that you can't add outgoing transitions to a status that does not already have one.

But you'll be fine to add status and transitions.

Resolutions are not directly linked to workflow.  You'll need to add a new resolution (if you haven't already got one) for "ready for release" and then push issues through a transition that either sets it to that, or asks the users for it.

[Barbara Shaw]

Thanks, @Nic Brough -Adaptavist- I appreciate your support! I'm concerned about this message on the workflow for this project when I click the pencil/edit icon: "Generated by JIRA Software version 1001.0.0-SNAPSHOT. This workflow is managed internally by Jira Software. Do not manually modify this workflow." 🫣 Would I be "safe" to copy this workflow, edit the copy to include the new resolution type, then publish the new workflow? Will all new issues then follow this new workflow for this BUGS project? I'm rather new to JIRA admin and don't want to break anything 😳

[Nic Brough -Adaptavist-]

Jira uses that warning a bit more than it ought to (it applies it to templated projects as well as simplified workflow projects nowadays)

The place you need to think about this really is just "simplified" workflows.  These apply only to "company managed projects", where one or more projects appear on a board, and the (JIra, not project) administrators have enabled simplified workflows.

In this case, do not edit the workflow - your changes can be destroyed by board admins.

All other workflows, go for it, perfectly safe.