You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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..
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.