-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 3.2.0-OD-17
-
Component/s: Request Type Configuration
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Problem Description
- If the customer changes the project key (following instructions here: https://confluence.atlassian.com/adminjiracloud/editing-a-project-key-776636293.html) then they cannot edit request groups because the database table references the old project key.
- The request should use the project ID, not the project key.
Diagnostic
Making a request to
https://<instance-url>/rest/servicedesk/1/servicedesk/<project-key>/groups
returns an HTTP Status Code of 400 and the following message:
{"errors":[{"errorMessage":"The Service Desk you are trying to view does not exist."}],"reasonKey":"AnErrorToServiceDeskHttpError..com.atlassian.servicedesk.internal.errors.ServiceDeskError$$anon$1","reasonCode":"400"}
You can confirm the problem by running the following query on the database and comparing the "KEY" value to that in the request above.
Query:
SELECT * FROM "AO_54307E_VIEWPORT";
Steps to reproduce
- Create a service desk project.
- Follow the steps to edit the project key here: https://confluence.atlassian.com/adminjiracloud/editing-a-project-key-776636293.html
- Go to Project Settings > Request Types
- Click "Edit Groups" on any of the Request Types listed.
Workaround
We don't have any workarounds for this bug at the moment
- is duplicated by
-
JSDCLOUD-5109 Unable to Edit groups in Request Type page if a project key has been changed
-
- Closed
-
- relates to
-
JSDCLOUD-3982 Cannot edit request type groups for a project if the key has been changed.
-
- Closed
-
-
SUCCESS-1111 Loading...
- was cloned as
-
DESK-4868 Loading...