Creating a automation rule that can be accessed across multiple team managed projects.

[Jayanthi Rajagopalan]

I am having trouble in running automation rules across multiple projects. It is a simple rule, where if there is a manual trigger from a task, then a new issue (sub task) is created under the issue triggering this task.

I have tried creating this rule in 2 different ways-

• Created this rule in one project (let's call in Project1).
  • In Global administration, changed the scope of this rule to "Multiple Projects."
  • Selected Project 1 and Project 2 as the projects that can access this rule.
  • Ran this rule from Project 1-
    • Works fine
  • Ran this rule from Project 2-
    • Rule fails because it couldn't locate the Sub task ID of Project 1 in Project2.
• Created this rule under Global administration as a global rule.
  • Then, changed the scope of this rule to Multiple projects.
    • Selected Project 1 and Project 
  • Ran this rule from Project 1
    • Rule fails, seems like it is looking for a sub task ID of a different company managed project.
  • Ran this rule from Project1. 
    • Rule fails, seems like it is looking for a sub task ID of a different company managed project.

Any ideas as to what might be happening here?

[mruttan]

The issue is that each project's tasks are seen as different 'issue types' in the back end.  I recently solved a similar type of issues using the "Same issue type as trigger" and "same project as trigger" this eliminates the need to specify the issue type and project.  

Hope this helps!

[Laurie Sciutti]

Hi @Jayanthi Rajagopalan and welcome to the Community!  Can you provide a screenshot of the Rule?  Several things might be impacting the results (different workflows, the action selected -- Create new issue vs Create sub-task, etc.) so the advice is dependent on your Rule specifications....