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
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
I want to link the 'Trigger issue' to my release ticket. How do I specify the ticket I want to link to. Previous versions of the Automation tool seem to allow a field to enter the issue to link to.
Trigger issue field changes -> Check it meets the criteria in my filter -> Link the Trigger issue to an issue I specify.
Per the docs:
Use smart values here: Yes
Links an issue to another by selecting the link type and the issue to link.
You can link to the issue that triggers the rule, the current issue on a related issues branch, a smart value or an issue key.
If I got it right you just want to set a specific issue to be linked, always the same.
In this case, I just tested it and you can type the issue key in the box and it works. It's not very clear from the interface, to be honest.
Of course, you can even use a smart value if you need it to be more dynamic
I hope this helps
Release tickets have a version number x.x.x.x in the title. They also have this number in
Dev tickets are in separate projects. They are tagged with the first three numbers. I have those tickets in filters, which change depending on the version that's going out.
All those matching dev items need to be linked to the Release ticket for better visibility of the payload, like in Timeline/Plan view.
I will try the hardcoded approach first. Then later, I'd like to figure out how to do it dynamically as the numbers increase with somewhat regular predictability. Thanks all. I can mark this closed as my initial thought was to try the hardcoded approach, first.
You're going to have to be more specific - you can approach this in lots of ways, depending on which ticket is running the rule, and where the other issues are in Jira.
Which issue are you specifying? Is the release ticket what you're running the rule off of?
You could use a lookup table if you have a specific list you're maintaining, or you can 'hard-code' it, or you can store any of the issues as a variable and re-use it in the rule branches...
The trigger is from the Dev project issues' field change meeting filter requirements.
The action is the 'Link issue' to an issue in a separate project.
Will try the lookup table approach next, and see how to build that list up-front, but for the time being the hard-coded will be ok.