-
Suggestion
-
Resolution: Unresolved
-
127
-
15
-
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Aditi Dalal
adalal@atlasssian.com
Product Manager, Jira Cloud
Problem
Linking 2 sites that have been cloned from each other throws the following error message:
{ "status": 409, "message": [ "Target application has the same ID as the current one. Linking directly back to this application (or clones of this application) is unsupported." ] }
Suggested Solution
Please provide a way to update the ID as done for Data Center/Server: https://confluence.atlassian.com/jirakb/change-the-server-id-for-an-instance-of-jira-server-285839562.html
Why This Is Important
XML backups are currently the only way to back up and restore everything from an instance. All other approaches are incomplete
Workaround
Using the Jira Cloud-to-Cloud approach
- mentioned in
-
Page Loading...