Removed migration mappings

Cloud Migrations
#1

The following mappings appear to have been removed from the migration mappings list:

  • jira:priority
  • jira/classic:issueType

They are no longer listed on the page:

https://developer.atlassian.com/platform/app-migration/mappings/

but can be seen on the cached version:

https://webcache.googleusercontent.com/search?q=cache:fdrSSOOqsTAJ:https://developer.atlassian.com/platform/app-migration/mappings/+&cd=1&hl=en&ct=clnk&gl=au&client=firefox-b-d

Does anyone know why they were removed? Are those entities retaining the same IDs after migration?

Regards,
Robert.

#4

Hi Robert,

I’ve had a look at

and I can see jira/classic:issueType is still listed. As for jira:priority I can see it is only used in the example request endpoint on both the current page and cached page, and isn’t listed on either page.

It looks like jira:priority is for Jira Software migration, but I’ll check the status.

Can you confirm if you can retrieve data for these namespaces?
Are they ones that you need to for your App to migrate correctly?

Thanks,
James.

#5

Hi James,

Thanks for replying. I’m sure that jira/classic:issueType was missing from the API doc when i made the post, but does appear to be there now.

My app requires the issue type mapping, not the priority mappings. I only mentioned it because when I compared the two pages (cached and live), those were the 2 mappings that had been removed.

Regards,
Robert.

#6

Hi @robertc

We’ve logged this issue as [MIG-502] Enable Jira nested mappings in the App migration platform which is currently being fixed. Please become a watcher of the ticket and we’ll update when the fix has been released.

Hope this helps.

Thanks,
James.

1 Like
#7

Hi @robertc,

The internal ticket for this has been resolved. Would you be able to test this again and see if the expected mappings are there?

Thanks,
James.

#8

Hello @robertc,

We’ve now tested this and the namespace mappings are appearing in new migrations.

Regards,
James.

1 Like