-
Bug
-
Resolution: Fixed
-
Low
-
2.5.0
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
User is unable to search Customer Request Type from Issue Search Filters.
When using the basic mode, the Customer Request Type is grayed and un-clickable. Hovering on top on it, shows an error that says :
Customer Request Type is not applicable for the current project and /or issue type.
It also does not work with JQL using the advance search option.
I have verified this with my own machine.
Workaround:
Thanks efridge for the tips!
Customer Request Type values follow the format of "key/lowercased-form-title-hyphenated", so it may be possible to guess.
For example project key of "ITS":
- General Assistance = its/general-assistance
- Infrastructure Support = its/infrastructure-support
- Telecommunications / Telephones = its/telecommunications--telephones (notice the double hyphen on this one)
I've also noticed that this value is determined when the form is FIRST created, and if you change the name of the form, it doesn't change the title. I've also seen some values that look like "req/its-request2" where it apparently added a number on the end to make it unique. I think that happened because I had two identically named forms when I first set up that project.
Maybe that will help you reverse engineer things and get some queries working.
PSQL Query that can be used to identify Customer Request type name formatting:
select distinct stringvalue from customfieldvalue cfv
where cfv.customfield = (select id from customfield where cfname = 'Customer Request Type') ;
- is related to
-
-
- Closed
-
-
DESK-4118 Failed to load
- relates to
-
-
- Closed
-
-
JSDSERVER-1054 Expanding 'Customer Request Type' JQL field usage and also documenting it
- Closed
-
- Closed
-
- Gathering Interest
-
QUALITY-266 Loading...
- mentioned in
-
-
-
-
-
-
[JSDSERVER-1583] Not able to search filter Customer Request Type
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304642 ] | New: JAC Bug Workflow v3 [ 3125747 ] |
| Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
| Labels | Original: #threshold affects-cloud affects-server cst pm | New: #threshold affects-cloud affects-server pm |
| Labels | Original: #threshold affects-cloud affects-server pm | New: #threshold affects-cloud affects-server cst pm |
| Workflow | Original: JSD Bug Workflow v5 [ 2058524 ] | New: JSD Bug Workflow v5 - TEMP [ 2304642 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2055877 ] | New: JSD Bug Workflow v5 [ 2058524 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 1956169 ] | New: JSD Bug Workflow v5 - TEMP [ 2055877 ] |
| Workflow | Original: JSD Bug Workflow v4 [ 1615443 ] | New: JSD Bug Workflow v5 [ 1956169 ] |
| Description |
Original:
User is unable to search *Customer Request Type* from Issue Search Filters.
When using the basic mode, the *Customer Request Type* is grayed and un-clickable. Hovering on top on it, shows an error that says : {quote} Customer Request Type is not applicable for the current project and /or issue type. {quote} It also does not work with JQL using the advance search option. (/) I have verified this with my own machine. h4. Workaround: {quote} {panel:bgColor=#F5F6CE}Thanks [~efridge] for the tips! :){panel} Customer Request Type values follow the format of "key/lowercased-form-title-hyphenated", so it may be possible to guess. For example project key of "ITS": # *General Assistance* = {{its/general-assistance}} # *Infrastructure Support* = {{its/infrastructure-support}} # *Telecommunications / Telephones* = {{its/telecommunications--telephones}} (_notice the double hyphen on this one_) I've also noticed that this value is determined when the form is FIRST created, and if you change the name of the form, it doesn't change the title. I've also seen some values that look like "req/its-request2" where it apparently added a number on the end to make it unique. I think that happened because I had two identically named forms when I first set up that project. Maybe that will help you reverse engineer things and get some queries working. {quote} PSQL Query that can be used to identify Customer Request type name formatting: {code} select distinct stringvalue from customfieldvalue cfv where cfv.customfield = (select id from customfield where cfname = 'Customer Request Type') ; {code} |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1583]. {panel} User is unable to search *Customer Request Type* from Issue Search Filters. When using the basic mode, the *Customer Request Type* is grayed and un-clickable. Hovering on top on it, shows an error that says : {quote} Customer Request Type is not applicable for the current project and /or issue type. {quote} It also does not work with JQL using the advance search option. (/) I have verified this with my own machine. h4. Workaround: {quote} {panel:bgColor=#F5F6CE}Thanks [~efridge] for the tips! :){panel} Customer Request Type values follow the format of "key/lowercased-form-title-hyphenated", so it may be possible to guess. For example project key of "ITS": # *General Assistance* = {{its/general-assistance}} # *Infrastructure Support* = {{its/infrastructure-support}} # *Telecommunications / Telephones* = {{its/telecommunications--telephones}} (_notice the double hyphen on this one_) I've also noticed that this value is determined when the form is FIRST created, and if you change the name of the form, it doesn't change the title. I've also seen some values that look like "req/its-request2" where it apparently added a number on the end to make it unique. I think that happened because I had two identically named forms when I first set up that project. Maybe that will help you reverse engineer things and get some queries working. {quote} PSQL Query that can be used to identify Customer Request type name formatting: {code} select distinct stringvalue from customfieldvalue cfv where cfv.customfield = (select id from customfield where cfname = 'Customer Request Type') ; {code} |
| Link |
New:
This issue relates to |
| Labels | Original: #threshold affects-server pm | New: #threshold affects-cloud affects-server pm |