Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,498
Community Members
 
Community Events
184
Community Groups

Will automation rules work between Team managed and Company managed projects

Tejashree S
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Mar 27, 2023

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?


2 answers

1 accepted

1 vote
Answer accepted
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 27, 2023

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_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 27, 2023

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
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Mar 27, 2023

Thank you for the info.

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 27, 2023

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events