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 have two different issue types, both sharing the same field (lets say "labels"). What I want is in JIRA automation, to have a rule where if a label is added in IssueType1, that it will check if that label value/content exists in an issue under IssueType2, and then take action if true.
Basically comparing the values of two of the same custom field, but in two different issue types. I know you can pull the contents of the field in JQL through {{issue.field name}}, but I wasn't sure how to use syntax to compare the same field name to itself, but for different issue types. If this is possible, I would assume if you had multiple labels to compare, you could change it from an equals to a contains statement?
Thanks!
Hey there Kyle!
I guess a semantic thing to note is that fields are added to specific issues and not issue types so that might help a little.
So the use case here is if an label = "database" is added to an issue with type Bug, you want to check if the label "database" exists as a label for any "Improvement" issue?
It's a little tricky but you can:
Hope that helps!
Cheers,
Mark C
Thanks for the help! Unfortunately this would be on the server version of JIRA, and to my knowledge, the "lookup issues" action is currently only available in JIRA cloud, not server :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Update - I got it to work to an extent using if else statements in JQL through JIRA automation, however it does NOT work properly if you have multiple tag values under labels, as it interprets those as spaces when comparing. The solution seems that it would work using the advanced compare condition using the contains method, so something like
If
{{issue.labels}} // (for issue type 2)
CONTAINS
{{triggerIssue.labels}} // (for issue type 1)
Then
Execute action
What might be happening is that using {{issue.labels}} is also selecting the trigger issue type. I have a "For" statement preceding that selects Issue Type 2 before that If statement though.
Is it possible to do something like {{issue.<issuetypename>.<field>}} ?
Like {{issue.Type2.labels}} ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Kyle Lefton did you ever find a full answer to this? I have had a similar issue. i have used zapir to bring epics and stories in to Jira and I now want to find a way to link the stories to the epics the stories have customer field that the same as the epic name. but I can find a way of creating the right trigger
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.