nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Migrate issues using scriptrunner

Aisha M

Hi,

I am trying to migrate my projects to a new workflow scheme, which has an updated Sub-Task workflow.

I have specified old status : new status mapping in the script. But, despite this, post migration, the sub-tasks are not working as expected (Though they are in the new workflow, they are behaving odd , like unable to move them through any status). We have used this same script to migrate other issue types without problem. Any thoughts on what we might be missing, or should sub-tasks be dealt differently ?

Here is a snippet of the logic,

def subtaskMapping = [ "old" : "new" ]

JiraWorkflow subTaskWF = workflowManager.getWorkflow("New Sub Task Worklow")

projectkeys.each { projectKey ->

def project = ComponentAccessor.projectManager.getProjectObjByKey(projectKey as String)
def oldWFScheme1 = ComponentAccessor.WorkflowSchemeManager.getWorkflowScheme(project)
def oldWFScheme = oldWFScheme1?.name ? oldWFScheme1.name: ""
def source

if (oldWFScheme == "XYZ Workflow Scheme") {
source = ComponentAccessor.projectManager.getProjectByCurrentKey("TEST") //source project with new scheme
}

if(source){
if(project){

def issues = ComponentAccessor.issueManager.getIssueObjects(ComponentAccessor.issueManager.getIssueIdsForProject(project.id));

issues.each{issue ->

if(issue.getIssueType().getName() == "Sub-Task"){
def oldStatus =issue.getStatus().getName()
def newStatus = subtaskMapping[oldStatus]
if(newStatus){
Status destinationStatus = constantsManager.getStatusByNameIgnoreCase(newStatus);
workflowManager.migrateIssueToWorkflow(issue as MutableIssue, subTaskWF, destinationStatus)
}

ComponentAccessor.getWorkflowSchemeManager().removeSchemesFromProject(project);

ComponentAccessor.getWorkflowSchemeManager().addSchemeToProject(project, ComponentAccessor.getWorkflowSchemeManager().getSchemeFor(source))

Accepted answers

Tuncay Senturk _Snapbytes_

Hi @Aisha M

I'm well, nice to hear from you

I'm not sure if the problem is related to that but I'd suggest two things at first glance.

1. reindex the issue after the migration

if (newStatus) {
  Status destinationStatus = constantsManager.getStatusByNameIgnoreCase(newStatus)
  workflowManager.migrateIssueToWorkflow(issue as MutableIssue, subTaskWF, destinationStatus)


  issueIndexingService.reIndex(issue)
}

2. Not related to the problems but it's a best practice. I'd call removeSchemesFromProject and addSchemeToProject once per project (not issue). So I'd change

if(source){
  if(project){

if (source && project) {

I hope this helps

All comments

Aisha M

Hello '@Antoine Berry @Tuncay Senturk _Snapbytes_ Hope you are well and good !!!! I just wanted to know if you experts have any thoughts that might really help me

Piyush Annadate _ACE Pune_

Hello @Aisha M ,

Can you log 'Status destinationStatus = constantsManager.getStatusByNameIgnoreCase(newStatus); and provide us the details'

Need to Confirm:

1. The status is correctly returned?
2. New workflow is published with required changes?

Tuncay Senturk _Snapbytes_

Hi @Aisha M

I'm well, nice to hear from you

I'm not sure if the problem is related to that but I'd suggest two things at first glance.

1. reindex the issue after the migration

if (newStatus) {
  Status destinationStatus = constantsManager.getStatusByNameIgnoreCase(newStatus)
  workflowManager.migrateIssueToWorkflow(issue as MutableIssue, subTaskWF, destinationStatus)


  issueIndexingService.reIndex(issue)
}

2. Not related to the problems but it's a best practice. I'd call removeSchemesFromProject and addSchemeToProject once per project (not issue). So I'd change

if(source){
  if(project){

if (source && project) {

I hope this helps

Aisha M

@Tuncay Senturk _Snapbytes_ Thank you for the reply ! That didn't make a difference.

I think it appears like, the sub-task is showing the new workflow scheme in the project configuration, but while moving through statuses, it still seems to follow the status of the previous workflow .

We have used the same script & logic to migrate Story, Bugs and few other issue types with no problem. Only sub-task seems to have this problem.

Ironically, when I ran a different script to directly make changes to the workflow scheme. that seems to work and move the Sub-task. But that was not practical unfortunately, because, around 1000+ projects use the scheme and that ran for around 15hrs . . This method of moving projects to a different workflow scheme with the new workflow, along with the mapping took around 2 hrs max

Aisha M

@Tuncay Senturk _Snapbytes_ I was able to figure out and it was such a silly mistake

It was supposed to be if(issue.getIssueType().getName() == "Sub-task") with a lower case "t" instead of "Sub-Task" . . I didn't know jira was this case sensitive :O

Tuncay Senturk _Snapbytes_

Ohh!, I would not find that. Thanks for letting me know. Yes, Jira is sensitive and case sensitive

Aisha M

@Piyush Annadate _ACE Pune_ Thank you for this suggestion. I was able to figure out the sub-tasks were not being processed only after adding logs. Definitely helped me pin point the problem

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

scriptrunner

jira

jira-data-center

data-center