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

Jira throws Javascript error while loading large number of versions

XMLWordPrintable

      Issue Summary

      When a board is configured to load large number of versions, Jira will throw following Javascript error:

      Cannot read property 'key' of undefined

      For Firefox, the error will be:

      Exception: TypeError: t.project is undefined

      Environment

      • Jira 8.2.3
      • Jira 8.3.1

      Steps to Reproduce

      1. Use Data Generator to create 400+ versions associated with issues from multiple projects.
      2. Create a Kanban board with a complex filter. Eg: 
        Project = "Sample Kanban Project" OR "Team" = MyTeam1 ORDER BY Rank ASC
      3. Save the filter and access the board.

      Expected Results

      The board loads all the versions from the projects and no Javascript error shown.

      Actual Results

      Following Javascript shown when users clicked on the Versions panel and no versions are shown:

      TypeError: Cannot read property 'key' of undefined
at t.sort (http://jira.megatron.com/vicky/s/9f56a5d58c111bc9e717d7de0ec9a795-CDN/ja95af/802003/7d70430a169e8519cad06ce4e13e018c/c4326ed06a07e0809f98015721255e8e/_/download/contextbatch/js/gh-rapid-work,jira.project.sidebar,atl.general,jira.global,com.atlassian.jira.projects.sidebar.init,greenhopper-rapid-non-gadget,-_super/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-MY:2144:1799)
at Array.sort ()
at t.getUnreleasedVersionList (http://jira.megatron.com/vicky/s/9f56a5d58c111bc9e717d7de0ec9a795-CDN/ja95af/802003/7d70430a169e8519cad06ce4e13e018c/c4326ed06a07e0809f98015721255e8e/_/download/contextbatch/js/gh-rapid-work,jira.project.sidebar,atl.general,jira.global,com.atlassian.jira.projects.sidebar.init,greenhopper-rapid-non-gadget,-_super/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-MY:2144:2002)
at Object.n.renderVersions (http://jira.megatron.com/vicky/s/9f56a5d58c111bc9e717d7de0ec9a795-CDN/ja95af/802003/7d70430a169e8519cad06ce4e13e018c/c4326ed06a07e0809f98015721255e8e/_/download/contextbatch/js/gh-rapid-work,jira.project.sidebar,atl.general,jira.global,com.atlassian.jira.projects.sidebar.init,greenhopper-rapid-non-gadget,-_super/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-MY:3209:2046)
at Object.n.updateView (http://jira.megatron.com/vicky/s/9f56a5d58c111bc9e717d7de0ec9a795-CDN/ja95af/802003/7d70430a169e8519cad06ce4e13e018c/c4326ed06a07e0809f98015721255e8e/_/download/contextbatch/js/gh-rapid-work,jira.project.sidebar,atl.general,jira.global,com.atlassian.jira.projects.sidebar.init,greenhopper-rapid-non-gadget,-_super/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-MY:3209:1842)
at Object.G.setVersionData (http://jira.megatron.com/vicky/s/9f56a5d58c111bc9e717d7de0ec9a795-CDN/ja95af/802003/7d70430a169e8519cad06ce4e13e018c/c4326ed06a07e0809f98015721255e8e/_/download/contextbatch/js/gh-rapid-work,jira.project.sidebar,atl.general,jira.global,com.atlassian.jira.projects.sidebar.init,greenhopper-rapid-non-gadget,-_super/batch.js?agile_global_admin_condition=true&baseurl-check-resources=true&flexboards=true&healthcheck-resources=true&jag=true&jaguser=true&locale=en-MY:2971:6364)

      Workaround

      Reduced the number of versions retrieved by the board, by adjusting its JQL.

            [JSWSERVER-20183] Jira throws Javascript error while loading large number of versions

            Moses Thomas added a comment -

            Dear Atlassian,

            Please also add affected version 8.5.1

            Kind regards,
            Moses

            Moses Thomas added a comment - Dear Atlassian, Please also add affected version 8.5.1 Kind regards, Moses

            Dmytro Borshchov added a comment -

            pastoraznar.francisco Sure, the version would be mentioned in fixed versions.

            Dmytro Borshchov added a comment - pastoraznar.francisco Sure, the version would be mentioned in fixed versions.

            Paco Pastor added a comment - - edited

            Will this ticket be updated if you backported this solution to the current Enterprise release version (8.5.X)? 

            Best regards.

            Paco Pastor added a comment - - edited Will this ticket be updated if you backported this solution to the current Enterprise release version (8.5.X)?  Best regards.

            Paco Pastor added a comment -

            We've detected this problem in production -> 8.5.1. Should't be solved in a new release of this enterprise version rather than in a completly new version like 8.9.0?

             

            Best regards.

            Paco Pastor added a comment - We've detected this problem in production -> 8.5.1. Should't be solved in a new release of this enterprise version rather than in a completly new version like 8.9.0?   Best regards.

            Mykola Vysochyn added a comment -

            Our production environment is also impacted by this issue - 8.5.1. Is there any solution or workaround?

            Mykola Vysochyn added a comment - Our production environment is also impacted by this issue - 8.5.1. Is there any solution or workaround?

            Joshua McKinnon added a comment -

            We are also impacted by this in production - Jira 8.2.2 (with a security mitigation in place until we go to 8.5.3). We have 800+ versions in our version table and 23 total projects. A board that uses a JQL query against all projects triggers this issue. Limiting it to a specific set of projects works around the issue.

            Joshua McKinnon added a comment - We are also impacted by this in production - Jira 8.2.2 (with a security mitigation in place until we go to 8.5.3). We have 800+ versions in our version table and 23 total projects. A board that uses a JQL query against all projects triggers this issue. Limiting it to a specific set of projects works around the issue.

              dborshchov Dmytro Borshchov
              vshanmugam Vicknesh Shanmugam (Inactive)
              Affected customers:
              7 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: