Summary

There are Jira macros with URLs such as

http://jira.customer.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?pid=10025&status=1&status=3&status=4&status=10000& component=10026& component=10362&sorter/field=issuekey&sorter/order=DESC&tempMax=1000

The http://jira.customer.com base URL should be updated to https://customer.atlassian.net IF the other entity id's can be mapped/updated such that the final macro/search works.

Replication steps

Jira Server

1. Create a project with:
   1. components
   2. workflows referring to custom (non-default) statuses, for example "in QA"

Note that component and status are used for reference only, this fix should apply to all migrated entities referred to by id.

Confluence Server

1. Create an application link to Jira.
2. Create a new page with a Jira macro ( {jira} ).
3. Insert a search URL into the search, with some Jira entities referenced by id.
4. Publish the page.
   The macro will have storage format:

   <ac:structured-macro ac:name="jiraissues" ac:schema-version="1" ac:macro-id="cba9ae64-3345-4e94-8728-d5eda09b3289">
       <ac:parameter ac:name="url">
           <ri:url ri:value="http://jira.customer.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?pid=10025&amp;status=1&amp;status=3&amp;status=4&amp;status=10000&amp; component=10026&amp; component=10362&amp;sorter/field=issuekey&amp;sorter/order=DESC&amp;tempMax=1000" />
       </ac:parameter>
       <ac:parameter ac:name="height">200</ac:parameter>
   </ac:structured-macro>
   

Migration

1. Migrate Jira and Confluence to cloud

Observe

Observe the Confluence page with the macro. Notice that the macro is broken after migration.

Notes

This depends on MIG-547 and/or CONFCLOUD-78131.
It is noted that this broken link contains a customer's full Jira URL - "http://jira.customer.com/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml". Fixing entity id's only will not solve the problem described in this Jira.

Workaround

There is no known workaround.