-
Bug
-
Resolution: Fixed
-
Low
-
5.9.0, 5.12.0, 5.14.0, 5.12.4
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
Jira Service Management 5.9 introduced the ability to share requests with groups. This feature introduces the "Groups" (com.atlassian.servicedesk:sd-request-groups) custom field to store this data.
The "Get request type fields" endpoint provides the fields listed on a request type. Most REST API consumers expect this technical/locked custom field to be excluded from the result.
Steps to Reproduce
- Install JSM DC 5.9.0+.
- Create a new service desk project.
- Send an authenticated HTTP GET request to <jira-base-url>/rest/servicedeskapi/servicedesk/1/requesttype/1/field.
Expected Results
Only the request type fields are provided in the response. For example:
{
"requestTypeFields": [
{
"fieldId": "summary",
"name": "What do you need?",
"description": "Tell us what you're looking for. For example, 'put me on the mailing list'.",
"required": true,
"validValues": [],
"jiraSchema": {
"type": "string",
"system": "summary"
}
},
{
"fieldId": "description",
"name": "Why do you need this?",
"description": "",
"required": true,
"validValues": [],
"jiraSchema": {
"type": "string",
"system": "description"
}
}
],
"canRaiseOnBehalfOf": true,
"canAddRequestParticipants": true
}
Actual Results
The "Groups" (com.atlassian.servicedesk:sd-request-groups) custom field is included in the response.
{
"requestTypeFields": [
{
"fieldId": "summary",
"name": "What do you need?",
"description": "Tell us what you're looking for. For example, 'put me on the mailing list'.",
"required": true,
"validValues": [],
"jiraSchema": {
"type": "string",
"system": "summary"
}
},
{
"fieldId": "description",
"name": "Why do you need this?",
"description": "",
"required": true,
"validValues": [],
"jiraSchema": {
"type": "string",
"system": "description"
}
},
{
"fieldId": "customfield_10113",
"name": "",
"description": "",
"required": false,
"validValues": [],
"jiraSchema": {
"type": "array",
"items": "group",
"custom": "com.atlassian.servicedesk:sd-request-groups",
"customId": 10113
}
}
],
"canRaiseOnBehalfOf": true,
"canAddRequestParticipants": true
}
Workaround
Sharing service requests with groups can be disabled by setting the following site-wide feature flag (How to manage dark features in Jira):
sd.share.request.with.group.disabled
The change will take immediate effect. Existing group request shares will be revoked but can be restored by removing the feature flag.
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-15147] Remove JSM "Groups" custom field from REST API endpoint
| Labels | Original: ltsr |
| Labels | New: ltsr |
| Fix Version/s | Original: 5.15.0 [ 107090 ] | |
| Fix Version/s | New: 5.15.2 [ 108100 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 878182 ] |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Fix Version/s | New: 5.15.0 [ 107090 ] |
| Assignee | New: Benjamin Suess [ c8bcca445054 ] |
| Status | Original: Short Term Backlog [ 12074 ] | New: In Progress [ 3 ] |
Your workaround is a life saver. I've been so confused about this for months now, why this f*cking field keeps popping back in on screens. Now our customer started to flag about safety 'cus they cant accidentally share issues to a whole group. Its such a stupid feature to have implemented for everyone. Really happy for this ticket, did not know about dark features. Thank you!