Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-41156

Bulk Action page is very slow for large amount of issues

      Summary

      Doing multiple Bulk Action operations is resource intensive and can contribute to overall performance problem, such as increased in page load times due to JIRA consuming CPU resources.

      Steps to Reproduce

      1. In Issue Navigator, search a set list of issue using a JQL Query
      2. Click on Tools > Bulk Change | all (X) issue(s) button

      Expected Results

      It's expected to have the result returned faster

      Actual Results

      The time it took to generate the result was relatively long due to evaluating permission for each issues on the bulk change action.

            [JRASERVER-41156] Bulk Action page is very slow for large amount of issues

            Hi Bo, 

            On the contrary, thank you so much for helping us narrow this down! This ticket didn't have a lot of specifics and wasn't verified, so it makes sense to think this was the cause. Our apologies for any confusion, we're currently working on curating our backlog and verifying all of our bugs. Since we don't believe this is a bug at this time, I've written the following article instead for this issue to avoid confusion in the future: Bulk editing a large number of issues is slow in Jira.

            And we will go ahead and resolve this ticket as 'Not a bug'. If this needs to be reopened, we can gather more specific information and have our support team troubleshoot and replicate this issue before reopening it.

            Daniel Ponzio,
            JAC Champion

            Daniel Ponzio added a comment - Hi Bo,  On the contrary, thank you so much for helping us narrow this down! This ticket didn't have a lot of specifics and wasn't verified, so it makes sense to think this was the cause. Our apologies for any confusion, we're currently working on curating our backlog and verifying all of our bugs. Since we don't believe this is a bug at this time, I've written the following article instead for this issue to avoid confusion in the future: Bulk editing a large number of issues is slow in Jira . And we will go ahead and resolve this ticket as 'Not a bug'. If this needs to be reopened, we can gather more specific information and have our support team troubleshoot and replicate this issue before reopening it. Daniel Ponzio, JAC Champion

            Hi @Daniel Ponzio

            Thanks for looking into this. I have been digging a bit further into this as well. It seems like the slowness appears sometimes when data in a certain plug-in is referenced (Xray). So, I agree, it is not a general issue (at least not a major issue). It looks like Xray do a lot of recalculation when certain data is being touched on projects with a large amount of issues. My apologies to Atlassian for my initial comments... wrong recipient.

            Bo Bøgvald added a comment - Hi @Daniel Ponzio Thanks for looking into this. I have been digging a bit further into this as well. It seems like the slowness appears sometimes when data in a certain plug-in is referenced (Xray). So, I agree, it is not a general issue (at least not a major issue). It looks like Xray do a lot of recalculation when certain data is being touched on projects with a large amount of issues. My apologies to Atlassian for my initial comments... wrong recipient.

            Hello bobo2,

            I've just tested this on a vanilla Jira 7.12 instance, and was unable to replicate any slowness. I've tested transitioning, changing the priority, and adding multiple values to multiple fields at once for 400 issues. The longest bulk edit from my testing lasted 27 seconds. It could be that this is only happening on a specific field. 

            Depending on your instance, this could be caused by a specific configuration or performance issue. I would recommend troubleshooting with support to see if can be fixed, and if we can help narrow down the cause. It would be useful to know what field you are editing, and if you are experiencing any other performance issues in your instance. 

            Daniel Ponzio,
            JAC Champion

            Daniel Ponzio added a comment - Hello bobo2 , I've just tested this on a vanilla Jira 7.12 instance, and was unable to replicate any slowness. I've tested transitioning, changing the priority, and adding multiple values to multiple fields at once for 400 issues. The longest bulk edit from my testing lasted 27 seconds. It could be that this is only happening on a specific field.  Depending on your instance, this could be caused by a specific configuration or performance issue. I would recommend troubleshooting with support  to see if can be fixed, and if we can help narrow down the cause. It would be useful to know what field you are editing, and if you are experiencing any other performance issues in your instance.  Daniel Ponzio, JAC Champion

            How can you have this as a minor bug....? Bulk changes are pretty much useless as it is now... Currently trying to add a single field value to a field on 398 issues.... 6 done after an hour! 

            Any work arounds? Any settings that can improve performance of the bulk operations?

            Bo Bøgvald added a comment - How can you have this as a minor bug....? Bulk changes are pretty much useless as it is now... Currently trying to add a single field value to a field on 398 issues.... 6 done after an hour!  Any work arounds? Any settings that can improve performance of the bulk operations?

            On "Step 2 of 4: Choose Operation", when choosing Edit Issues, and pressing Next, I get the following delay times before showing the page "Step 3 of 4":

            For 1 selected issue: 10 seconds.
            For 5 selected issues: 51 seconds.
            For 10 selected issues: 97 seconds.
            For 20 selected issues: 193 seconds.

            The scaling appears to be linear. We are running JIRA v6.3.13 and JIRA Agile v6.3.13.1.

            Please help. All other steps in the Bulk Edit operation are reasonably quick. But the step 2 -> step 3 transition makes Bulk Edit is practically unusable. Thank you!

            Ben Robinson added a comment - On "Step 2 of 4: Choose Operation", when choosing Edit Issues, and pressing Next, I get the following delay times before showing the page "Step 3 of 4": For 1 selected issue: 10 seconds. For 5 selected issues: 51 seconds. For 10 selected issues: 97 seconds. For 20 selected issues: 193 seconds. The scaling appears to be linear. We are running JIRA v6.3.13 and JIRA Agile v6.3.13.1. Please help. All other steps in the Bulk Edit operation are reasonably quick. But the step 2 -> step 3 transition makes Bulk Edit is practically unusable. Thank you!

              Unassigned Unassigned
              pniewiadomski Pawel Niewiadomski (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: