-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Currently if a user wants to search for an issue by request type; they have to use 'Customer Request Type' JQL field in their search.
Currently; the usage for 'Customer Request Type' is not properly explained and documented.
- Assuming we are searching for issues with IT Help request type; currently; this field only excepts <project key>/it-help as a valid value. The JQL field should not be restricted by project key only and should also accept normal values like IT Help instead of it-help.
- I believe that Service Desk specific JQL fields should be mentioned in the documentation together with the usage instructions/descriptions.
- is related to
-
JSDCLOUD-5084 The workaround suggested when searching for Customer Request Type stopped to work.
-
- Closed
-
-
JSDSERVER-1583 Not able to search filter Customer Request Type
-
- Closed
-
-
JSDSERVER-193 Customer Request Type in Basic Search
- Gathering Interest
-
DESK-4118 Failed to load
-
DESK-4572 Failed to load
-
QUALITY-266 Loading...
- relates to
-
JSDCLOUD-1054 Expanding 'Customer Request Type' JQL field usage and also documenting it
- Closed
- causes
-
SUCCESS-97 Loading...
- mentioned in
-
Page Loading...
Form Name |
---|
[JSDSERVER-1054] Expanding 'Customer Request Type' JQL field usage and also documenting it
Workflow | Original: JAC Suggestion Workflow [ 3011400 ] | New: JAC Suggestion Workflow 3 [ 3648820 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2664215 ] | New: JAC Suggestion Workflow [ 3011400 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2324027 ] | New: Confluence Workflow - Public Facing v4 [ 2664215 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JSD Suggestion Workflow [ 2053263 ] | New: JSD Suggestion Workflow - TEMP [ 2324027 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2048315 ] | New: JSD Suggestion Workflow [ 2053263 ] |
Workflow | Original: JSD Suggestion Workflow [ 1280155 ] | New: JSD Suggestion Workflow - TEMP [ 2048315 ] |
Description |
Original:
Currently if a user wants to search for an issue by request type; they have to use 'Customer Request Type' JQL field in their search.
Currently; the usage for 'Customer Request Type' is not properly explained and documented. # Assuming we are searching for issues with *IT Help* request type; currently; this field only excepts *<project key>/it-help* as a valid value. The JQL field should not be restricted by project key only and should also accept normal values like *IT Help* instead of *it-help*. # I believe that Service Desk specific JQL fields should be mentioned in the documentation together with the usage instructions/descriptions. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-1054]. {panel} Currently if a user wants to search for an issue by request type; they have to use 'Customer Request Type' JQL field in their search. Currently; the usage for 'Customer Request Type' is not properly explained and documented. # Assuming we are searching for issues with *IT Help* request type; currently; this field only excepts *<project key>/it-help* as a valid value. The JQL field should not be restricted by project key only and should also accept normal values like *IT Help* instead of *it-help*. # I believe that Service Desk specific JQL fields should be mentioned in the documentation together with the usage instructions/descriptions. |
Link |
New:
This issue relates to |
Labels | Original: affects-cloud fws ix sdt | New: affects-cloud affects-server fws ix sdt |
Labels | Original: fws ix sdt | New: affects-cloud fws ix sdt |