Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Want to move IssueTypes from one workflow to other in same project



I want a sample code snippet using script runner how can i move a issue types from one workflow1 to another workflow2 and while moving the statuses of issue type should be updated accordingly.

Example UseCase :

My "Workflow-1" is created for "IssueType-1" and it has statuses like.

initial ->progess->end

(End being the final state for issueType-1) once it reaches end , this issue can be moved from workflow-1 to workflow-2 .


And workflow -2 is created for IssueType-2 and has following status.



IF i move issuetype1 with "END" status in workflow1 to another workflow 2

IT should reflect as issueType2 with status being set to "start".


Want to check if its possible to do ,if so if some one can suggest me how this can be done in Scriptrunner or any work around for this. Your guidance is much appreciated.





1 answer

0 votes

Issues do not "move workflow".  Workflow is directly determined by, and locked to, the issue type (the workflow scheme for a project tells Jira which workflow to use for each issue type)

So, your question is not "move workflow", it's actually "change the issue type".  This is not something you are going to do in a "snippet" of code - you are going to need to invoke and feed Jira's whole "move issue to another type" process (unless the two issue types are identical, having the same fields, field configs and, well, workflow)

I would very strongly recommend not trying to do this.  Changing issue type is something you should see as an "exception" - it's for when there's been a genuine mistake or wholesale restructuring or reconfigurations.

In the process you describe, a better option would be to have a single workflow, and one issue type.  Although I would say your design is odd: initial ->progess->end -> start -> others?.  Should that be something like "initial -> progress -> dev done/waiting for test -> in test -> others"?

Suggest an answer

Log in or Sign up to answer
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

95 views 0 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you