Generate subtasks based on user input

[Josh Noren]

I am trying to create subtasks based on a form input. Ideally once a user submits a form within a project, they select from a list of software applications needed. Then from the software applications needed, subtasks within the master ticket are created. 

If not possible, I am also trying to setup automation based on a manual action. The helpdesk would hit the action - select each app from a check list. These apps are stored as smart values at this time. For each smart value selected, create a subtask for it. 

[Ste Wright]

Hi @Josh Noren 

This should be possible via Automation - but can I confirm...

• Is this a Jira Work Management form, or Jira Service Management?
• Is the form field attached to a Jira custom field? Or is it only available on the form?
• How have you stored the apps as a checklist/smart values within the manual action at this point?

Ste

[Josh Noren]

So sorry for the lack of details. I have been tasked to create this workflow with 0 Jira experience so I am learning on the fly. 

This is a Jira Service Management form. 

I think the form field is only attached to the custom Jira form since I haven't done anything else with it. It ONLY exists in the form I suppose.

The apps are currently just stored in the checklist itself. Sounds like there is a better place to put them?

Thanks so much

[Ste Wright]

Hi @Josh Noren 

It is possible, but it's a workaround.

There's a detailed answer I posted for this on this question, but in summary:

• You need to use entities from the Form in the Automation Rules; you can find the form entities using this free app
• There's an issue properties smart value which allows you to access this information, and use it in the Rules
• With this information, you could create an IF/ELSE rule based on form options

There's also some useful information on this question also

---

This will require a lot of trial and error though.

Your alternative is to create the field in Jira, and link the form field to it. That way you can use the Jira custom field for the rule, which would be significantly easier.

Ste