Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Search returns wrong project issues

Del Jensen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 4, 2019
We have several projects setup. Two of those projects have project keys of ENGHARBOR (Harbor) and CPOINT (Centerpoint). When I enter a simple search for:

project = ENGHARBOR AND resolution = Unresolved ORDER BY priority DESC, updated DESC
This will return issues in the ENGHARBOR project.

If I let Jira change the ENGHARBOR to Harbor, it will return issues in the CPOINT project.
project = Harbor AND resolution = Unresolved ORDER BY priority DESC, updated DESC

Affects Version/s
7.13.0

1 answer

0 votes
Antoine Berry
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 4, 2019

Hi, 

I would suggest either using the key without quotes, or the name of project with quotes, i.e. : 

project = ENGHARBOR 
project = "Harbor"

Antoine

Del Jensen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 4, 2019 edited

Thank you.

When I do this and press the search button

project = ENGHARBOR

It returns the expected results.

If I type and let Jira auto-change to Harbor (that's the project Name) it returns the CPOINT project issues.

project = Harbor 

When I use this, it returns the CPOINT project issues.

project = "Harbor"

 

Other projects return correctly, at least the ones I've tried.

Antoine Berry
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 5, 2019

Well this is beyond my knowledge then. :)

Looks like a bug. I usually use the key of the project anyway because I am sure this is unique and it is shorter. I guess this is a problem for users in your case that use the name of the project instead ?

Del Jensen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 5, 2019

Thank you for your help!  Greatly appreciated!

I prefer using the key of the project also.  Jira, when creating the search string, will auto-fill to the name even if enter the key, at least in our instance it does.  I submitted the issue to Atlassian, if I hear anything, I'll post it here.

Like • Antoine Berry likes this

Suggest an answer

Log in or Sign up to answer