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
We have a rule in place to create Jiras when certain conditions are met. I would like to add a rule to automatically fill in one of the custom fields which has a drop-down list of allowed values.
What I have so far:
1. Action to create smart variable from a specific part of the issue.summary string.
2. Conditional rule to check whether a certain string is found in the issue.summary
=> If condition is met, default my custom field to a specific value from the drop-down.
3. For the "Else" condition, I want to compare the value of my smart variable to the drop-down list for that field.
=> If this condition is met, default custom field to matching value.
=> else, leave field blank.
The first 2 parts (create smart variable & set condition to choose a specific value) seem straightforward. But I'm not clear how to compare my smart variable to the drop-down list. Can someone supply recommendations, or am I on the wrong path here? Am I going to have to replicate my drop-down list in JSON?
Hi @Cristin Williams -- Welcome to the Atlassian Community!
Just to confirm, are you trying to...Compare something in the trigger issue to a list of allowable values, which is already used in a selection field?
If so, you have a couple of options:
You may want to try option #1 initially to confirm the values from the Summary extraction and selection field match as expected.
And something I just noticed...When using things like Create Variable, Lookup Table, and Advanced Branches, it is a good idea to use names which are unique and cannot be confused with a smart value (e.g., Model and model). I like to add a prefix to avoid smart value collisions, such as varModel.
Hi @Bill Sheboy. Yes, correct. I want to compare the value of the smart variable created in my first action to the list already available in a selectionfield.
It's quite a long list, which is why I wasn't in a hurry to have to hard code it as a table if avoidable. I could hard-code a few options as as a test. I haven't gotten into REST API functions, so will go learn more about that option.