We currently do not allow request creation without a request type so this made our Slack Jira Cloud app worthless to us because we can't pass the workflow to create the issues with Jira Cloud and can only use the Assist App which needs special configuration. 

I mean this is a regression from the Halp experience we had. Every little thing that used to work in Halp is now missed here in JSM and we are being asked to submit and vote for feature request. 

This is making less and less sense. You had almost 2-3 years to copy/ integrate the best features of Halp into JSM, if only you had paid enough attention to why even folks were using Halp and stuck around even after you bought this you would have made a informed choice.

I am not debating that every little thing need to be built, we build software too and I understand that you can't cater to everything, but please reflect upon all of these features which were working perfectly fine prior to June 4th and inexplicably a miss in JSM.

This would be incredibly beneficial. We use the Jira cloud app on slack, and it is definitely lacking some functionality. This feature being added would be incredibly helpful to help our support engineers and users further categorize their requests. 

+1 This seems like a miss to be honest, not something we would send as a feature request.

+1 for this feature, would be amazing to have the ability to create issues from Slack and use request types as the parameters

Please can someone look into fixing this issue. I understand service projects have the benefit of the customer portal to raise things but having the slack integration working would enable better engagement with my colleagues