Search returns wrong project issues

[Del Jensen]

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

[Antoine Berry]

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]

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]

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]

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.