-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
High
-
Component/s: Macros - Other - Native (1st Party)
-
44
-
Severity 3 - Minor
-
175
Issue Summary
After running Jira Macro Repair, a macro may still show this message
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
In this case, viewing the storage format of the page will still show the original server application link id and server name instead of the new cloud values
Steps to Reproduce
- Run Jira Macro Repair from the Confluence Cloud UI
- Map the Old > New application link[s]
- Once completed, review example pages
Expected Results
Macros should be updated and rendering correctly with results, or at least the message no longer showing and rendering with zero results in cases where JQL is invalid, or where Jira projects have not been migrated yet.
The macro fix traceId should list the page as having been updated
ext.traceId=0087253092cc0429 `connie-prod` "123456"
LOG Entries
- Received broken content ids from cc-migration
- Processing body content of page
- Processing macro on page
- Jira macro changed, pending save
- Attempting content entity update
- Updated content entity
- File scan-based fixing result: {"status":"DONE","additionalMessage":"","problems":{"contentIds":[],"existingAppLinks":[],"brokenAppLinks":[],"status":"DONE"},"skippedContentIds":[123457],"fixedContentIds":[123456],"partiallyFixedContentIds":[],"fileScanResult":false}
Actual Results
Having identified the macro fix trace id and the affected pageId, running this query to locate the page in the logs shows
ext.traceId=0087253092cc0429 `connie-prod` "123456"
LOG entries
- Received broken content ids from cc-migration
- Processing body content of page
- Skipping page update due to no changes.
- File scan-based fixing result: {"status":"DONE","additionalMessage":"","problems":{"contentIds":[],"existingAppLinks":[],"brokenAppLinks":[],"status":"DONE"},"skippedContentIds":[123456],"fixedContentIds":[123457],"partiallyFixedContentIds":[],"fileScanResult":false}
The page has valid macro[s] that should be updated but the page has been skipped and the macros not updated.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is blocked by
-
PGXT-5406 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
ACE-5202 Loading...