Some Jira Issue links not resolving on initial load of Confluence Databases

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • Component/s: Database
    • None
    • 4
    • Severity 3 - Minor

      Issue Summary

      When loading a Confluence Database that has multiple Jira Issues linked only 20 issues are loaded properly.

      The column where the link should appear displays only a plain-text for the issue key, with no link, and other columns referencing other fields of that issue appear as blank.

      Upon manually searching for the issue, on any column of Jira Issue type, will force all the references to that issue to load/render properly. However upon refreshing the page it reset to the non-rendered state.

      This seems related to a pagination issue in the API response, hence only 20 items loading fine.

      Steps to Reproduce

      1. Create some Confluence Database with a column of Jira Issue type
      2. Populate rows with more than 20 different Jira Issues (ensuring your user has permission to see those issues in Jira)
      3. Load the page and check the issues listed

      Expected Results

      All Jira links and respective fields load fine (as long you have permission to see it).

      Actual Results

      Only 20 of Jira Issues links will appear. The remaining items will display only a plan-text issue key instead.

      Workaround

      The only known workaround so far is forcing the render of the "broken" links by searching for them manually in any of the Jira Issue type columns for that Database, however that's not persistent and the links will be gone upon refreshing the page.

        1. DatabasesBrokenLinks.png
          377 kB
          Rodrigo Bozza (Atlassian)

            Assignee:
            Rebecca Dai
            Reporter:
            Rodrigo Bozza (Atlassian)
            Votes:
            5 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: