Availability of all statuses(for all projects, workflows) mappings during migration process

[Valentin Mikhailov]

Hello, community!

Could someone help me?!

I have a question regarding the issues statuses mapping during DC to cloud migration. Is there is a way to get all possible/available issues statuses
mappings? (see jira/classic:issueStatus)
Currently, it looks like I get mappings for thous statuses that are used in projects currently migrated, but in my plugin I need
all the statuses mappings because plugin might contain information about other projects(migrated earlier or migrated manually).


Explanation by example: for instance, I have migration process from DC where I have 5 projects but migrating only one - "Project One" which one has
workflow something like this:


during the migration I'm migration my App as well which has data regarding 2 DC project statuses say "Project One", "Project Two", where project "Project Two" has been
migrated earlier, moreover "Project Two" has different workflow:




One can notice that currently migrating project "Project One" has no "Under Review" status in workflow, but "Project Two" has one. So during migration of my App
along with "Project One" request to statuses mapping does not return mappings for "Under Review" status even if it presents in both DC and Cloud(was
migrated earlier). But if App is migrated along with "Project Two" which one has "Under Review" in the workflow, request to mapping statuses does return
mappings for "Under Review". Is this behaviour expected, and can I have all the statuses mapping for all the projects during migration?!

[James Richards · Accepted solution]

Hi @Valentin Mikhailov

The workflows are migrated with the project, so if the status isn't in a workflow then it won't be migrated. What you are showing here are 2 different workflows and so the status are different.

jira/classic:issueStatus will be the issue statuses that are used for the issues, not all the ones in the workflow.

What you can do on server is write a migration listener, and then query the database and send the data yourself that you need. You can review the documentation in https://developer.atlassian.com/platform/app-migration/app-data/

Hope this helps.

James.

[Valentin Mikhailov]

Hi, @James Richards

Thank you for  an answer and detailed explanation. Will take a look toward the migration listener!

[Rajesh Ramankutty]

Hi You can create the Same Status in the Cloud JIRA and Try