-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
JCMA - 1.11.17
-
None
-
3
-
Severity 3 - Minor
-
2
Issue Summary
The attachment ID was updated but the base URL was left as the source instance. This is the Jira attachment link pattern:
https://jira.source.com/secure/attachment/12345
The base URL https://jira.source.com was not updated to the target Jira Cloud site even though the attachment ID 12345 was correctly updated.
Steps to Reproduce
- Create a Jira project with an issue and attachment
- Add a link to an attachment that contains the format:
https://jira.source.com/secure/attachment/12345
- Migrate the Jira project to Cloud using JCMA
Expected Results
- After migrating, the user should be able to update product links: https://support.atlassian.com/migration/docs/update-product-links/
- Any attachment link should get updated to the target cloud site and new attachment id value:
https://jira.destination.atlassian.net/secure/attachment/11111
Actual Results
After the migration and running the task to Update Product Links, the link:
https://jira.source.com/secure/attachment/12345
was updated to:
https://jira.source.com/secure/attachment/11111
Note: the attachment was updated correctly but the base URL did not get updated to the target Jira Cloud URL
Workaround
Currently, users will need to update the base URL manually for any area that contains these partially updated links:
- Description
- Comments
- Custom fields