Block Automation Rule execution on REST API Request

[Grzegorz Ostrowski]

Is there any possibility to block Automation rule execution after REST Request?
I would like to heave possibility to update Jira through REST without triggering automation rules.
Is thos possible? Anybody knows how to do it?

[Alex Koxaras _Relational_]

Ηι @Grzegorz Ostrowski ,

I don't think this is possible. I haven't done it and from what I know from this issue https://jira.atlassian.com/browse/JSWCLOUD-22713, there is also an open request for having REST API to control JA.

[Grzegorz Ostrowski]

My problem is that I would like to have option in rest request like "notifyUsers" in issue update request. Option to disable automation rule trigger only for this request change. I dont think that this ticket covers this scenario. But thanks for answer.

[Alex Koxaras _Relational_]

@Grzegorz Ostrowski the ticket I provided covers the "disable automation rule" you are talking about.

[Grzegorz Ostrowski]

Yes, I see this, but it is about disabling autmation rule permamently, not only for one request. This ticket is about ability to control Enabled switch in automation rule from rest API. Ok this could be usefull in my case but there is tiny posibility that when I disable the rules to execute my other request some user in Jira will do somethin what should trigger automation rule.

[Bill Sheboy]

Hi @Grzegorz Ostrowski 

Adding onto Alex's answer: what problem are you trying to solve by doing this?

Knowing that information may help the community to offer suggestions.  For example, perhaps instead your rule could have a trigger/condition based upon the presence of issue data, and so eliminate the need to disable a rule: instead just change the issue data.

Kind regards,
Bill

[Grzegorz Ostrowski]

I am writing integration between Jira and ERP system. I am using automation rules to send data to ERP on worklog, issue change/add. But when I send data on issue/worklog change from ERP to Jira it triggers automation rules. Sometimes automation rule is triggered before i get response on my request to Jira. For me it is difficult to handle this scenarios. Maybe there is other possibility to pass data to Jira without triggering automation rules. Of course there are webhooks, but they will be triggered by worklog/issue update through rest too.

[Bill Sheboy]

Without seeing your specific automation rule, I wonder if you can alter the trigger or perhaps add a condition on the {{initiator}} user to prevent the rule processing under those conditions.