Hey!

What about Cascading List? It's still not supported, right?

With kind regards
Slava

We have "Security Level" as a required field in Jira, in order to ensure everything remains secure in several of our projects and the Jira Service Management help desk portal we have as well.... I'm unable to create tickets using "Jira Cloud for Slack" aka the Jira Bot, because the Slack ticket creation form is not showing the Security Level field; and therefore, Slack is attempting to create a ticket in Jira without the "Security Level" defined, and the ticket is unable to be created.

This is the error message that I get when I try to create a ticket using the Jira plugin/bot within my Slack:
Jira Cloud for Slack
Could not create the issue due to the following errors:
• security: Security Level is required.
 
Please also note, that my normal Jira/Slack notifications for ticket updates and whatnot come through just fine to my Slack channels that I've configured the Jira Bot with....I just cannot create any new Jira Issues directly from Slack because we require the "Security Level" to be populated within our Jira Project(s).
 
Can anyone please assist?

Yea, I need select list as well 

@dmichelson Custom Fields of type "Select List (cascading)" aren't supported by the Slack App correct? Any plans to support fields of this type?

Hi, 6fbb754d6a60.

The Jira Cloud for Slack app does support custom fields, though not all of them either due to the complexity or restrictions imposed by the Slack API.

If there's a particular field type or use case you have in mind that's not supported today, please consider creating a new Suggestion/Feature Request ticket.

This doesn't appear to support custom fields, would it be possible to add that functionality? 

c3326dffbdf5 due to some restrictions in the Jira API around it handles autocompletion for sprints, options will only show up if you start typing something in the field.

jose.queiros1 we don't have any additional documentation right now. But, you should be able to just use /jira create, select a site, project, and issue type, and then your fields should show up to be filled in!

Is there any documentation or any announcement on this feature? Would like to know how to setup the fields that appear and the ones that don't.

f.lamein1135332074 nope, that sounds like a bug to me. If you could type `/jira feedback` and report this issue, we'll dig into the details and figure out what's wrong. We do intend to support the vast majority of fields in a classic project. Let's get to the bottom of this error. 🤔

it works very well for us, thanks!!

Great news!!!

Thanks guys! You're every incredibles with us.

That's good news, but do I understand correctly this only seems to work for next-gen projects?

When I try to create an issue in a classic project by selecting the project in the dropdown it gives an error:

"Something went wrong! Please try again later"

Great news David! I just tried it out and love it. I did notice the values for sprints weren't pulling in correctly- is that one of the fields that will be coming soon?

Hi everyone! I'm David, a PM on the Slack integrations team.

I'm excited to announce that the Jira + Slack integration now supports creating issues with required fields from Slack! Previously, you could only fill out a Summary + Description for issues, but now the integration can dynamically pull in the fields for a project/issue type, allowing you to fill out those required fields straight from Slack, and more.

Try it out and let us know what you think! Just enter /jira create in any Slack conversation to get started.

Caveat - we have covered most field types with this recent change, but there are still a few that are not supported.

Eager to have that rolled out. The better we integrate jira with slack the better (for my use case scenario at least).

great to hear that & looking forward to the release!

7d09952545e8 I've seen some folks work around this by creating a special "simplified" project for ticket ingestion/triage. 

Nonetheless, I wouldn't recommend doing that at this point. We're very close to having a solution for you. We're currently testing it internally. Expect to see something soon! We'll update this ticket when there's something to try out. 

Seth Gholson
Product Integrations Dev Manager

Is there any workaround or means, other than removing the "required" property on additional fields, and/or manually creating the ticket from the integrated "manual" button in slack?  Jira / slack integration was great until we decided to mark another field as required to support our work flows. 

Would be nice if we have this.

We really need this! We want to optimise our work flow in Slack, but can't create tickets directly because of the mandatory field blocking the creation of the ticket. 

Our teams has started creating the issues through Slack connector and not having the ability to create issue with extended field set (rather than just the basic fields). This feature enables our teams do their work in more efficient way and I will like to see this feature implemented.

The current message actually suggests this is being worked on instead of "gathering Interest".

Jira Cloud(opens in new tab)APP  11:18
 Oh no! It looks like the project you tried to create an issue for has required fields. We’re working on adding functionality to support required fields. In the meantime, please use the Manual button below to manually create your Jira issue.
 

This should be fixed, it's a major drawback in the Jira/Slack integration.

Very much interested in this issue being fixed.

definitely we need this.

Would be great if this could be implemented. Current version of this tool is too rigid and serves only as a very rudimentary tool for issue creation.

This would save so much time if implemented! 

I would like to see this feature implemented.

> Display required fields in the create issue dialog.

It would be nice to be able to create Jira issues without leaving Slack, especially with the official Atlassian integration that is free so we don't have to pay for 3rd party integrations that support this feature.