Hi,
I have two projects. A Service Management project (SM), open to anybody.
And a Jira Software project (JS), where fewer people can create tickets. I created an automation so that when a ticket has been raised in the SM project, a ticket with the same fields is created in the JS project, where the developers manage it.
I now want it (the SM ticket) to change status when the JS ticket changes status.
To do that I created two automations:
1. to create the new ticket and link them (Re-fetch issue data AND Link issue to/relates to: Trigger issue.) The creation works fine, the linking doesn't.
2. to transition the SM ticket when the JS ticket transitions. (When JS issue transitioned from Status to Status/ If Project = JS/ Branch: Fir Linked issues (relates to)/ IF Project = SM/ Then transition issue to Status.) This doesn't work, I suspect because the linking didn't in the first step.
What am I doing wrong?
Thanks
HI @Daniel Gavrila , welcome to the community.
Could you please add some screenshots of your current rule configuration to help analyze it better why issue linking is not working.
Thank you!
To create a new issue and link it to the trigger issue is usually one simple action:
Just make sure, the rule actor has all the necessary permissions in both projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have created the corresponding ticket, the issue is with the linking. The first is the automation I used for step 1. The second is for step 2.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you.
To see if your other rule is working correctly, just manually link it.
As for your first rule: set the link to the trigger issue in the same action you create the issue. See my screenshot above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you so much, @David Friedrich !
Adding the link into the first automation solved the problem. And I didn't have to do anything on the second, which seemed to be correct. Thank you again!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.