The Unassigned section is showing 1, however, it should be zero:
Unassigned
1
Check out this post: https://community.atlassian.com/forums/discussion/3317282/bug-report-unassigned-items-showing-wrong-value?utm_source=community-share
Hi Shivam,
I'd start by checking what the Unassigned queue lists when you open it, because the number in the sidebar can differ from the list behind it, and Atlassian documents that case.
If the queue opens empty, it's the count that's off, and Atlassian has a KB for this exact case, Resolving Discrepancies in JSM Queue Ticket Counts (https://support.atlassian.com/jira/kb/resolving-discrepancies-in-jsm-queue-ticket-counts/), which says it's often related to the browser cache. Their steps are to clear the cache and cookies, or to try an incognito window or another browser. The page on priority groups (https://support.atlassian.com/jira-service-management-cloud/docs/prioritize-your-queues-by-using-groups/) also says that Starred queues refresh their count on a regular sync, so the number can lag a little behind a change you've made.
If the queue does show one item, open it and check its status and Resolution. Unassigned queues normally filter on Resolution = Unresolved, which only means the Resolution field is empty, so a request that was moved to a done status without a resolution being set still counts as open (the KB on queue resolution behaviour covers this: https://support.atlassian.com/jira/kb/project-queues-in-jira-service-management-are-empty-and-not-showing-any-open-tickets/). Setting a resolution on that item clears it from the count, and if it keeps happening, check that your done transition sets one.
Does the queue list anything when you open it?
That’s the queue counter in Jira Service Management, and Atlassian has a KB article for exactly this difference between the number in the sidebar and the list. According to it, the cause is usually the browser cache.
So first try the quick things: open the same queue in an incognito window, or in another browser. If the count is correct there, clear the cache and cookies in your normal browser.
If the 1 is still there in incognito, I would check if there is a work item you can’t see. Ask a Jira admin to run the JQL of that queue in the work item search. If the admin gets one result and you get none, the work item exists but is hidden from you, for example by a security level. Then the number is right and it’s a permissions question, not a bug.
If the admin also gets zero results, it’s worth reporting to Atlassian support with both screenshots.
Hi Shivam - Welcome to the Atlassian Community!
It's almost certainly a browser issue. Clear cache or open an incognito/private window and see if they match up.
Didn't work in incognito window either :(
Hi @Shivam Gupta, incognito failing too rules out the browser cache, so the next step is to find out whether a request really matches that queue. First, when you open the Unassigned queue itself, does it list a request or is it empty?
Then Pavel's check is the right one, comparing what an admin sees with what you see. A project admin can open Queue settings from the More actions menu next to Queues, select the Unassigned queue, then choose More actions and Edit queue. The Work items to show field holds the queue's JQL, and Atlassian's Edit queues page ( https://support.atlassian.com/jira-service-management-cloud/docs/edit-queues/ ) says it shows a live preview of the matching work items as you edit. Nothing needs saving.
If the preview shows a request and you can see it in your queue too, open it and check its status and Resolution, as in my first reply. If the admin sees a request that you can't, it's hidden from you, which is Pavel's security level case. Atlassian fixed a bug back in 2020 where the sidebar counted requests the agent couldn't see ( https://jira.atlassian.com/browse/JSDCLOUD-9529 ), so a count that includes a hidden request is something to report. If the preview is empty for the admin as well, the count itself is wrong. I looked through Atlassian's public bug tracker and couldn't find an open bug for this symptom, so whether the count includes a hidden request or the preview is empty, support is the route, with screenshots of the count and the empty queue, as Pavel said.
Since incognito didn’t help, it’s probably not the browser. One question: do you use security levels on your work items in that space? It look like a red lock on the right corner of your ticket.
I’m asking because a work item with a security level that you are not part of would match the queue, but you would not see it in the list. I haven’t seen the counter go wrong like this before, so I can’t say for sure that this is the reason, but it is quick to check. Ask a Jira admin or a colleague with more access to open the same Unassigned queue. If they see one work item there, that’s your answer.
If they also see an empty list with the number 1, I would report it to Atlassian support with your two screenshots.
When an Unassigned count is one higher than what you can see, there is usually one work item that is counted but hidden in that view. To find it:
If the search returns nothing and the count still shows 1 after a hard refresh, it's a display bug: raise it with Atlassian Support with a screenshot, the page URL and your JQL. If you can say which screen this is (board, backlog or Summary page), we can be more specific.
It looks like you're new here. Sign in or register to get started.