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.
I am trying to create an automation when a bug is raised and assigned to a specific person it links to a specific story.
When I try the automation tools the only options I have for linking to is either link to the trigger or most recent issue created.
Hello @Kathryn Jenner
You can enter a smart value in that field by clicking in the space that says Trigger issue and starting to type in the smart value. After completing the smart value entry you click on the Smart value '{{... text so that it will be entered into the field.
I think I'm reading @Kathryn Jenner's question differently.
If bug is assigned to QA Person 1, then link the bug to "QA Person 1's Epic" or something like that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that is the same way I'm reading it.
We are missing information about how the rule is getting the value of the issue to which the trigger issue will be linked. It is possible that it is somehow retrieving that issue as part of the rule, in which case a smart value referencing that issue could be used.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's where I'm not following your example answer. {{issue.key}} would give you the same issue you're triggering off, which OP said they didn't want.
If it's truly a fixed, specific issue for each assignee, then wouldn't the way to go be to put in that issue key, either through IF-ELSE or a lookup table. I think the confusion may be with the interface itself (suggesting an alternate answer).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My {{issue.key}} was just an example of a smart value, not necessarily the smart value that should be used in this rule. I was trying to point out that the action is not limited to just the two options listed, and a smart value could be used to specify a different issue (if the rule is constructed such that a smart value can be used to reference the target issue). I guess I should've provided more explanation.
Without additional information about the rule I could not provide a smart value that would work for that rule specifically.
If the issue per Assignee is a fixed value that can be hardcoded, then yes, and If-Else block could be used to look at the Assignee and then link the trigger issue to an explicit issue. In the same manner as adding a smart value, you can click into the space that says Trigger Issue and start typing the issue key for the target issue.
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.
I believe you're trying to link to a specific issue (ex: ABC-123).
The UI here isn't super clear. When you initially open that dropdown, it'll only show you "Trigger Issue" and "Most recently created" as you've seen. What isn't immediately obvious is that if you click into that box and start typing a key (ex: ABC-123), there will then become an option to link to that specific issue.
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.