Search for key doesn't show issue in list, but pressing Enter opens it

[Karl Friberg]

Our users want to use the search to find issues by number (key), e.g. entering 1234 instead of PREFIX-1234.

Using the search top left, the resulting list shows issues with Summary and Description(?) containing "1234". Not the issue "PREFIX-1234", as they want.

But when hitting Enter, issue PREFIX-1234 is opened, which in itself is good, but is a problem since we have aorund 20 different projects on the site.

My question is; How can the users find PREFIX-1234 without the prefix in the most easy way?

[Jamil Rahimov · Accepted solution]

You can add issue key(without prefix) to summary with  script.
After that you can search issue using jql for summary.
You can see in the image:

[Karl Friberg]

Thanks :-) we will think about using this.

[Jamil Rahimov]

Not at all :)

[Troy Anderson]

@Karl Friberg

@Jamil Rahimov 

Is this still the only solution to allow consistent searching by the numeric portion of the issue key at all search interfaces?

[Tarun Sapra · Accepted solution]

Hello @Karl Friberg

When you search, then that search is Jira wide thus just searching for "1234" will give you issues with summary having 1234 in their text so this is expected behavior.

But when you hit enter then you go to project which is last viewed by the user, so if the project is PREFIX then PREFIX-1234 is searched.

Suppose you are working on the project XYZ and you when 1234, then Jira will try to open issue XYZ-1234 and if it doesn't exist you see the error on the screen "You can't view the issue" because it doesn't exist. 

[Karl Friberg]

True, thanks! My wish was perhaps - since you are logged in - that the search is limited to projects you have access to.

[Jamil Rahimov]

@Tarun Sapra 
Sir can you look at my question?
https://community.atlassian.com/t5/Jira-questions/Share-button/qaq-p/962499

[Tarun Sapra]

Hello @Karl Friberg

The search is always limited to the projects which the users have "Browse permissions"  but Jira wide based on user activity i.e. users will never see a projects in the search auto-results which they dont' have access to ( don't have browse project permission).