You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
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.
start->evaluate->Completed
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.
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"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.