Automation rule - project restriction

[Ron]

I want to create an automated rule for a status transition of linked issues.

This issue type has restriction for this transitions (should move from new -> 1st approval -> 2nd approval -> pending deletion) only 2 users can move the ticket to 1st/2nd approval.

I checked Bypass workflow conditions and permissions

and I am still getting this error in the logs - 

NO ACTIONS PERFORMED
This rule was configured with a project restriction. You can change this restriction in the 'Rule details' section.

[Alex Koxaras -Relational- · Accepted solution]

Hi @Ron 

You created a rule for an issue which lives in Project A. Then you say for its linked issues (which may live on another project) transition these issues.

If you have set up the scope of this rule to one project (project A), then this rule can't do any actions on issues in another project. So you either set this rule to be global, or you define multiple projects. Either of this action can be performed via the GLobal Automation and not the project automation.

Hope that helps!

Alex

[Ron]

Hi, Thanks for your answer both issues are from the same project

[Alex Koxaras -Relational-]

@Ron can you please paste a screenshot of the rule log?

[Ron]

[Alex Koxaras -Relational-]

@Ron you are not getting any error with this rule. The passage you copied/pasted is an informative one, hence the "i" next to it.

Your rule runs smooth. However the linked issues didn't match the conditions you specified. That's why no actions were taken:

All link types must be equal to a certain issue type (end user deletion).

Are they all the same?

[Ron]

I need to change all linked issues of type 'End User Deletion'.

Currently I have one linked issue of this type and the condition fails

[Prashant BALASUBRAMANYAN]

@Alex Koxaras -Relational- Infact Jira works as you mentioned. But I have the following requirement and question please

Issue A (Project A) is Linked to Issue B (Project B) as a depends on link. 

I would like to transition Issue A to done, when all the linked issues ( which are in other projects of course ) are closed. 

Here I am not doing any modifications on the issues of other projects, my transition is only on the Issues in Project A. Why must the rule be Global, For me here I write in project A and just do a read on other projects 

[Darryl Lee]

You can also look in the Rule details section to edit the the scope of your rule:

[Ron]

The issues are in the same project