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"
Thank you for the response Nic. I'm not concerned with boxes that may later be unchecked, so the 3rd bullet point you list can be ignored. For the other 2, what would be the best way to compare the original field values to the new?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.