nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Will automation rules work between Team managed and Company managed projects

Tejashree S

I have a project which is Team Managed. I have created an automation rule, that will execute when an issue transitions and I want to create a new issue in a Company Managed project.
The rule is not executed.

Is there any limitation that an automation won't execute between two different types of projects?

Accepted answers

Alex Koxaras -Relational-

Hi @Tejashree S and welcome to the community,

For every automation rule, there are certain limits which can be found here: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

If you make your rule global (or multiple project scoped), then you should be aware of the executions limit:

The limits for that are (for a month) 100 executions for Free plan, 500 executions for Standard and 1000 executions per licensed Premium user.

All comments

Alex Koxaras -Relational-

Hi @Tejashree S and welcome to the community,

For every automation rule, there are certain limits which can be found here: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

If you make your rule global (or multiple project scoped), then you should be aware of the executions limit:

The limits for that are (for a month) 100 executions for Free plan, 500 executions for Standard and 1000 executions per licensed Premium user.

Alex Koxaras -Relational-

And here is the link of the official documentation about execution limits https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

Tejashree S

Thank you for the info.

Trudy P Claspill

Hello @Tejashree S

Welcome to the Atlassian community!

There is not a limitation that prevents an automation rule running against a Team Managed project from creating an issue in a Company Managed project. You don't have to have the rule set as a Global rule for this case. Creating an issue in a different project is the one scenario where you can affect two projects when the rule scope is only one project.

If your rule is not operating correctly we can help you debug it. Please show use the entire rule and also show us the audit log for the rule. Also confirm that you are taking an action in your Team Managed project that will cause the trigger and any initial conditions in the rule to be met. And, the Actor of the rule must also have permissions to create issues in the destination project.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management