Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Adding a new status and transition to multiple workflows with the same transition ID

Noah Conley February 12, 2019

I have 4 pre-existing workflows that have the statuses Ready for Deploy and Ready for QA with a transition in between. On all 4 workflows, the transition ID is the same.

I'm trying to add a new status, Deploying, and add a new transition between Ready for Deploy -> Deploying (the old transition goes Deploying -> Ready for QA), but I can't figure out how to reuse the transition so they all have different IDs.

I published the changes from one of the workflows with the idea that when creating a new transition from a different workflow, I would be able to reuse the transition I created for the publish workflow, but that doesn't seem to be the case.

How do I reuse the new transition with the same ID on the other workflows?

1 answer

1 accepted

0 votes
Answer accepted
Ignacio Pulgar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 12, 2019

When a workflow is copied, the new workflow initially has the same transition ids than the original one.

However, further editions in one of those workflows, either in the original or the copy, do not affect the other one.

The only way I can think of for achieving what you need on a Jira Cloud instance is:

  1. Copy the workflow which would take more time to build from scratch (ie: named 'merged').
  2. Edit said merged workflow and add all statuses and transitions from all the remaining workflows which transition ids you'd like to be identical. Be patient, will require some time.
  3. Once the merged workflow counts with all statuses and transitions from the desired workflows, make as many copies of it as the number of desired workflows.
  4. Get one of the copies of the merged workflow and edit it by removing statuses until it uses the same statuses than one of the workflows you'd like to use.
  5. Repeat step 4 for getting each of the reamaining workflows with each of the remaining copies of the merged workflow.
  6. Keep the merged workflow as a backup, just in case you need it for creating slightly different workflows with the same ids.

Hope it helps.

Noah Conley February 12, 2019

Thanks for such a quick and detailed response, but this solution is more complicated than what I'm looking for, especially since I don't want to mess up any other transitions hooked into external services.

Ignacio Pulgar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 12, 2019

I understand. If it were a Server instance, there whould be a way for setting the ids directly against the database...

Noah Conley February 12, 2019

I see, I'll keep that in mind if we ever need to evaluate using the cloud vs a server

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events