-
Suggestion
-
Resolution: Fixed
-
0
-
23
-
NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.
Summary
As soon as a user is added to an issue as an approver, that user is treated as a customer for the purposes of notifications, even if they're an agent. Unless they then remove themselves after approving a given issue, they'll miss out on receiving any subsequent internal notifications.
Suggestion
If a user is added as an approver to an issue, if they're an agent, keep treating them as an agent for the purposes of notifications.
The use case here is when a customer is set as an approver and merely replies via email saying "This is approved" but doesn't visit the portal to actually click the Approve button. The agent can add herself to the Approvers field and manually approve it to transition the issue through the workflow.
- is related to
-
JSDCLOUD-4167 Issue approver doesn't get any other notification than the one to approve the request, even if they are also Watcher and/or Assignee in JIRA Service Desk Cloud
- Closed
-
JSDSERVER-4207 Approvers should not be always treated as customers
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...