Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-91990

Allow Admins to disable "Due Date/Overdue Alerts" Notifications for Jira site

XMLWordPrintable

    • 462
    • 8

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Users will receive daily notifications at around 8-9am local time through email and the in-app drawer if overdue/due today issues are assigned to them.

      Current Options

      1. This feature can be turned off by each individual user by going to Jira Personal Settings(jira/settings/personal/general), scrolling down to Jira labs and toggling off Overdue Alerts.
      2. Alternatively, Jira Admins may disable all notifications of the site following Settings > System > Outgoing Mail (https://<SITE>.atlassian.net/secure/admin/OutgoingMailServers.jspa), this is mostly useful for sandbox instances only.

      Suggestion

      It would be better to have the option to disable ONLY the overdue alert notifications for the entire site. 

            [JRACLOUD-91990] Allow Admins to disable "Due Date/Overdue Alerts" Notifications for Jira site

            Marcus added a comment - - edited

            We are already using Jira automation to inform users about overdue issues. The notification E-Mail contains a list of relevant issues with name, URL and due date.

            So we would like to opt out from the currently inferior "out of the box" notification. Its confusing for our users why they suddenly get this.

            Marcus added a comment - - edited We are already using Jira automation to inform users about overdue issues. The notification E-Mail contains a list of relevant issues with name, URL and due date. So we would like to opt out from the currently inferior "out of the box" notification. Its confusing for our users why they suddenly get this.

            Tom added a comment -

            Most of my team have asked if these notifications are genuine, as they look like phishing emails!

            I aim to stop unnecessary email noise and chatter not propagate it.

            This is the same as when default emoji-based comment prompts were added.  I'm sure most don't want it so leave the few that do to activate it themselves.

            Tom added a comment - Most of my team have asked if these notifications are genuine, as they look like phishing emails! I aim to stop unnecessary email noise and chatter not propagate it. This is the same as when default emoji-based comment prompts were added.  I'm sure most don't want it so leave the few that do to activate it themselves.

            Josh added a comment - - edited

            This feature launch had some issues that I hope Atlassian can learn from to improve future releases

            1. Experimental features should not be opt-in, particularly for Premium / Enterprise users
            2. The initial recommended workaround was to instruct all users to individually turn off this feature (not acceptable in an enterprise environment)
            3. More communication should be provided before sending a new type of notification to users, especially when:
              1. The sender is different ( jira@po.atlassian.net )
              2. The description is very generic (it looked like a phishing message to our team)
              3. The included link is unusual ( *https://atlas-trk.prd.msg.ss-inf.net* )

            Josh added a comment - - edited This feature launch had some issues that I hope Atlassian can learn from to improve future releases Experimental features should not be opt-in , particularly for Premium / Enterprise users The initial recommended workaround was to instruct all users to individually turn off this feature (not acceptable in an enterprise environment) More communication should be provided before sending a new type of notification to users, especially when: The sender is different ( jira@po.atlassian.net ) The description is very generic (it looked like a phishing message to our team) The included link is unusual ( * https://atlas-trk.prd.msg.ss-inf.net* )

            Josh added a comment -

            Customer-Recommended Workaround

            • Contact Atlassian Support and ask that they disable this feature at the site level on your behalf.

            Josh added a comment - Customer-Recommended Workaround Contact Atlassian Support and ask that they disable this feature at the site level on your behalf.

              Unassigned Unassigned
              543d2e85f0a8 Joao Vasconcelos
              Votes:
              20 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated: