-
Bug
-
Resolution: Fixed
-
High
-
15
-
Severity 3 - Minor
-
15
Issue Summary
With this new Jira experiment for Overdue Alerts, if the customer decides to enable it for their sandbox instance, which has the data copy from the Prod instance up to date, the sandbox items that are close to the due date or are overdue will still notify those users even if they don't have access to the Sandbox site.
If they click on it, they will be redirected to the Sandbox site to request access.
IMPORTANT: For the users to disable that, as the option is inside the site's personal settings, they need to access their personal settings inside the site. This means the Jira admins necessarily need to give the users access to the Sandbox so they can disable that option and then revoke the access again.
Steps to Reproduce
- The sandbox needs to have the Overdue Alerts feature in place
- Then add items that will be close to the due date or overdue
- The assignee can't have access to the Sandbox
- That item will notify the user even if they are not part of the
Expected Results
The users that don't have access to the Sandbox shouldn't receive those alerts from Sandbox.
Actual Results
Users are receiving the notifications from the Sandbox, redirecting them to request access to Sandbox.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
[JWMCLOUD-857] Enabling the overdue alerts on Sandbox will notify users even if they don't have access to Sandbox
The fix has been implemented and we've disabled the feature for all sandbox instances. Thank you for your patience.
All comments
I see this request was closed 16 minutes ago. What does that mean. Is the fix implemented, moved to a different request? What does that mean now for folks that were seeing this appear and had Atlassian turn it off on our sandbox instance(s).
Another item we encountered is if a project is archived, you will not get the results even though the email says you have xx items overdue. We also had adjusted permission on one of sandboxes so even though the email came from that sandbox, the users were not enabled to actually access the instance.
(This bug appeared in our instance.)
Also, please notice, that emails have been sent, although when clicking on the link to display the overdue issues, no issues have been shown. The filter result was empty. So, there is also a bug in the email generation as well.
It is very hard for us admins, if such a feature is released, and we are not able to disable it centrally. You can imagine that we receive a lot of comments on that traffic.
Excited for this new feature, as well however we also do not want to notify all our users that do not have access to the sandbox. I asked to have it turned off until this issue is resolved.
This is very critical for sandbox environments with high user counts. we cannot test new feature if they are going to affect users outside of the sandbox...
Pinned by
Raghav Sriram
The fix has been implemented and we've disabled the feature for all sandbox instances. Thank you for your patience.