when searching and jira id in search bar on jira board i am getting 2 results

[Vaibhav Garg]

Hi atlassian my name is vaibhav garg 

and i am using jira board in my company but there is a bug

when i am going to back log and searching for any jira id like 33172 .... 2 searched result are coming as a count but when when i go through that ... on screem there is only 1 searched result ....

when i am clicking up and down keys on both searched results then its taking me to the same jira 

[Sunny Ape]

Hello @Vaibhav Garg 

It's not possible to search for Issues based on their ID via the backlog view, so whatever you are searching on, it's not the ID.

The Issue's ID is an absolutely unique, sequential number that is mostly hidden from view, and it's impossible for two issues to have the same ID.

[Vaibhav Garg]

Hi, but when go to the backlogs ok or reports..or ctrl+f and give the jira id then its showing 2 result

[Sunny Ape]

Sorry, but I don't understand what you are saying. I have no idea how to open the Reports page, then use 'ctrl-f' to search for Issues by ID. The Reports page has no Issue 'search' capability... it just contains a collection of Reports.

You will need to provide a set of screen grabs that show exactly what you are talking about, and provide step-by-step instructions of the sequence to follow to reproduce the problem you are describing.

[pawarsachin84]

Hello @Vaibhav Garg ,

Welcome to Atlassian Community! 😊

Thank you for your question.

1. Clear your browser's cache and cookies. This is the first and easiest step to rule out any caching issues. If the problem persists, try using an Incognito/Private window or a different browser to see if the problem is specific to your browser profile.

2. Are you using Jira Data Center or Jira Cloud? If you are using Jira Data center then your Jira administrator can initiate a full re-index of Jira. This forces the system to rebuild its search index, potentially resolving any corruption or inconsistencies.

3. If you've tried the above steps and the problem persists, it's best to contact Atlassian Support for assistance.