Slack to Jira - Ticket creation

Ofir Oxenberg

Hello, 

Im trying to create a new process in my company to create tickets from Slack to Jira.

I have a mandatory field that needs to be filled when opening a ticket in Jira. 

The issue is, that I want them to be able to see only a few options from that drop-down field. 

When using the "Jira cloud - create" in the workflow, it shows the field with all its options, and that doesn't work for me. 

I remember there's a way to collect information during the workflow as a form and send it to Jira to create a ticket. I don't remember how i did it in the past and cant find information online. 

Doing it that way it allows me to create a limited drop-down and then map it out to the Jira field. 

Anyone knows? 

ashu patel_rub1iq

Creating Jira Tickets from Slack with Custom Dropdown Options

To create a Slack-to-Jira ticketing process where users see only select dropdown options for a mandatory Jira field, you have several approaches:

The Limitation with Standard Jira Slack Integration

• Using the native "Jira Cloud - create" workflow or /jira create command in Slack displays all values for mandatory dropdown fields defined in your Jira project.

• Jira's standard field configuration does not natively filter field options based on the workflow or user.

Solutions to Restrict Dropdown Options

1. Custom Field Contexts in Jira

• In Jira Cloud, you can limit dropdown options by creating separate "contexts" for your custom field. Each context can be mapped to specific projects or issue types, which limits which dropdown values are available depending on the context chosen in Jira.

  • Go to Jira Settings → Issues → Custom fields.

  • Find your dropdown field, click the menu, then select Contexts and default value.

  • Create a new context, select projects/issue types, and define allowed options.

• Limitation: This restricts dropdown options for specific issue types/project contexts, but when using Slack, the list still reflects what is configured for that issue type/project.

2. Using Jira Forms (Built-in or Add-ons)

• Jira Cloud offers built-in Forms (previously “ProForma”) which let you design custom forms mapped to Jira issue fields.

  • Forms can feature limited dropdowns distinct from the Jira field, allowing you to present only certain options to users.

  • Once a form is filled, the selections can be mapped to hidden or more complex Jira field values.

  • These forms can be shared via a URL—including in Slack—so users fill them in a controlled environment, and on submit, the ticket is created in Jira with mapped values.

• Add-ons like Smart Forms for Jira enable even more sophisticated custom forms with logic, public sharing, flexible option mapping, and more. These can fill in issue fields and restrict seen options without modifying the global field context.

3. Integrating Slack Workflow Builder + Webhook or Form

• Use Slack Workflow Builder to create a custom workflow:

  • When users trigger the workflow, present them with a custom form in Slack.

  • Limit dropdown values in this form to your required subset.

  • Submit their choices to a middle-layer (like a webhook or automation tool) that converts form answers to a Jira ticket via the Jira API, mapping the restricted values to the appropriate field in Jira.

• Benefits: Full control over the options and the user experience.

Recommended Process

1. Determine if Standard Forms Work: If your environment supports Jira forms (via Jira Service Management or Business Projects), create a form with a restricted dropdown and embed/share it in Slack.

2. For Further Control: Use an add-on (like Smart Forms for Jira) or build a Slack workflow that collects user input, provides the restricted dropdown, and passes data to Jira.

3. Map to Jira Field: Ensure your method maps the form-selected value to the correct Jira custom field when the ticket is created.