NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding bug report.
Summary
The approver doesn't get any other notification than the one to approve the ticket even if they are also set as the request assignee and are watching the request as well.
Also after removing that user as the approver, still no notifications are sent to them.
Environment
Reproduced on JIRA Cloud version: 1000.245.1
Steps to Reproduce
Case 1:
- In JIRA Service Desk create a service request that needs approval (e.g. purchase request)
- Set the same user as approver, assignee and watcher
- Add couple of comments to the request (internal and public)
Case 2:
- In JIRA Service Desk create a service request that needs approval (e.g. purchase request)
- Set the same user as assignee and watcher
- Add couple of comments and see that you get the notifications for those comments
- Add the same user as the approver for the request
Expected Results
In both cases the expected result is that the user get notifications for all the comments and status changes
Actual Results
Case 1:
- The user only receives the notification that the request needs approval
Case 2:
- The user receives the notifications up until step #3. Then, after getting the approval notification they stop getting any other notification
Notes
If you approve the request, then removing the user as the approver does not fix the issue since the user is still set as the one that approved the request.
Workaround
None at the moment.
- is related to
-
JSDSERVER-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
-
- relates to
-
JSDCLOUD-4207 Approvers should not be always treated as customers
- Closed
[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
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2303929 ] | New: JAC Bug Workflow v3 [ 3446045 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 2057895 ] | New: JSD Bug Workflow v5 - TEMP [ 2303929 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2055340 ] | New: JSD Bug Workflow v5 [ 2057895 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 1954913 ] | New: JSD Bug Workflow v5 - TEMP [ 2055340 ] |
| Workflow | Original: JSD Bug Workflow v4 [ 1874142 ] | New: JSD Bug Workflow v5 [ 1954913 ] |
| Description |
Original:
h3. Summary The approver doesn't get any other notification than the one to approve the ticket even if they are also set as the request assignee and are watching the request as well. Also after removing that user as the approver, still no notifications are sent to them. h3. Environment Reproduced on JIRA Cloud version: 1000.245.1 h3. Steps to Reproduce *Case 1:* # In JIRA Service Desk create a service request that needs approval (e.g. purchase request) # Set the same user as approver, assignee and watcher # Add couple of comments to the request (internal and public) *Case 2:* # In JIRA Service Desk create a service request that needs approval (e.g. purchase request) # Set the same user as assignee and watcher # Add couple of comments and see that you get the notifications for those comments # Add the same user as the approver for the request h3. Expected Results In both cases the expected result is that the user get notifications for all the comments and status changes h3. Actual Results *Case 1:* - The user only receives the notification that the request needs approval *Case 2:* - The user receives the notifications up until step #3. Then, after getting the approval notification they stop getting any other notification h3. Notes If you approve the request, then removing the user as the approver does not fix the issue since the user is still set as the one that approved the request. h3. Workaround None at the moment. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Service Desk Cloud*. Using *JIRA Service Desk Server*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDSERVER-4167]. {panel} h3. Summary The approver doesn't get any other notification than the one to approve the ticket even if they are also set as the request assignee and are watching the request as well. Also after removing that user as the approver, still no notifications are sent to them. h3. Environment Reproduced on JIRA Cloud version: 1000.245.1 h3. Steps to Reproduce *Case 1:* # In JIRA Service Desk create a service request that needs approval (e.g. purchase request) # Set the same user as approver, assignee and watcher # Add couple of comments to the request (internal and public) *Case 2:* # In JIRA Service Desk create a service request that needs approval (e.g. purchase request) # Set the same user as assignee and watcher # Add couple of comments and see that you get the notifications for those comments # Add the same user as the approver for the request h3. Expected Results In both cases the expected result is that the user get notifications for all the comments and status changes h3. Actual Results *Case 1:* - The user only receives the notification that the request needs approval *Case 2:* - The user receives the notifications up until step #3. Then, after getting the approval notification they stop getting any other notification h3. Notes If you approve the request, then removing the user as the approver does not fix the issue since the user is still set as the one that approved the request. h3. Workaround None at the moment. |
| Link |
New:
This issue is related to |
| Project Import | New: Sun Apr 02 00:24:18 UTC 2017 [ 1491092658763 ] |
| Workflow | Original: JSD Bug Workflow v2 [ 1602666 ] | New: JSD Bug Workflow v4 [ 1615338 ] |
| Workflow | Original: JSD Bug Workflow [ 1588936 ] | New: JSD Bug Workflow v2 [ 1602666 ] |