Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-57838

Jira Issues Macro in Confluence sometimes loses sorting ability on some columns

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Low
    • None
    • 6.6.3, 6.6.6, 6.12.2
    • Macros - Jira Macros
    • None

    Description

      Issue Summary

      The Jira Issues Macro in Confluence will sometimes lose the ability to sort some columns. Some of the columns will remain sortable, others will not.

      Environment

      • Confluence
      • Jira (connected via Application Links)

      Steps to Reproduce

      1. Link Confluence and Jira
      2. Create a Page
      3. Insert a Jira Issues Macro
        1. Choose a project of filter
        2. Make no other changes
        3. Save the macro
      4. Save the page

      Expected Results

      Most, if not all, fields should be sortable

      Actual Results

      Some fields cannot be sorted.

      The /rest/jiraanywhere/1.0/jira/clientIds/ call returns the macro. In order for a field to be sortable, the header must have <span class="jim-table-header-content"> wrapped around it. The non-sortable fields are missing this span.


      (Above, the 'Key' field can be sorted, but the 'Summary' field cannot)

      Notes

      This seems to not happen after a recent Confluence start-up, but after running for some time, it happens. It can be observed across pages, spaces, filters, projects, browsers, and users. Clearing the browser cache or using another browser does not fix it.

      Workaround

      Disable, then re-enable the Confluence Jira Plugin in Confluence.

      or

      Re-start Confluence

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jbentrup Jason B
              Votes:
              7 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: