Is there a way to import smart values from a form into subtask

[Joanna Whitley]

I have a form that is using Checkbox (multiple selection) to ask if the end user needs supplies (7 Possible answers).  The question is created and linked via custom fields.  Now I am trying to pull the custom field values into the sub task.   I am guessing I will need to write a JSON script under the additional fields but now sure. 

 Form Name: Resource Request (RR)

Custom Field: RR=Hardware/Supplies

[Joseph Chung Yin · Accepted solution]

@Joanna Whitley -

Based on your screenshot, the form element is already mapped to an actual project's custom field.  All you need to ensure that this field is also available for your Subtask issue type in your project, then you can extract the value and populate your subtask during the issue creation action in your automation rule.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Joanna Whitley]

Thank you for your response.  The sub-tasks are being created however what I would like to see under description is the values that are being selected.  for below I would like it to say Hardware/supplies: 10-key, Broadband Car/Mifi, Keyboard, Monitor, Mouse.  and then a link back to the parent request.

Thank you

Joanna

[Joseph Chung Yin]

@Joanna Whitley -

You can simply add the smart value extraction from your parent issue's RR=Hardware/Supplies field into the Subtask's Description field.

Since the subtask is created via the automation rule, it is automatically linked to the parent issue.

Best, Joseph

[Joanna Whitley]

Again thank you but while I can manual add RR=Hardware/Supplies into the description it does not supply me with what the user selected:  Example would be if the user only needed a 10-key.  I would like the sub task to let the assignee know what was requested.

Joanna

[Joseph Chung Yin]

@Joanna Whitley -

You should be able to use the following smart value syntax to extract parent issue's checkbox field-

{{issue.customfield_10090.value}}

replace 10090 with your custom field ID

Hope this helps.

Best, Joseph