Bulk Changing issues Types via Groovy

[Zachary Singh]

Hi! 

I am trying to bulk change issue types via groovy. I have been able to do so but only at a single issue, here is the following script:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.event.type.EventDispatchOption

def issueManager = ComponentAccessor.issueManager
def constantsManager = ComponentAccessor.constantsManager
def loggedInUser = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def issueKey = 'xx-xxx' 

def issue = issueManager.getIssueObject(issueKey)
def summary = issue.summary
def description = issue.description
def sourceIssuetype = issue.getIssueType().getName()
def targetIssueType = constantsManager.allIssueTypeObjects.find {it.name == 'Task' }


if (sourceIssuetype = 'Bug') {
    issue.setIssueType(targetIssueType)
    issueManager.updateIssue(loggedInUser, issue, EventDispatchOption.DO_NOT_DISPATCH, false)
}

 I am hoping to pass a JQL into the script or a bulk amount of issues to change at once. The UI move is very tedious and often times out for us. Any suggestions?

[David Di Blasio]

Hi Lorenze,

Indeed just renaming "clones" to "cloners" should resolve this behavior. For some additional background on this issue please check the following KB article out:

• The Clone Link Type 'Cloners' Does Not Exist Due to Missing Property

Let us know if this helps :).

[lorenze larot]

Or maybe add a new issue link called "Cloners"? I have yet to try this. 

Thanks for the response. 

[David Di Blasio]

Happy to help! Indeed adding another issue link called "Cloners" will also resolve the behavior as well. Essentially Jira is just looking for this exact matching string during the process of creating the issue link while cloning an issue.

Please let us know how it goes.