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

As an JIRA Administrator I want to show to users JQL complexity of the Kanban boards

XMLWordPrintable

    • 3
    • 19
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      This is related to performance problem described in https://jira.atlassian.com/browse/JSW-13211. A JIRA system has a maximum throughput of JQL's depending on the number of cores etc, DB, index etc. Kanban boards have a "JQL load score" (JQL complexity) based on the complexity of the query and the multipliers created by swimlanes+colours.
      A system can become overloaded if too many Kanban boards with a high "JQL load score" are loaded in a short interval.

      Suggested Solution

      The system performance can be maintained if users that create boards are advised of their "JQL load score".

      Workaround

      Parse access log for slow requests and then review related Kanban boards

        1. kpc_app.kt
          4 kB
        2. kpc.jar
          2.19 MB

            [JSWSERVER-13797] As an JIRA Administrator I want to show to users JQL complexity of the Kanban boards

            Andriy Yakovlev [Atlassian] added a comment - - edited

            Update 2017-10-27

            This tool provided as is and not supported by Atlassian team.
            Our dev team prepare simple test tool to help to identify slow loading Kanban boards.

            This is single threads, so it produces minimal load. Tool will wait one minute after loading one of board will fail. That being said, we still recomend to run tool against staging or during low peek hours.

            How it works

            Script do the following:

            1. Loads all boards
            2. Filter only kanban boards
            3. Load each kanban board
              • For each board load all issues
            4. Group and count the issue prefix, that will give details about projects
            Output

            Output will contains board id, name, project count, load time (in ms), error message. Also there will be 2 output files:

            • kpc-output.csv - all kanban boards, not sorted, printed right after load board
            • kpc-sorted-output.csv - kanban boards with more than 1 project, sorted by project count
            Usage

            To run tool use command:

            java -jar kpc.jar -DjiraUrl=<Jira url> -DjiraUser=<username> -DjiraPass=<password>

            Example:

            java -jar kpc.jar -DjiraUrl=http://localhost:8080 -DjiraUser=admin -DjiraPass=admin
            File

            Download kpc.jar
            Source: https://bitbucket.org/dwlizlo/kanban-project-counter

            Andriy Yakovlev [Atlassian] added a comment - - edited Update 2017-10-27 This tool provided as is and not supported by Atlassian team. Our dev team prepare simple test tool to help to identify slow loading Kanban boards. This is single threads, so it produces minimal load. Tool will wait one minute after loading one of board will fail. That being said, we still recomend to run tool against staging or during low peek hours. How it works Script do the following: Loads all boards Filter only kanban boards Load each kanban board For each board load all issues Group and count the issue prefix, that will give details about projects Output Output will contains board id, name, project count, load time (in ms), error message. Also there will be 2 output files: kpc-output.csv - all kanban boards, not sorted, printed right after load board kpc-sorted-output.csv - kanban boards with more than 1 project, sorted by project count Usage To run tool use command: java -jar kpc.jar -DjiraUrl=<Jira url> -DjiraUser=<username> -DjiraPass=<password> Example: java -jar kpc.jar -DjiraUrl=http: //localhost:8080 -DjiraUser=admin -DjiraPass=admin File Download kpc.jar Source: https://bitbucket.org/dwlizlo/kanban-project-counter

            mike brosnan added a comment -

            For users of JIRA, their individual and team's experience is dependent on how the project and boards have been set up. The other side of this is that JIRA instance performance can be impacted by pervasive instances and usage of poorly set up boards.

            Since this vulnerability exists, JIRA users should be directed towards better usage patterns by pop-ups when boards are saved etc.

            mike brosnan added a comment - For users of JIRA, their individual and team's experience is dependent on how the project and boards have been set up. The other side of this is that JIRA instance performance can be impacted by pervasive instances and usage of poorly set up boards. Since this vulnerability exists, JIRA users should be directed towards better usage patterns by pop-ups when boards are saved etc.

              Unassigned Unassigned
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              28 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated: