Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-13701

JIRA "View on Board" link GHGoToBoard response time degrades with number of boards. Might result in 504 error


      NOTE: This bug report is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding bug report.


      View on board call (GHGoToBoard.jspa) loads all Board's JQL and executes them one by one to check if given issue belongs to it. So by design View on board performance will degrade with increasing number of boards. This also multiplied by complexity of each Board's JQL.

      Steps to Reproduce

      1. Create Jira with many issues (> 500k)
      2. Create many board (> 1000)
      3. Go to View on board link at any issue.

      Expected Results

      The page should load expected board where Sprint will appear.

      Actual Results

      The feature will fail with 504 error.


      • Re-try the page as will work sometime to see the applicable board
      Reduce number of boards
        • Check scrum boards. Check the sprint dates for the current/last sprint. If a project is inactive then it is highly likely that sprints have not been planned in the recent few months.
        • Check kanban board. Run the created/resolved chart for the filter/project in that kanban board and see. Again, if the project is inactive then not many new issues would had been created in recent past.
        • Check empty JQL board.

            Unassigned Unassigned
            ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
            10 Vote for this issue
            20 Start watching this issue