-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
6.3.9, (17)
6.3.12, 6.4-OD-15, 6.4.4, 7.0.10, 7.2.7, 7.4.4, Archived Jira Cloud, 7.0.0, 7.2.13, 7.2.4, 7.9.2, 7.6.8, 8.0.1, 8.2.0, 8.3.2, 8.5.9, 8.13.1
-
6.03
-
40
-
Severity 3 - Minor
-
9
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
When performing a bulk operation on issues, the count for the issues will be inflated by the number of sub tasks those issues have (even if the sub tasks aren't selected for the bulk operation).
This is a display problem, as the sub tasks themselves aren't changed (unless they were selected in the bulk operation).
Steps to Reproduce
- Create an issue (TEST-1, and a sub task for that issue (TEST-2
- Find the issue with JQL (KEY = TEST-1) and bulk edit that one issue
Expected Results
The message above the progress bar shows one issue is being edited.
Actual Results
The message above the progress bar shows the number of issues being edited plus the count of subtasks those issues have (although only the issues selected are being edited).
Bulk Operation:
Message:
Notes
Jira is incorrectly including the sub tasks as a part of the calculation.
Workaround
There is no workaround for this issue.
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
- mentioned in
-
Page Failed to load
[JRASERVER-42436] Bulk Operations on Issues with Sub Tasks will show the wrong progress count
I just noticed the related Jira Cloud issue logged as JRACLOUD-42436 was resolved an hour ago. The currently latest comment (from 19 Feb) says:
The fix for this bug should be available to all the customers by end of next week.
So obviously the fix is known and implemented for Cloud—is it as simple as dropping it more-or-less in place into Server?
(oh, and by the way—Server 8.13.2 still exhibits this bug.)
You've been "Gathering Impact" for over two years. Here's the impact...
"User performs bulk-update. User sees much larger number than what he was expecting. User submits trouble ticket to the help desk. Help desk informs user that it's nothing to worry about. User later forgets that it's nothing to worry about and six months later submits new trouble ticket for strange, worrying number; saying that he kind of remembers something about it but just wants to 'be sure'."
It simply CANNOT be a difficult fix, so fix it!
I'm not sure if this has already been documented, but I was doing some bulk operations today and was updating 389 (both issues and sub tasks) and was told that 519 issues were being updated. Since I was purposly updating both issues and sub tasks I thought that the count would match in this instance, but I was wrong.
Here is the query I was using: project = PROJECT AND status = "Rolled Out" AND status changed to "Rolled Out" during (2019-08-01, 2019-10-15)
I was about to open a support issue on this but thought I would check for anything existing; glad I did! I have been seeing this strange activity from 6.4 all the way up to my current Jira Software version, which is 8.1.0
Thanks, Dave. I manage multiple large Jira instances (Cloud and Server) and users pretty frequently see the bad counts and then worry that they have accidentally updated the wrong set of issues. Sometimes they then submit support tickets to us about it and we have to let them know it's a known bug (for years!).
Confirmed 9.17.2 exhibits this behavior.
Was alarming, since I thought I accidentally modified a larger number of issues than I expected (26 became 126). 🥲