nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cannot mark notifications as read

Rob Mason_myzu9l

I cannot mark notifications as read. Every time I click on the bell it is showing thousands of unread notifications (with "Only show unread" ticked).

Clicking "Mark all as read" (which has behind 3 dots menu, used to just be a link) makes the notifications disappear, but clicking the bell shows they're all there again, still unread.

Individually clicking mark as read on each notification makes them disappear, but then if I click the bell, they're all there again, showing as unread.

This is happening in every browser, even after logging out and logging in, clearing all caches, cookies, session and local storage.

Accepted answers

All comments

Marc -Devoteam-

Hi @Rob Mason

I can't replicate you behaviour.

It might be an instance issue, please raise an issue at Atlassian Support

Bibek_ikuTeam_

Rob Mason_myzu9l

OK thanks.

Edit: hmm that link says an admin has to file a request on my behalf, or get help from the Atlassian Community.

Marc -Devoteam-

Hi @Rob Mason

Yes only an admin in your instance can raise a request.

The community option is always given, this to not have every users the option to raise issues at Atlassian support or issues that have been functional and already resolved by community members

But on issues like this, its most likely an instance issue and community member are not in your instance and even if they where, only Atlassian Employees have access to the backend on an instance

Hung Tran Manh

I also have the same issue

Howard, Marion

Hello, this is also happening to me for the last week, and is so inconvenient. Is there a larger bug open?

Rob Mason_myzu9l

I found that if you keep you clicking the bell and choosing "Mark all as unread" repeatedly it will eventually start showing different unread issues and then finally clear them.

The first time I did that I had to do it about 40 times. It's definitely broken.

Karolina Łaciak

Me too!

Dale G_

I am also experiencing this issue. Using `Mark all as read` functionality under Notifications initially marks all Notifications as Read, but if I reload the page or change from Direct -> Watching and back, none of the Notifications stay marked as Read.

Howard, Marion

Omg, I did that and it worked. It creates a new notification for each comment on a ticket. I hope they fix that because it's definitely inconvenient.

Joseph Skupniewicz

I was just about to report this as well!

The "Mark all as read" button and "Only show unread" setting no longer function as they used to.

To reproduce:

Jira > Notifications > Direct > "Only show unread" enabled
Click dropdown menu > "Mark all as read".
Confirm no notifications shown as expected
Refresh
All notifications are present again, despite "Only show unread" being enabled

Joseph Skupniewicz

Exactly the same thing over here

Joseph Skupniewicz

Possible also being reported on https://community.atlassian.com/t5/Jira-questions/Can-the-notification-bell-count-notifications-not-marked-as-read/qaq-p/2801051

Joseph Skupniewicz

OK- I figured out something-

Similar to what a few other people commented, it seems that if you "Mark as read" enough it seems to eventually clear out all the notifications. I verified that this is true.

So, it is not an issue of notifications not being marked as read- per se- but rather something happened on the Jira server (maybe a bulk update?) that caused 100's of tickets to get updated which generated notifications, and you need to continue refreshing and clicking "Mark as read" repeatedly until you work through the backlog.

To save time, I came up with an automated approach to "Mark as read" on a loop which I will post below.

Joseph Skupniewicz

What I did instead of clicking and refreshing manually is I used my browser's Developer Tools on my browser while clicking Notifications Dropdown > "Mark as read" and I analyzed the POST call that gets made to Jira, something like this:

POST: https://<org>.atlassian.net/gateway/api/notification-log/api/3/notifications/mark?direct=true

Payload (Raw): {"toState":"READ"}

Then I used Postman to replicate this call and confirmed that it was successful (you also need to copy a valid cookie from Developer Tools and add supply this as a Header), exported the collection as a JSON, and then I used Newman to perform this call from the command line on a 10-second loop for about 30 minutes until this cleared out all of my backlog of notifications.

brew install newman

while true; do newman run jira-mark-notifications-read.json; sleep 10; done

There are probably other ways to simulate this call, but it was the fastest way I could think of. Hope this helps!

Joseph Skupniewicz

To Jira Developers:

Please consider supporting a "Mark notifications read" with "All" checkbox to force _all_ to make all pages of notifications to be marked as read.

Rob Mason_myzu9l

It's an ongoing bug with Jira. It happens to me every day, whenever there are lots of updates to tickets (real updates from people). I have to open the bell and do "mark all as read" multiple times in order to clear them.

There was an update to Jira which moved "mark all as read" behind three dots, and at the same time they broke the functionality so it doesn't actually mark all of them as read.

Rob Mason_myzu9l

This has started happening for me again. I have to repeatedly mark them as read to get rid of them.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud