Cannot create JIRA issue which contains answer to a Slack multiple choice form entry

[Jean-Michel Garcia]

I'm trying to create a JIRA ticket based on the answers from a Slack form (part of a Slack workflow). However, it throws an error if I try to use the answer to a multiple choice question.

Is this a limitation?

[Rohit Utukuri]

Hi @Jean-Michel Garcia ,

Depending on the Jira space, you are trying to the create the work item in .There might be additional mandatory fields required before the work item is created. 

Try to create a work item manually and cross verify if the data captured from the slack integration is populating data into all of the required fields.

[Jason Krewson]

This is a great place to start, does this Jira Space require certain fields to be filled out prior to creating a work item, if so are those available on the form and mandatory? 

[Jean-Michel Garcia]

Nah. I'm just adding text to the description. It succeeds without the multiple choice item added.

[Olha Yevdokymova_SaaSJet]

Hi  @Jean-Michel Garcia 

If the work item is created successfully until you add the Slack multiple-choice answer, then it is probably not a required-field issue. It sounds more like a formatting/data type problem between Slack Workflow Builder and Jira.

Multiple-choice answers from Slack are often passed as a structured value or list, while the Jira Description field expects plain text/Atlassian document format. So when you insert the multiple-choice response directly, Jira may fail because it cannot parse that value as normal description content.

A few things you can try first with the native setup:

1. Test the same workflow with a simple text field from Slack — which you already did, and it works.

2. Try adding only one selected option from the multiple-choice answer, if Slack exposes it separately.

3. If Slack allows formatting the value, convert the selected options into a plain text string before sending it to Jira, for example:
   Selected options: Option A, Option B

4. If the multiple-choice value is being sent as an array/object, avoid placing it directly into the Jira Description field.

Another approach you might consider is using Smart Forms for Jira, developed by my team, when the form data needs to land in Jira in a more controlled way. Instead of collecting the request in Slack and then fighting with how Slack passes multiple-choice answers, you can collect the structured input through a reusable Smart Form that created work items in dedicated project and flexible field mapping set up options.

For example, you can create a reusable request form with dropdowns, checkboxes, multi-choice fields, attachments, and validation rules. On submission, the form can create a Jira work item with the selected values already mapped into the right Jira fields or added into the description in a readable format. Smart Forms templates can also be reused across projects, so you do not need to rebuild the same request form for every team.

If Slack is still the preferred entry point, you could share the Smart Form link in Slack or trigger it from a Slack workflow message. That way, users still start from Slack, but the actual request data is collected in a Jira-ready format.

[Nicholas Bouchard]

This is probably a field type mismatch. Slack's form builder treats "Multiple choice" and "Dropdown" as different answer types. Dropdowns output plain text while Multiple Choice outputs an array of values. Jira's ""Create an issue"" step expects a string, so the array from Multiple Choice breaks the request.

If that question only ever needs one answer, try changing the field to Dropdown rather than Multiple Choice. If you do need multiple selections, you'd need to use Slack's developer tools to build a custom workflow step.

Hope that helps!

[Jean-Michel Garcia]

Thank you Nicholas. That's what is happening. It seems likely a bug or oversight to me. I was hoping someone could point me to the right place to report and get this fixed?

[Nicholas Bouchard]

I think this workflow step is actually run by Slack, so if you wanted this fixed or addressed, it'd be with Slack's support team.