Details
-
Suggestion
-
Resolution: Unresolved
-
79
-
26
-
Description
NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.
Auto set the Customer Request Type when there is only one associated with the Issue Type.
or
Auto set the Issue Type when choosing the Request type
Steps to reproduce:
Make sure you have at lest two Request Types, each one related to a different Issue Type.
- Create a Issue
- Change the Issue Type
The Request Type field will show "No Matches", even when there is only one Request Type available for the Issue Type.
Hi all,
We have recently launched a new feature "Default request types" that should solve this problem.
To access this feature, simply click on "Project Settings" > "Features" and scroll to the bottom.
If you turn on this feature, whenever an issue is moved or any other action is taken that causes the request type to be lost, the request type field is updated so that it is not null.
By default, it will select the first request type alphabetically. But you can override the default by setting the request type yourself.
This is a "Feature Lab" feature which means that it is an early solution that will be refined later on. This feature does work as expected and will be fully supported.
So, what will change?
- We are looking to have the default request type selection be respected in the issue create experience within Jira. This is not available now but will be available later.
- We will eventually move this out of the Feature Lab and provide a better UX but this will provide an immediate solution to those that need this.
I'd love to know whether this feature meets your expectations, looking forward to hearing from you all!
Kind regards,
Jehan Gonsalkorale
Product Manager, Jira Service Management
Attachments
Issue Links
- duplicates
-
JSDCLOUD-4176 As a user, for service desk tickets, I want JIRA to prompt users to set request type when performing a move operation to change Issue Type
- Closed
- is duplicated by
-
JSDCLOUD-6339 Update Request Type automatically when issue type is moved
- Closed
-
JSDCLOUD-8405 Update Request Type automatically when issue is moved to different project or different workflow
- Closed
- is related to
-
JSDCLOUD-5901 Request type field shows previous request type value in issue navigator list view
- Closed
-
JSDCLOUD-5807 Inconsistent database value for Request Type prevents "moving" issues to a different type and "editing"
- Closed
-
JSDCLOUD-9181 Wrong request type in the queue and filter view after changing the issue type
- Long Term Backlog
-
JSDSERVER-1835 Update request type upon issue type change.
- Gathering Interest
-
ENT-1559 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...