Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-65062

Bulk change shows incorrect number in Bulk Progress page when issues to change is larger than 1000

      When you try to change more than 1000 issues, the JIRA system limits it to the first 1000. This is ok, and the number "1000" is reflected in all bulk-change wizard pages, except in the Bulk Operation page, after you confirm.

      Steps to repro:

      • Use Bulk Change on a query result of > 1000 issues
      • Change something (unselect "send mail", it will make this very slow) (I changed Assignee, didn't test with other changes)
      • Confirm your change
      • You will see something like in the screenshot. My selection was 2300+ issues large, the first time it showed 1028 issues, the second batch showed 1006 issues. I could not verify whether that was the number of issues actually changed, or whether the number was simply wrong.

            [JRACLOUD-65062] Bulk change shows incorrect number in Bulk Progress page when issues to change is larger than 1000

            I have the same problem! it shows me more issues in the processing then I filtered and put for the bulk change.

            Martin Junek added a comment - I have the same problem! it shows me more issues in the processing then I filtered and put for the bulk change.

            Test1 Jun added a comment -

            I have the same issue, not only when bulk changing 1000 issues, but any numbers, for example, bulk changing 466 issues, the progress shows changing 527 issues.

            I need to know what the extra 61 issues are being changed.

            Test1 Jun added a comment - I have the same issue, not only when bulk changing 1000 issues, but any numbers, for example, bulk changing 466 issues, the progress shows changing 527 issues. I need to know what the extra 61 issues are being changed.

            Dylan added a comment -

            Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage.

            Cheers,

            Dylan - Service Enablement @ Atlassian

            Dylan added a comment - Due to an extended period of inactivity and low interest this bug has been auto-closed. If you’re still experiencing this issue, please comment and we’ll re-open to triage. Cheers, Dylan - Service Enablement @ Atlassian

              Unassigned Unassigned
              3681d549f03f Abel Braaksma (admin)
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: