-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Problem Definition
Currently, the /jira create command lacks the functionality to allow users to customize which fields are to be filled out during the issue creation process. This limitation arises from Slack's restrictions on the maximum number of fields that can be displayed within the issue creation modal. Efforts are made to select fields relevant to the project and issue type chosen by the user, yet it may not always be feasible to display all available fields for the specified issue types due to these Slack constraints. In such instances, users are presented with a warning message and advised to create the issue directly in Jira should they need to complete those fields.
As of now, the customization of fields displayed in the Slack 'Create Issue' form is governed by the fields configured in the 'Create Issue' screen for the respective issue type in Jira Cloud. It is important to note that any modifications to this screen, whether adding or removing fields, don't instantly reflect in Slack. There could be a delay before the changes in the field configuration are visible in Slack's issue creation process.
Suggested Solution
It would be beneficial to have a feature that allows configuring the form for the /jira create command on a per-project and per-channel basis.
Why this is important
By implementing this feature, issues created in Jira via Slack would be fully detailed from the outset, eliminating the need to edit the issue post-creation to add additional information not available on the Slack creation form.
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
- Gathering Interest
- relates to
-
- Closed
-
- Gathering Interest
[API-157] Customize the fields in the 'Create Issue' form in Slack
| Remote Link | New: This issue links to "Page (Confluence)" [ 1025193 ] |
+1 this would be a big, big deal for us and save our team a great deal of time.
Even simply allowing it to respect the markdown I've used in the forms would be great.
Major +1
We have custom fields to ensure work appears on the correct board for the intended teams
Without this, they can't create tickets via Slack, because making that field optional will cause absolute chaos given current level of accountability + responsibility—which is why we have processes as safeguards in the first place
The Jira-Slack integration allows teams to streamline their work, but how many businesses use Jira as-is out of the box w/o some form of customization set for business needs?
This is also blocking us with our Metro Retro - Jira integration. So, all integrations
This functionality is the difference between my company remaining on a "free" account or upgrading to a paid subscription. I'm actually surprised this wasn't thought of when initially developing the integration.