Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-13701

JIRA "View on Board" link GHGoToBoard response time degrades with number of boards

XMLWordPrintable

    • 6.07
    • 132
    • Severity 2 - Major
    • 176
    • Hide

      Hey Jira folks,

      We are glad to announce that this issue will be addressed in one of the incoming releases -> 9.0. We’ve replaced the old way of viewing issues on boards with an entirely new experience aimed at improving the responsiveness of searching for boards that display a particular issue.
      Now, instead of searching through every board in the system, Jira will only search the boards that make explicit mention of an issue’s project key and the boards you viewed recently. This way, you’ll get more meaningful results much quicker than before.

      Thanks, 

      Andrzej Kotas

      Product Manager
      Jira Data Center

      Show
      Hey Jira folks, We are glad to announce that this issue will be addressed in one of the incoming releases -> 9.0. We’ve replaced the old way of viewing issues on boards with an entirely new experience aimed at improving the responsiveness of searching for boards that display a particular issue. Now, instead of searching through every board in the system, Jira will only search the boards that make explicit mention of an issue’s project key and the boards you viewed recently. This way, you’ll get more meaningful results much quicker than before. Thanks,  Andrzej Kotas Product Manager Jira Data Center

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

      Summary

      View on board call (GHGoToBoard.jspa) iterates over all boards the user performing the lookup has access to 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 numbers of boards. This is also multiplied by the complexity of each Board's JQL.

      Steps to Reproduce

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

      Expected Results

      Call executed within 1 minute. It's JScript timeout.

      Actual Results

      Call times out with Communications breakdown error. If you open the link in a new tab it might take 200 secs.

      Note on fix

      A new "Find on Board" functionality had been introduced.
      We’ve replaced the old way of viewing issues on boards with an entirely new experience aimed at improving the responsiveness of searching for boards that display a particular issue.

      Now, instead of searching through every board in the system, Jira will only search the boards that make explicit mention of an issue’s project key and the boards you viewed recently. This way, you’ll get more meaningful results much quicker than before.

      What has changed:

      • We are not searching through all of boards that user has access to
      • Search is limited to:
        • Boards that make explicit mention of an issue’s project key (project-centric);
        • Recently viewed boards;
        • Maximum amount of 100 boards;

      Workaround

      1. Increase AJAX calls timeout
      2. If possible, reduce the number of boards and their complexity:
        • 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.
        • The list of JQL filters associated with all Boards can be retrieved running the below query: 
          select rv."ID", rv."NAME", sr.reqcontent from searchrequest sr, "AO_60DB71_RAPIDVIEW" rv where rv."SAVED_FILTER_ID" = sr.id;
      3. Disable the View on board functionality:
        • Block calls to /secure/GHGoToBoard.jspa at proxy level
        • please see example for Apache Httpd: 
          RewriteEngine On
RewriteRule ^/secure/GHGoToBoard.jspa - [F]
        • for nginx 
            # Blocked GHGoToBoard because of severe performance impact. Links
  # are not supposed to be accessible but people seem to keep find them.
  location = /secure/GHGoToBoard.jspa {
    error_page 403 /403-page-disabled.html;
    return 403;
  }

        1. View All Boards.png
          View All Boards.png
          25 kB
        2. View_on_board.png
          View_on_board.png
          65 kB

          Form Name

            [JSWSERVER-13701] JIRA "View on Board" link GHGoToBoard response time degrades with number of boards

            Cathy S made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 884298 ]
            Sandip Shrivastava made changes -
            Link New: This issue is related to JRASERVER-76185 [ JRASERVER-76185 ]
            Rodrigo Baldasso made changes -
            Remote Link Original: This issue links to "PSR-382 (Bulldog)" [ 464634 ] New: This issue links to "PSR-382 (JIRA Server (Bulldog))" [ 464634 ]
            Michał Błajet made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 722542 ]
            TJ Royall made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 706830 ]
            Andriy Yakovlev [Atlassian] made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 659962 ]
            Marcin Sasinowski made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 657679 ]

            Andriy Yakovlev [Atlassian] added a comment -

            Hi All,

            Note on backporting.
            This is a new functionality that required new UI, so it can't be backported to the previous 8.x line.
            Sorry.

            Cheers.
            Andriy | SET

            Andriy Yakovlev [Atlassian] added a comment - Hi All, Note on backporting. This is a new functionality that required new UI, so it can't be backported to the previous 8.x line. Sorry. Cheers. Andriy | SET
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-13701].
              {panel}

            h3. Summary
            _View on board_ call (GHGoToBoard.jspa) iterates over all boards the user performing the lookup has access to 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 numbers of boards. This is also multiplied by the complexity of each Board's JQL.
             !View_on_board.png|thumbnail!

            h3. Steps to Reproduce
            # Create Jira with many issues (> 500k)
            # Create many boards (> 1000)
            # Go to _View on board_ link at any issue.

            h3. Expected Results
            Call executed within 1 minute. It's JScript timeout.

            h3. Actual Results
            Call times out with *Communications breakdown* error. If you open the link in a new tab it might take 200 secs.
             
            h3. Notes
            None

            h3.Workaround
            # Increase AJAX calls timeout
            #* See https://confluence.atlassian.com/jirakb/how-to-change-the-default-ajax-timeout-in-jira-824345485.html
            #* This will work only for middle-sized instances. Suggested new timeout value: 120 secs
            # If possible, reduce the number of boards and their complexity:
            #* 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*.
            #* The list of JQL filters associated with all Boards can be retrieved running the below query:
            {code:borderStyle=solid}
            select rv."ID", rv."NAME", sr.reqcontent from searchrequest sr, "AO_60DB71_RAPIDVIEW" rv where rv."SAVED_FILTER_ID" = sr.id;
            {code}
            # Disable the _View on board_ functionality:
            #* Block calls to {{/secure/GHGoToBoard.jspa}} at proxy level
            #* please see example for Apache Httpd:
            {code:borderStyle=solid}
            RewriteEngine On
            RewriteRule ^/secure/GHGoToBoard.jspa - [F]
            {code}
            #* for nginx
            {code:borderStyle=solid}
              # Blocked GHGoToBoard because of severe performance impact. Links
              # are not supposed to be accessible but people seem to keep find them.
              location = /secure/GHGoToBoard.jspa {
                error_page 403 /403-page-disabled.html;
                return 403;
              }
            {code}             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-13701].
              {panel}

            h3. Summary
            _View on board_ call (GHGoToBoard.jspa) iterates over all boards the user performing the lookup has access to 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 numbers of boards. This is also multiplied by the complexity of each Board's JQL.
             !View_on_board.png|thumbnail!

            h3. Steps to Reproduce
            # Create Jira with many issues (> 500k)
            # Create many boards (> 1000)
            # Go to _View on board_ link at any issue.

            h3. Expected Results
            Call executed within 1 minute. It's JScript timeout.

            h3. Actual Results
            Call times out with *Communications breakdown* error. If you open the link in a new tab it might take 200 secs.
             
            h3. Note on fix
            *A new "_Find on Board_" functionality had been introduced.*
            We’ve replaced the old way of viewing issues on boards with an entirely new experience aimed at improving the responsiveness of searching for boards that display a particular issue.

            Now, instead of searching through every board in the system, Jira will only search the boards that make explicit mention of an issue’s project key and the boards you viewed recently. This way, you’ll get more meaningful results much quicker than before.

            What has changed:
            * We are not searching through all of boards that user has access to
            * Search is limited to:
            ** Boards that make explicit mention of an issue’s project key (project-centric);
            ** Recently viewed boards;
            ** Maximum amount of 100 boards;

            h3.Workaround
            # Increase AJAX calls timeout
            #* See https://confluence.atlassian.com/jirakb/how-to-change-the-default-ajax-timeout-in-jira-824345485.html
            #* This will work only for middle-sized instances. Suggested new timeout value: 120 secs
            # If possible, reduce the number of boards and their complexity:
            #* 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*.
            #* The list of JQL filters associated with all Boards can be retrieved running the below query:
            {code:borderStyle=solid}
            select rv."ID", rv."NAME", sr.reqcontent from searchrequest sr, "AO_60DB71_RAPIDVIEW" rv where rv."SAVED_FILTER_ID" = sr.id;
            {code}
            # Disable the _View on board_ functionality:
            #* Block calls to {{/secure/GHGoToBoard.jspa}} at proxy level
            #* please see example for Apache Httpd:
            {code:borderStyle=solid}
            RewriteEngine On
            RewriteRule ^/secure/GHGoToBoard.jspa - [F]
            {code}
            #* for nginx
            {code:borderStyle=solid}
              # Blocked GHGoToBoard because of severe performance impact. Links
              # are not supposed to be accessible but people seem to keep find them.
              location = /secure/GHGoToBoard.jspa {
                error_page 403 /403-page-disabled.html;
                return 403;
              }
            {code}
            Mateusz Beczek made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]

              b6cf9181bff6 Krystian M
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Affected customers:
              106 This affects my team
              Watchers:
              133 Start watching this issue

                Created:
                Updated:
                Resolved: