-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
None
-
1
-
Severity 3 - Minor
-
0
-
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Summary
Currently, Reporter doesn't receive notification for Issue Moved event. This is expected as per:
However, Notification Helper says that Reporter receives notification. Though this is also expected according to JIRA's Default Notification Scheme, it's confusing.
Steps to reproduce
- Create 2 SD projects A and B
- Create a customer C and ensure C has access to both A and B
- As customer C, create a request in A
- As an agent, move the request to B
Expected behavior
C doesn't receive notification and Notification Helper should explain why.
Actual behavior
C doesn't receive notification but Notification Helper says it should.
Note
It has been suggested that customers receive notification for Issue Moved event. This is currently being tracked in JSD-3417.
- is incorporated by
-
JSDSERVER-3417 Issue Moved notification
- Closed
- relates to
-
JSDCLOUD-4373 Incorrect Notification Helper for Issue Moved
-
- Closed
-
- links to
[JSDSERVER-4373] Incorrect Notification Helper for Issue Moved
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Labels | Original: pm ril | New: cleanup-seos-fy25 pm ril |
Labels | Original: pm | New: pm ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 954963 ] |
UIS | Original: 5 | New: 0 |
UIS | New: 5 |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304536 ] | New: JAC Bug Workflow v3 [ 3126339 ] |
Status | Original: To Do [ 10071 ] | New: Gathering Impact [ 12072 ] |
Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Support reference count | New: 1 |
Labels | New: pm |