-
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
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[API-157] Customize the fields in the 'Create Issue' form in Slack
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.
+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
We use a custom field for ticket assignment based on the main software/hardware/area/topic and that field is required so tickets get auto-routed. Without this feature, we can't create tickets from Slack messages using Create Issue. If we make the field optional, MANY tickets won't get routed.
This has been here for FIVE years and has nearly 500 votes. What will it take to move it up the list?
+1. This should also cover -> JRACLOUD-82695 Support Team field when Creating issue in Slack - Create and track feature requests for Atlassian products.
This seems pretty essentials otherwise it is no better than the Atlassian Assist app. We should have the choice of all of the fields being populated etc.
Being able to do this would greatly streamline processes of ours that depend on specific fields.
I would just like to add that when system fields are displayed in the Slack preview card (e.g. Priority) it can actually cause confusion when the preview is for an issue in a project that doesn't even use that field or uses an alternate custom field (e.g. "Urgency Level"). In this scenario an issue with a highly urgent "Urgency Level" may still display as the system default Priority of "Medium" in the preview card in Slack, causing confusion to channel members.
The preview can be turned off with the /jira previews slash command, but then that removes the entire preview card. It would be great if the display card could be customized regarding which fields appear.
+1, this would really help us in auto-triaging tickets filed from different slack channels.
I got tired of waiting for Atlassian to give me a more compact and in-line way to refer to Jira tickets in slack, so I created a bookmarklet. It combines the first 75 chars of the ticket title (removing the {{ – JIRA}} at the end of the title), makes this a clickable link and puts it onto your clipboard so that you can paste it into Slack.
For example, this ticket appears as API-157 Customize the fields from the create issue from Slack to Jira - C….
Source, and escaped js for bookmarklet: https://gist.github.com/truthdoug/d7e6bfc60f333d7800f555e221dc2533
+1
We really should be able to define which fields come up in Slack and in what order.
+1
I only want team members in Slack to create a ticket from a form with fields for Project, Issue Type, Priority, Assignee, Summary, and Description.
Just checking in on this thread and adding my org to the vast numbers of us who would LOVE to be able to set a default project for submissions made by users using Jira /create.
Note how Jira (and Confluence) has a nice compact method of showing ticket summaries inline like this:
KEY-1234 Summary or Title Text IN PROGRESS
That's simple. This is what I want to see in Slack, not the current block that's the equivalent of 5-6 lines of text:
KEY-1234 Summary or Title
Status: In Progress
Type: Task
Assignee: Unassigned
Priority: Medium
[Watch button] [action dropdown]
It breaks up the conversation too much. I don't need actions here. I'll click through to get those.
(It should be obvious, but I'll state here that the emojis I chose are not what I see in JIRA/Slack... they're just placeholders to get the idea across.)
If we can set auto-fill the 'Description' field instead of 'Summary', it would be great.
Please escalate this feature request.
We have 2 required fields that prevent issue transition if empty. This blocks efficiency utilizing slack/jira integration.
Being able to customize the template for issues that are sent to Jira from Slack would be very much appreciated
+1
in the current way only option is to custom built an app, which is hard to maintain and get bandwidth for. this will help easily adopt in many teams for sure.
+1, interested in this capability and also on the issue listed on https://jira.atlassian.com/browse/API-173
it'd be great if we can use the request forms that are associated with the request type. As we heavily rely on slack apps
This is important, please enable this.