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). 🥲

Jira v9.12.10 is affected too

Jira v9.4.15 still has this issue... It freaked me out!! 

Server 8.13.13 alsso has this issue.

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!).

Hi Folks,

As a part of making sure our bug reports are as clear as possible, I've gone ahead and updated this issue to make it a bit clearer as to what's going on - and that it's a display issue only.

hfisher3, jdrao12 - Thanks for letting us know about the newer versions, I've added them (as well as the most recent release, Jira 8.2) to the affected versions list

For anyone who's seeing problems with bulk operations and there are no sub tasks, please raise a support request with Atlassian Support.

Cheers,
Dave
Atlassian Support

Hi, I'm seeing this issue in Jira 7.9.2 also. Can you please include it in the list of affected versions

Observed in 6.4.14

Observed in 8.0.1. Very disconcerting for our users.

Observed on v7.10.0

Also observed this problem on v7.3.0

This bug also occurs on Jira 7.8.2

Got a support request for this today. We're using Jira 7.4.2.
This is really confusing, please fix it.

Yes, this is very disconcerting. Happened to me again today. 

I am experiencing this too (7.3.8 - upgrade pending, but still outstanding).

We see it with Jira Server 7.5.0 and can confirm that this causes confusion here.

Experiencing the same problem. I guess we'll see a correction of this corny behavior within the next decade or so. 

This is more serious than marked because it creates confusion with every user every time a bulk edit is done.  If I'm doing a bulk edit I'm double and triple checking that I have the right query and am changing what I mean to change.  The confirmation needs to be accurate.  Ideally it would confirm that the number you selected are updated, and give additional information about any related issues that were updated.

Love this one, see it all the time (on-premise JIRA v6.4.6). Today’s best effort:

• JIRA: “Transition 13 issues?”
• me: “confirm”
• JIRA: “Transitioning 124 issues”
• me: “dude srsly”

And just to note—this Issue is almost 19 months old now.

Also seeing this in v7.0.10; extremely confusing when doing a large number of bulk changes due to field or assignee changes.

Also seen in 6.3.12 including datacenter and very confusing to our users at our Premier site.

I can confirm the behaviour mentioned in the issue's description.
Please fix it.
Thanks

I have just seen an instance where:

Steps to reproduce

1. Have one issue with 16 sub-tasks.
2. Have a query that lists this issue AND all subtasks.
3. Bulk update all 17 (1+16) issues.

Actual outcome

1. The message reads

   Editing 53 issues

No idea where this number came from.