Hi 05f6b86c1845,

Thanks for the detailed steps! Unfortunately, I'm not able to reproduce the bug in Jira Cloud even with these steps.

Could you please open a support ticket so that we can get more details and help you further?

Hi - thanks for your response. Definitely still happening!

1. Started with search for a specific epic's child issues using search by epic link as I'm updating components for child issues in specific epics.
2. Took note of issue count - one example had 14.
3. Selected bulk change from the meatball (meatball! love this! ) selecting all 14 issues.
4. Went to Change component, as as there are no components anywhere yet, selected 'Add to existing'
5. Confirm.
6. Bulk operation progress says 'Editing 46 issues' - that's the correct count if including all subtasks.
7. Checked subtasks - no component added (they do have a component field activated but I don't want to add a component to a subtask)
8. When going to a story with an added component, clicking component presents the search page with the correct number of issues changed - 14.

So it works correctly, it's just confusing with the incorrect bulk operation progress count.

Hey 05f6b86c1845, I tested this now in a few test sites, and it is not including the subtask count as expected. These are the steps I followed:

1. Go to the issue navigator page
2. Select the bulk change issues option from the meatball option on the top right of the screen
3. Select an issue that has subtasks
4. Select Bulk edit
5. Select the Component field and replace it with a new component
6. Press Confirm
7. The progress screen appears with the issue count excluding subtasks

Could you please confirm if your process differs from what's outlined above?

If you are getting the bug even with the above steps, you can open a support ticket where we would be happy to help further.

Hi - I'm still seeing this though - I'm adding a component to, say, 14 issues but the bulk update will show me 32 issues, including sub-tasks. However, no component has been added for sub-tasks (which is correct, as they weren't specifically available for selection). 

Hi everyone,

This is Madhusudhan from the Jira team. This bug is fixed and I confirmed the functionality to be working as expected. 

Sincerely,

Madhusudhan K

@Atlassian when will this bug be fixed? It confuses users when they bulk change issues.

Hi psilveira, 

The fix for this bug should be available to all the customers by end of next week. 

ian41 wrote:

seeing this right now, funny thing is it's adding 20 issues to the count consistently

I’d suspect that’s the total number of Subtasks contained by the parent Issues you were bulk editing—that’s where the crazy number seems to stem from.

I'm seeing this right now, funny thing is it's adding 20 issues to the count consistently - editing 958 issues - editing 978 issues on progress page.

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.