Create subtasks matching each value of mutliselect or checkbox field

[Charles Albrecht]

We have a multi select or checkbox field with a number of possible options. Consider this to be something like "Impacted Functions":

Impacted Functions:

1.   UI
2.   Data
3.   Passwords
4.   Environment
5.   (etc)

We would like a single automation rule which (when invoked) will create a distinct subtask for each of the checked values without hardcoding the list of possible values in the rule itself. 

ie: checking the first three items above - and invoking the rule - would result in three new subtasks:

• Review Impacts to UI
• Review Impacts to Data
• Review Impacts to Passwords

Or, by the same token, against the "Affects version/s" field, (for an example where the possible values is large and frequently changing), new subtasks for:

• Test upgrade from 1.0.0
• Test upgrade from 1.0.1
• Test upgrade from 1.0.2-beta2
• Test upgrade from 1.0.2-rc1

Is this something that's currently possible and I'm just not seeing it?

[Joshwa Marcalle]

Hi Charles, 

Scriptrunner or Automatic subtasks professional

The first one needs coding, the second one does not. 

Hope this helps

Josh

[David Fischer]

You could also easily achieve it using the JMWE app.

[Tim Martin]

@Charles Albrecht, you could probably do dynamic sub-task creation using the Scriptrunner or Power Scripts add-ons (which also integrate into Automation rules). I've found a few complex tasks where I offload functionality to the script engines, but still want to use Automation's triggers, audit log, etc.

[andreas]

Hi Charles,

Unfortunately we don't support this use-case yet in Automation for Jira: https://codebarrel.atlassian.net/browse/AUT-81

For now the only way around this, would be to pretty much 'hard-code' the values as you mentioned, with a bunch of if/else blocks, which isn't ideal.

We've got quite a few higher priority items in our backlog, so it will be quite a while before we'll get to this, but we'll leave a not here when we do!

Cheers,
Andreas