-
Type:
Suggestion
-
Resolution: Low Engagement
-
Component/s: Approvals, Forge and Connect
-
1
-
1
Issue Summary
In the JSM portal, customers can see the "waiting for approval" state with "approvals needed" including a number:
When a REST API client attempts to get approvals using `GET /rest/servicedeskapi/request/
{issueIdOrKey}/approval`, the endpoint responds with a paged set of ApprovalDTO}}s. The {{ApprovalDTO does not include the "number of approvals needed" as is show in the portal UI. This prevents customers & developers from recreating the portal UI using the REST API.h3. Steps to Reproduce
# `GET /rest/servicedeskapi/request/{issueIdOrKey}
/approval`
Expected Results
The response ApprovalDTO includes a "number of approvers needed" to proceed to the next workflow status.
Actual Results
The response ApprovalDTO doesn't include the "number of approvers needed".
Workaround
Even if the data were available in the Jira platform API, a portal UI should authenticate as a portal user and may not have Jira platform access. Hence, this data would be needed in the JSM REST API. Currently there is no known workaround for this behavior.
- blocks
-
DEVHELP-6058 Loading...