Why did my bulk issues transition require two confirmations and jump from 256 to 742 issues?

Question

In the Sandbox, in order to close 256 issues, I created in my workflow a new status from All, and from that status a transition to the regular completed status.

In a bulk edit, I transitioned the issues to the new status, and in another bulk edit, transitioned the issues to the regular completed status.

In each bulk edit, I had to click Confirm twice.  In both edits, the second Confirm did not display the option to send emails.  In each of the first edits, the reported number of issues was 256.  In the second edits, the reported number of issues was 740 and 742, respectively.  The 2-issue discrepancy in the reported number of issues doesn't seem like a concern, but why the jump from 256 to 740?

Phil Bustin_7fmhjs · Answer

* How did you select the issues on the first operation and on the second operation?

I used a filter to select the issues for the first operation, and if I remember correctly, I modified the filter to specify the new status for the second operation.

* Also why did you chose to use a transitionary status instead of adding the "All" transition directly to the final status and thus doing only one bulk action ?

I had tried adding the "All" transition directly to the final status, but when I tried again after reading your answer, I saw that the "All" transition was difficult to spot because "All" and its transition arrow in the diagram view were embedded in another status and transition to the final status.  I'll make the correction.  I only see using this transition in the Sandbox; when and if I construct everything in Production, I'll omit it.

said kouzibry · Answer

Hello @Phil Bustin

Can you please provide some more information about the action you performed,

* How did you select the issues on the first operation and on the second operation ?
* Also why did you chose to use a transitionary status instead of adding the "All" transition directly to the final status and thus doing only one bulk action ?

The best practice your case would be to respect the pre-existing workflow in order to make sure all post-functions and automations are executed properly.