Jira Repair Macro mistakenly finds wrong macros on pages with ‘Tip’ macro

XMLWordPrintable

    • 6
    • Severity 3 - Minor
    • 1

      Issue Summary

      Jira Repair Macro mistakenly finds wrong macros on pages with ‘Tip’ macro.

      Macro Repair performs successfully; and then when you click start Macro Repair, it pops up with this message "we've found broken Jira macros on your instance" given that the users has run Macro Repair several times without any errors. 

      Steps to Reproduce

      1. Run Jira Macro Repair, start
      2. Map Jira -> System Jira
      3. Completes Marco Repair without any errors
      4. And then repeat step 2, and then system prompts wit this popup message _
        "We've found some broken Jira issue macros on your instnace"
      5. Repeat the same steps and it comes up with the same popup message
      6. No errors are logged

      Note, the actual macro is associated with TIP Macro

      <ac:layout><ac:layout-section ac:type="single"><ac:layout-cell><ac:structured-macro ac:name="tip" ac:schema-version="1"><ac:parameter ac:name="title">Welcome to your software project space!</ac:parameter><ac:rich-text-body>
      <p>This is home base for your software project in Confluence. It's where you can plan your project, keep important documentation, and discuss it all with your team.</p></ac:rich-text-body></ac:structured-macro>
      <p>Next, you might want to:</p>
      
       

      Expected Results

      Jira Macro Repair is expected to fix TIP Macro

      Actual Results

      Jira Macro Repair doesn't fix this macro and continuously reports broken macros. 

      Workaround

      The workaround is to delete the Macro, update the page, reinstate the macro and then update the page.

            Assignee:
            Ryan Szczecinski (Inactive)
            Reporter:
            Sayeed Islam (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: