Recently, Jira started sending daily emails with a list of overdue issues. As I find those very annoying, I'm looking for a way to keep al my email alerts, except for that one. How do I turn of the Overdue alert emails?
Hello @Marian ,
Good day! This feature can be turned off by the user by going to Jira Personal Settings ( Site -> profile icon -> Personal settings ) , scrolling down to Jira labs and toggling off Overdue Alerts.
Thank you!
Why would such a experimental feature be enabled by default?
This one seems like it should be an "opt in" feature as it is a push-communication that was not requested.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Shalini Pradhan ,
Do you know if admins can turn this off globally? I haven't been able to find anything supporting that they would be able to turn it off.
Any input would be great,
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This setting is not present.
The answer seems not correct to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yup, same for me too. there is no Overdue Alerts option under Jira Labs. Also in my case, the ticket is not really even overdue, so the email is wrong. We send our tickets to Resolution, and give user 5 days to reply before we officially close it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think I have found now the correct place for the setting.
Its not on the main page of the notifications, so no scroll down. Instead select DIGESTS on the left and deactivate the option "Due or overdue work items" there
Digest Notifications - AES PM/TL Management Support Tool
For me it does not make sense to create a separate page for this single option instead of list it together with all the other notifications.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I see that now! In my case, I would love for it to be smarter as in my case its looking at the wrong status so its over reporting what is actually overdue. So now I have to decide do I want to never get any overdue notifications or get a bunch that could be wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
EDIT: Sorry this was meant to be a reply not an answer
Hey @Shalini Pradhan
This doesn't seem to be present under Jira Labs for me;
I would have expected the notification option to be...well...under notification settings, but it doesn't appear to be there either;
Where can we now find where to turn off these notifications?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi everyone!
Apologies for not responding on time. Upon further checking, the location for the toggle has been changed. The new location to toggle this overdue alert is Personal Jira settings > Digests and toggling the Due or Overdue work option.
Bill Sheboy,
To answer your question, experiments are features under development that are exposed to a subset of customers to get an early indication of how users react to the experience before we decide to launch it. Your site might be currently enrolled in an experiment and thats why you see this.
Hope that helps!
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I understand how software experiments work.
To restate my observation, experiments should always include a way for a customer to "opt out", at an individual and site level, as the customer's flow may be disrupted in a way that causes confusion and increases labor costs (e.g., site admins tracking down if there is a defect). Customers opting out would be valuable information for the Atlassian design team to learn and consider if there is flaw in their hypothesis which led to the experiment.
Disabling the "Atlassian labs" feature no longer does this consistently for paid license customers and free license customers rarely have a way to disable such features.
This practice of experiment-without-disable increases support costs for Atlassian when people need to submit a ticket to turn off an experiment, ignores an agile concept of "make it safe to experiment", and seems to ignore several of Atlassian's own values: https://www.atlassian.com/company/values
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.