Hey guys! Im kind of new to the Jira support platform and have been brainstorming about whats the best way to create a rule in which per affected service a seperate subtask is made.
Currently i tried this structure:
- When: value changes for 'affected services'
- For each: Smart value (advanced brancing)
{{AffectedService}}
- Affected service equals (Issue fields condition)
'service1'
- Then: create a new (create issue)
subtask in same project
When executing the workflow, the subtask is made. But when I fill in multiple affected services (for instance 3 services) the same subtask is created three times.
There has to be a mistake in the rule, any comments are appericiated :)
EDIT:
I wanted to provide some more information. Thanks again for the comments.
For clarification, on the list of 'affected services' i'm trying to filter multiple times to add different subtasks with different names.
I have been getting the error below:
"The provided smart value was unable to be resolved to an object."
Hi @Julian Adam and welcome to the community!
I'm getting the gist of what your rule is doing, but it may help to share a screenshot of the rule. Specifically, it would be helpful to see the specifics around your Branch and Create New Sub-Task components.
Thanks for your response Mark! I edited the original post, i hope this might clarify most of the details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think you need the "{{#}}" unless you're looking to "print" the results. Try setting your branch to this:
{{issue.affectedServices.name}}
Also, you shouldn't need the conditions. You should be able to have a single Create Sub-Task and do something like this for the summary:
{{ListAffectedService}}
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.
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.