Details
-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
6.1.7, 6.3.15
-
6.01
-
Description
Summary
According to Creating a Notification Scheme documentation, Issue Moved notification works as follow:
An issue has been moved into or out of this project.
However, Issue Moved notification only received by the receiving (target) end, no notification on the source project
Steps to Reproduce
To fully check whether the Issue Moved notification was sent properly:
- Clear Issue Updated notification
- Clear Issue Assigned notification
- Ensure that User A and User B has Issue Moved notification
- Move issue from Project A to Project B
Expected Results
Both User A and User B receive the notification
- If the functionality works as what it was described in the documentation, then User A will only need to have Notification Scheme added in Project A to get notification for issue moved into or out of the project
- If the notification was set up correctly, User A only need to be in the Issue Moved notification for Project A in order for it to receive notification for moved issue from that project to every other projects, and it doesn't need to be included on other project's notification scheme.
Basically it should work like: "Hi user, issue from Project A has been moved to Project B", "Hi user, issue form Project A has been moved to Project C"
Actual Results
Only the receiving end (User B, Project B) receive the notification.
In the Mail Queue there is only one mail in the queue, which indicates that only one user is receiving the notification
Notes
Creating this bug not Improvement Request, because documentation says that An issue has been moved into or out of this project.
Attachments
Issue Links
- relates to
-
JRASERVER-65083 Doc update for Notification Schemes
- Closed