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,551,708
Community Members
 
Community Events
184
Community Groups

Im so confused...

Loosing my mind right here.

The Jira automation is trying to kill my last patience.

I have created the rule which is creating a new issue in another project and it can't pair a request type on it -.- so i said to my self OK, i will add it in another automation in the second project. But there is NO trigger which would trigger the action after the issue was created with that previous automation in other project. 

Simply it wasn't taking any action. So i have create a ticket manually via create button on the bar in jira and it was working.. -.-

So, the jira automation is making a difference between ticket which has been created via automation and the tickets which have been created manually. Thats no sense. I have spent last 4 hours figuring why my triggers and automations are not working and this is the reason. 

Tell my why Jira? Tell my why..

2 answers

1 accepted

1 vote
Answer accepted

Someone should check it. This is definetelly a bug. 


When you will set a trigger When issue is created, it will do NOTHING. When the automation created the issue from other project. 

But if you will create it manually, it works. There must be something wrong.Snipaste_2023-05-08_14-26-51.pngSnipaste_2023-05-08_14-27-27.pngSnipaste_2023-05-08_14-27-49.pngSnipaste_2023-05-08_14-28-02.png

Ok so i have the solution.. -.- It because i didnt have checked the rule can be fired after that previous rule has been shot from another project. 

-.- 

I hate my self and maybe little bit jira for this.

Thank you and have a nice day.

Maybe it has something to do with the projects being company managed or not ?

You can make automation rules in a project but also general "accross" projects.

Hey, both of them are company managed.

Suggest an answer

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

Atlassian Community Events