Incoming webhook for field value comparison

[Javid Huseynli]

Hi All,

I have a problem in automation rule, based on incoming webhook.

I have two team-managed project. Project "A" and Project "B"

In project "A" when issue created, if the value in custom field "X" is equal to the value of field "Y" in project "B", then link the issues. 

I made configurations but it doesnt work. 

Need your advice.

[Bill Sheboy]

Hi @Javid Huseynli 

Would you please clarify: what exactly is not working as you expect?

For example, you note comparing issues in different projects, A and B.  Where is that comparison happening in your rule?

And, as you note different projects: a rule looking as issues in different projects often needs to be global / multiple-project in scope.  What is your rule's scope?

Kind regards,
Bill

[Javid Huseynli]

Hi @Bill Sheboy , 

As the global rules have limits, I am trying to do it with webhooks. 

In first screenshot, you can see that I am sending webhook from project A.

In second screenshot, the rule in project B is based on incoming webhook. And there you can see the condition, if field "Corporate email" contain/equals {{webhookData.adrCorporateEmail}}, then link issue: relates to - {{webhookData.adrCorporateEmail}}. 

In logs it shows success, but issues are not linking to each other.

The point of this, when issue created in project A, find the issue(which is already created) in project B and link it.

[Javid Huseynli]

In section if field "Corporate email" contain/equals {{webhookData.adrCorporateEmail}}, then link issue: relates to - {{webhookData.adrCorporateEmail}} 

I changed the relates to from {{webhookData.adrCorporateEmail}}  to {{webhookData.key}} and it is still not linking.

[Bill Sheboy]

For project-scope rules, the only thing you can do with other projects is Create Issue or Clone Issue.  All other actions, such as linking, require a global-scope rule.

As you are trying to bypass the global-scope, rule execution limits with the REST API, you could try doing the same for the issue linking.

Please note, you may be avoiding one limit and cause exceeding another: if your total execution time (such as per hour, etc.) exceeds limits due to web requests the rules could also stop running.

[Javid Huseynli]

Well, I found the way to configure it and it works :)

[Bill Sheboy]

Just to clarify, did you find that a project-scope rule could link to an issue in another project using the Link Issue action?