The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Request Type

František Vůjtek
Contributor
May 8, 2023

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

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
František Vůjtek
Contributor
May 8, 2023

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

František Vůjtek
Contributor
May 8, 2023

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.

0 votes
Frederik Vantroys
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
May 8, 2023

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.

František Vůjtek
Contributor
May 8, 2023

Hey, both of them are company managed.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events