-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
Component/s: Assets - AQL
-
None
-
2
-
Minor
-
6
Issue Summary
We have identified a bug affecting Jira Service Management Cloud when creating customer requests via the REST API, specifically when using an Asset custom field configured with the AQL filter groups having user("currentReporter()"). The issue occurs only for customer users (portal users) and not for regular Jira users.
Steps to Reproduce
- Create a customer user and assign them to a group.
- Configure an Asset custom field with the AQL filter: groups having user("currentReporter()").
- Create an Asset object with a “groups” attribute that includes the group the customer user belongs to.
- Set up a JSM project and request type using the configured Asset custom field.
- Attempt to create a request as the customer user via the API (/rest/servicedeskapi/request).
Expected Results
The request should be created successfully, and the Asset custom field should resolve the correct object based on the customer user’s group membership.
Actual Results
The API returns a 400 error with the following response:
{
statusCode: 400,
body: '{"errorMessage":"Your request could not be created. Please check the fields have been correctly filled in. Validation failed for Insight object","i18nErrorMessage":{"i18nKey":"sd.validation.request.creation.failure.required.field","parameters":["Validation failed for Insight object"]}}'
}
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Loading...