This is important, please enable this.

+1

+1

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

+1

+ 1

+1

+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. 

+1

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

+1

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.

+1

+1

+1

+1 yes - please support this feature!

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.

+1

+1

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.

please support this

+1

+1

+1

+1 absolutely needed

+1

At the very least being able to add a default parent, thanks

+1

+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

+1

+1

We really should be able to define which fields come up in Slack and in what order.

Yes please, per project-based fields.

Would be fantastic

+1

+1 Whould be great

+1

+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.)

Upvoting for this!  

If we can set auto-fill the 'Description' field instead of 'Summary', it would be great.

+1

That would be great!

+1

Please make this possible

We need this feature . This would be helpful. 

Please make this possible.

+1

+1

+1

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 Awaiting this awesome implementation.

+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

+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

Need this functionality to make issues logging easier.

Is there a way to set a default project selection? As in, when someone types "/Jira create" in a certain slack channel, the "Project" field will have a specific project pre-selected?

I'm seeing mixed results with my testing. In a private channel I made, it auto-selects the project I am interested in. I believe it's because it is considered a "recent project". But in another channel, it auto-selects a different project. How do I clear or reset the "recent project" list & selection?

Any help would be appreciated thanks all!

It would be great if admins can edit this by themselves, depending on the form they have in Jira. Please work on this!

We have a mandatory custom "Select List (cascading)" field .. without this feature we can't use the Slack integration at all 

Without this function or the ability to specify the field in the /Jira call it's not usable.

Need it also, else not really useful to integrate Jira

It will be amazing to have this feature in place!! Are there any plans on adding into the roadmap? 
Thanks. 

We need this feature 

Hey cb677b17f330, 18d497f99515 & fe116b29fba7!

Please be sure to use the voting feature on this request so that it will increase the change of consideration on the roadmap!

Please make it happen! It is so needed to streamline workflows. Ideally we have both default value customization and ability to provide certain values at the `/create` command line prompt. Ideally, we have the default board settings assigned per user and per Slack channel and ability to choose epics, assignees and priority from the prompt itself (e.g. mentioning someone would make them the task owner, etc.)

This is definitely something that we need. ASAP if possible. 

We need that 

We would like to be able to add a custom field when creating an issue from Slack. We would like to add a custom field called "Request Type". Is this possible?

We cannot use this function (and would love to) because it is pulling random fields from our project. Would love to see this get fixed soon.

Specifically interested in being able to set "Epic" from slack, but other fields useful too.

Current cannot use the Create Issue feature because one of our required fields for issues in Jira does not appear on the Slack form

Adding Organization feature would greatly streamline our process when creating issues in Slack. Please add this to the integration! 

I need to be able to use a Screen definition to control this. 

I created some custom fields in my Jira project 1 out of 4 created reflected in the Jira create form, where can i manage to Add or Remove them ?

Hi, would be possible to set a value from "Component" field from slack ? It would be great in order to categorize support tickets then.

Thanks

Our team would greatly benefit from customization in our Jira slack form integration at a per channel level.

• the ability to pre-populate select field values for all submissions for a specific slack channel integration
  • e.g. Summary: DGC New data request
  • e.g. Description: pre-crafted template of inputs we require - event, description, properties, sample values, etc. 
• the ability to remove select fields for all submissions for a specific slack channel integration
  • e.g. remove components
  • e.g. remove epic link
  • e.g. labels

+1!!!

Seems like this should be a simple screen - you need to be using a screen to have this current functionality work - why not let that screen be assigned by us in Jira settings? that'd be super helpful - for us like others i know slack is the main creation point for issues

I would love to see defaults configurable for /Jira create, so that when users make tickets they automatically go to the correct project.
For example, If I could set issue type, assignee and priority to always be the same, this would hugely improve the efficiency of ticket creation (since most of my team is always on Slack) and keep my ticketing queue organized at the same time.

3 years old, second my upvoted topic. hmmmmm

+1

Hi will.sargent1,

The summary should be shown if properly configured in Jira Cloud. The field set is retrieved according to the configuration for the issue type and project. 

It may be the case there's a special configuration for your issue type and project that is inhibiting the summary field from being listed as part of the Issue Create Metadata.