How to override Android Do Not Disturb for Operations Alerts in Jira Cloud app

Question

I'm using Jira Cloud app v174.1.8 on Android 16.

I'm trying to configure Operations Alerts to override Android's Do Not Disturb.

In Android Settings - Modes - Do Not Disturb, I've added Jira Cloud as an app that can interrupt.

When I select Jira under "Apps that can interrupt", it shows a list "Notifications that can interrupt". There is no entry in this list with the word "alert" in it.

What am I missing?

Marc -Devoteam- · Answer

Hi @michael.benson

But still it seems related to google, as you personal phone uses a profile.

See if Google has a fix for this, and then Atlassian could implement this.

michael.benson · Answer

Thanks, but don't think this is applicable. App is installed on personal phone with no personal/work profile separation.

Marc -Devoteam- · Answer

Hi @michael.benson

I'm not that into the app world on phones.

If its then this can't be overwritten, see the won't fix article from google, https://issuetracker.google.com/issues/77939714?pli=1

From Atlassian:

"We have reproduced this issue and saw that the workaround previously mentioned (installing the app in both the Personal and the Work profile) does not work. This workaround has not been an official fix for this issue.

Google Developer Docs states that: “Managed profiles cannot grant Do Not Disturb access”. In this context, “Managed profiles” refer to the Work profile.
This workaround that has previously worked in Android 12 and below has been patched, and it does not work anymore on Android 13 and above.

Unfortunately, we are unable to provide any further assistance with this issue, as this is a decision made by Google about the usage of the Work profile, and we have no control over how the Work profile works and what permissions it can block out for any of our apps.

There is an issue about this on Google’s IssueTracker, and it can be found here: https://issuetracker.google.com/issues/77939714
If Google chooses to provide a fix for this, we are happy to implement it for all of our users. But, as it stands now, we are unable to assist further with this issue."