Want to streamline how your team creates Jira issues from Discord? You can customize which fields appear in the /create issue slash command and modal dialog to fit your workflow perfectly. Less clicking, more doing! 🚀
Before You Start
Quick checklist to make sure you’re ready:
- âś… Admin access to your Discord for Jira General Settings
- âś… At least one Jira project connected to your Discord server
- ✅ Understanding of your team’s most-used Jira fields
Step 1: Access Issue Creation Settings
Let’s get to the configuration screen where all the magic happens.
- Navigate to General Settings
- In Jira, click the Settings gear icon
- Select Apps from the menu
- Under Discord for Jira, click General Settings
- Switch to Issue Creation Tab
- Click the Issue Creation tab (it’s right next to General Features)
- You’ll see your connected Discord server and current field configuration
đź’ˇ Quick tip: These settings apply to all projects connected to your Discord server - think server-wide consistency!
Step 2: Understand Your Field Options
Before we start customizing, let’s understand what each setting does:
Core Fields (Always Required)
- Project - Users select which Jira project (non-editable)
- Issue Type - Bug, Task, Story, etc. (non-editable)
- Summary - Issue title (non-editable, always required)
Configurable Fields
Each field can be configured with three options:
- Command Parameter âś… - Field appears in the
/create issueslash command - Show in Modal âś… - Field appears in the detailed creation dialog
- Required Field âś… - Makes the field mandatory for issue creation
💡 Smart behavior: If a required field isn’t available in a specific project, users can still create issues. Modal dialogs will show a helpful warning but won’t block issue creation.
Step 3: Available Fields Reference
Here’s a complete list of fields you can configure for Discord issue creation:
Core Fields (Always Available)
| Field | Type | Description | Notes |
|---|---|---|---|
| Project | Select | Choose which Jira project | Required, non-editable |
| Issue Type | Select | Bug, Task, Story, etc. | Required, non-editable |
| Summary | Text | Issue title/summary | Required, non-editable |
Standard Jira Fields
| Field | Type | Description | Best Used In |
|---|---|---|---|
| Assignee | User | Who should work on this issue | Command (autocomplete dropdown) |
| Reporter | User | Who reported this issue | Command (autocomplete dropdown) |
| Priority | Select | Critical, High, Medium, Low | Command (proper dropdown) |
| Parent | Select | Epic or parent issue | Command (searchable dropdown) |
| Description | Textarea | Detailed issue description | Modal (multi-line support) |
| Due Date | Date | When issue should be completed | Command (date picker) |
| Labels | Multi-select | Issue tags/categories | Command (single selection) or Modal (comma-separated) |
| Components | Multi-select | Project components affected | Command (single selection) or Modal (comma-separated) |
| Fix Versions | Multi-select | Target release versions | Command (single selection) or Modal (comma-separated) |
| Attachment | File | File uploads | Command only (not supported in modal) |
đź’ˇ Note: Only the standard Jira fields listed above are available for Discord issue creation. Custom fields are not currently supported.
Field Type Compatibility
| Field Type | Command Parameter | Modal Dialog | Notes |
|---|---|---|---|
| Text (single line) | âś… Good | âś… Excellent | Perfect for free-form text |
| Textarea (multi-line) | âś… Good | âś… Excellent | Works in both |
| Select (single) | ✅ Excellent | ⚠️ Limited | Dropdown vs text-only input |
| Multi-select | ✅ Good | ⚠️ Limited | Single selection vs comma-separated text |
| User | ✅ Excellent | ⚠️ Limited | Autocomplete vs manual typing |
| Date | ✅ Excellent | ⚠️ Limited | Date picker vs text format |
| Attachment | ✅ Only option | ❌ Not supported | Discord limitation |
⚠️ Important: Modal dialogs only support text inputs. Select fields, date pickers, and user autocomplete are emulated as text-only fields in modals, making command parameters much better for these field types.
⚠️ Note: You can configure up to 5 fields maximum to show in modal dialogs due to Discord limitations.
🔧 Required Field Behavior: If you mark a field as “Required” but it’s not configured in a specific Jira project, users can still create issues for that project (to avoid blocking them). Modal dialogs will show a warning that the field isn’t supported for the selected project.
Step 4: Test Your Configuration
Time to see your customization in action:
- Save Your Changes
- Click Save Changes at the bottom of the page
- Changes apply immediately to your Discord server
- Test the Slash Command
- Go to Discord and type
/create issue - Verify your chosen fields appear as command parameters
- Go to Discord and type
- Test the Modal Dialog
- Complete the slash command or click Submit
- Check that your modal fields appear correctly
🎉 Success? Your team now has a customized issue creation experience that matches your workflow!
Troubleshooting / FAQ
🤔 Field not appearing in Discord? Check that the field is available in your Jira project’s create screen and that you’ve saved your changes.
🤔 Too many command parameters making
/create issueclunky? Move less-critical fields to “Show in Modal” only - keeps the command snappy while preserving access to detailed fields.
🤔 Field not showing up as expected? Make sure the field is enabled in your Jira project’s create screen configuration. Only standard Jira fields are supported.
🤔 Warning about unsupported field in modal?
This appears when a required field isn’t available in the selected Jira project. The warning is just informational - users can still create the issue without that field.
