You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi, @Clare Lawson. You will find an answer to your question here: Improving the Create Issue Experience in Jira Service Management Cloud. It was released in early July 2022 and then retracted and then relaunched a few days ago.
You may follow this feature request [JSDCLOUD-1211] Customer Request Type not visible on edit and create screen - Create and track feature requests for Atlassian products.
Hi @Clare Lawson ,
Thanks for raising this and sorry for the confusion. I'm the product manager that pushed these changes out. We're aware that we've created some end user frustration here and do apologise for that. Subsequent releases will involve more clear communication.
The new request type field is intended to encourage people to select a request type. The reason for this is that, at least from what we've seen, the vast majority of issues should have a request type mapped to ensure that the issue behaves as expected. Common problems of issues that don't have request types are:
Some issues in JSM, like "Task" and "Subtask", don't come with request types in our templates (subtasks can't be mapped to request types) and we are looking to introduce issue layouts for these issue types in the future so there is some project level configuration to surface.
In the meantime, the idea is to encourage request type usage unless you are sure you don't want to use them.
I hope this gives you a sense of what we are intending to do here. I'd love to get your thoughts. What do you think about these changes? And does our approach make sense to you?
Product Manager, Jira Service Management
P.S. Thanks @Kalin U for tagging me in this post.
request types exist in Jira Service Management projects and represent different types of requests your customer can create. These customer request types can in the end all still result in the same issue type (if desired).
If you don't set a request type on an issue, you can't share the request with a customer since Jira doesn't recognize it as a proper JSM issue.
There's also more background in the documentation here.
Here are some questions to better understand your problem:
I can't see that there is a field on a screen for request type. On our service desk we have a few issue types hidden from the portal - which therefore don't have associated request types. It appears that when creating one of these the request type is just switched to a default copy of the issue type.
Less that ideal but I guess if you create an Request type for one of your issue types it will remove the unsightly error on the creation screen. If you aren't using and therefore distributing the portal link it shouldn't have any adverse affects.
I guess there is a question of what functionality you are gaining from using a service desk project if you aren't using the portal. Perhaps you should use one of the other project types?
Recommended Learning For You
Level up your skills with Atlassian learning
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Managing Permissions in Jira Cloud
Sharpen your skills at configuring and troubleshooting permissions in Jira Cloud with this free course.