I'm creating a Rule for a specific project (ie id 11700) .
In one of the filters I want to check if the related issues meet meet some requirements...
The problem: JQL must filter issues from other projects, but internally the automation injects the "project Id" into the JQL.
This behavior does not occur when set the rule as global.
desired behavior : Im looking for Related ISSUES! Can be any project!!
probe JQL::
issue in linkedIssues ("ERP-123", "is dependent on")
Hi Alexandre,
This is the expected behaviour (e.g. in larger organisations this sort of compartmentalisation helps keep divisions from seeping into each other).
If you'd like your rule to access multiple projects in this way, but only trigger on a single project's issues, you can set your project to global and add a compare condition at the start that checks if `{{issue.project.key}}` equals your project's key.
Cheers
Huw
Developer at Code Barrel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.