-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.5.4
-
None
-
8.05
-
1
-
Severity 3 - Minor
-
Issue Summary
REST API for Deleting actor users/groups returns success (204) even if the group/user doesn't exist in Jira. In the documentation for [JIRA 8.5.3|https://docs.atlassian.com/software/jira/docs/api/REST/8.5.3/#api/2/project/
{projectIdOrKey}/role-addActorUsers]h3. Steps to Reproduce
Do a DELETE request to the endpoint /rest/api/2/project/{projectIdOrKey}
/role/
{roleId}?group={groupname} sending an invalid use like this groupnameDo a DELETE request to the endpoint /rest/api/2/project/{projectIdOrKey}/role/{roleId}
?user=
{username}sending an invalid use like this username
Expected Results
If the group indicated does not exist, the expectation is that there would be an error 404 as indicated in the documentation: "STATUS 404 Returned if the project or role is not found, the calling user does not have permission to view it or does not have permission to modify the actors in the project role".
Actual Results
A message 204 (success) is returned.
Workaround
Currently there is no known workaround for this behaviour. A workaround will be added here when available
- relates to
-
JRASERVER-70937 REST API for Add actor users returns success (200) even if the user doesn't exist
- Closed