Let's assume that we have three components (design, art, tech). I would like to copy parent components to the newly created issue only if parent components don't include art or tech component. What's the best way to create one IF step in the automation so it's easy to extend the list of components?
Hi @Mateusz Janczewski - Hope you are doing well. I think the best way to implement if you just want the "Components" to get filtered -
This way you can add remove components easily. Other way would be to use a JQL if you want to add other conditions in one go.
Thanks,
Bharat
@Bharat Kalia @Jack Brickey thank you for answering quickly :)
So, to clarify the intent - I'm trying to copy components to create an issue ONLY if Parent Components don't contain a certain value. To make it easy to extend, I'm trying to solve it through regular expression if the method I'm using doesn't work (screen).
Any thoughts on this?
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.
hi @Mateusz Janczewski - Can you please try using something like this in the condition -
You can replace the "Second value" with your components list... One way to check is print the "{{issue.parent.components.name}}" in a log action within the rule so that you can get an exact value.
Hope this will solve your problem.
Thanks,
Bharat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey, thank you for helping. Not sure why, but when I swapped the logic it started working :D
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Glad, I could help. Cheers!
Thanks,
Bharat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Mateusz Janczewski , it seems that you have a rule already create but maybe concerned about scaling this rule? If your condition is one of exclusion, meaning you only want to execute the action, if the parent doesn't include a list of components, then it should look something like below. If I am missing your point here, could you please elaborate, and maybe even include your current rule?
branch for parent
Issue fields condition components does not include x, y, z
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.