Create Issue Performance

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 9.4.7, 9.9.0
    • Affects Version/s: 8.20.9, 9.4.5
    • Component/s: Issue - Actions
    • None
    • 8.2
    • 1
    • Severity 2 - Major
    • 4

      Problem

      Time spent between the User hitting the "Create" button and receiving the pop-up window for the creation of the issue is slow. 

      The slow request is the "/secure/QuickCreateIssue!default.jspa?decorator=none".

      If the user has access to multiple Project, and these project contain multiple issue types, and each issue type contains multiple fields defined with a default value, multiple SQL queries will be executed on the genericconfiguration table:

      "SELECT ID, DATATYPE, DATAKEY, XMLVALUE FROM jiraschema.genericconfiguration WHERE DATATYPE='DefaultValue' AND DATAKEY='99999'"
      

      The data loaded is stored in the cache CachedOptionSetManager and it expires after 5 minutes. So a second "Create" action executed by the same user will be fast, as the data will be gathered from the cache.

      Workarounds

      1. Give all users only access to projects which they need to.
      for admins it will still load slowly (if they need access to all projects)
      but for end-users it might be fast, if they have access only to a couple of projects

      2. Define a higher expiration time for the cache, adding on the jira-config.properties (all nodes) and restarting Jira:

       optionset.cache.expiry.minutes=30
      

      We do recommend to execute issue type maintenances during off-peak hours to avoid old data returned as reported on https://jira.atlassian.com/browse/JRASERVER-64106 or https://jira.atlassian.com/browse/JRASERVER-23148

            Assignee:
            Unassigned
            Reporter:
            Murakami [Atlassian Support]
            Votes:
            8 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: