Bulk operation acting weird

[purchasing mobileye.com]

Hello,

We noticed a weird behavior of the Bulk Operation option.

Before making the change of several issues with Bulk Operation Progress, it showed us that x issues are going to change, but during the process of change, it showed us that more issues are going to change (x+y).

After the bulk change, we checked how many issues have updated within the last 5 minutes, we have seen that only x issues have updated, not x+y issues.

Do you have any idea why it presented us different number of issues before and after the change?

Thanks,

Bar

[rambabu patina · Accepted solution]

On Bulk operation, If the issues have sub-tasks, these are included in this count, even though they are not updated.

For more details you can refer the Bug already raised in atlassian!

[purchasing mobileye.com]

Hi Rambabu,

Thank you very much!

[Jobin Kuruvilla [Adaptavist]]

What operation did you do? Was it the subtasks that were getting affected during the bulk edit? For example, a move operation will affect the subtasks as well.

[purchasing mobileye.com]

Hi Jobin,

We changed the Workflow of spcific issue type. That's means that the changed was done only for issues that their statuses were different than the new statuses in the new workflow.

As far as I know, if I'm changing the workflow of one issue type that's not effected other issue types such as sub-tasks, right?

Thanks,

Bar

[Jobin Kuruvilla [Adaptavist]]

It shouldn't, that's right. I am not sure if there are external configurations that potentially changes their subtasks will end up in the count or not but I haven't observed it myself.

[Vishnukumar Vasudevan]

Sounds like an indexing issue.  Do you wanna try a full re-indexing ?

[purchasing mobileye.com]

Hi Vishnukumar,

That's what we thought and we will do re-indexing.

But our question is how many issues were really changed? if it wrote bigger number than the original, what is the effect? maybe there are issues that were changed in this bulk change and we don't know?

Thanks,

Bar