Looking for insight into the best way to solve this issue:
I started setting this up using the ScriptRunner Create Subtask function, but looks like I'll need to create a listener function for each option, which is not ideal. However this does appear to handle all my needs, other than I'm unsure how to code the condition to ensure it doesn't create new subtasks nor modify existing ones for values that were previously checked. Currently the Scriptrunner condition is using the following:
'My value' in cfValues['My Multi List']*.value
Any assistance would be greatly appreciated!
You will need a listener but quite a complex one because there's quite a lot of things you need to think through. It's definitely better to use a single one though, rather than one per option.
On events "issue updated" or "issue transition"
I'd run JQL to read through the existing sub-tasks for the issue and compare them with what I might be creating - any close match found, don't create it.
Last time I did this, there was a simple case - we were creating sub-tasks by component, so a simple "parent = current issue and component = <component we're thinking of creating for>" test applied.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs