How to make "Advanced Issue Search Bulk Change" trigger an automation rule

[Daniel Newman]

Hi,

I have an automation rule that triggers via the "Issue Updated" Trigger. 

When amending the parent of a sub task manually one at a time, this rule triggers as expected; however, if I use the advanced issue search bulk update function to update multiple sub tasks at the same time, the rule is not triggered.

Is there something that I need to do to make the bulk update function trigger automation rules as normal or is this just the way the system works?

Thanks

Dan

[Daniel Newman · Accepted solution]

Following feedback from the support ticket raised it has been confirmed that this is a bug in the Jira Cloud software and there is not a workaround for this.

The support team have raised the bug which can be found using the link below:

https://jira.atlassian.com/browse/JRACLOUD-78204 

Please watch this for further updates.

[Daniel Newman]

Bug closed as "Not a bug" stating that automation does not support responding to bulk change operations.

The Jira support team have therefore created a feature request for this which can be found using the following link:

https://jira.atlassian.com/browse/JRACLOUD-78215

Please watch this for further updates.

[Bill Sheboy]

Thanks for the follow-up, Daniel.

[Bill Sheboy]

Hi @Daniel Newman 

Is this for a team-managed (nextgen) project?  If so, it may be related to this open defect: https://codebarrel.atlassian.net/browse/AUT-1987

If not and you are on a paid license, I recommend working with your site admin to submit a ticket to support here to investigate: https://support.atlassian.com/contact/#/

Once you hear back from them, please post what you learn so the community can benefit.  Thanks!

Kind regards,
Bill

[Daniel Newman]

Hi @Bill Sheboy 

Thanks for your response.

I am using a company managed software project so have raised a ticket for support to investigat.

I will update this ticket when I get a response.

Thanks

Dan

[Daniel Newman]

Hi @Bill Sheboy 

Following feedback from the support ticket raised it has been confirmed that this is a bug in the Jira Cloud software and there is not a workaround for this.

The support team have raised the bug which can be found using the link below:

https://jira.atlassian.com/browse/JRACLOUD-78204 

Please watch this for further updates.

Kind Regards

Dan