Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Project filter not working

Peter Horner July 18, 2019

Hi,

I'm trying to filter results based on a specific project, so have been using:

project = GCB

This was working until this afternoon when two tickets from completely random projects appeared in my filter and I cannot remove them from the results regardless of how I modify the filter.

Is there any method of making the "project" filter impossible to deviate from in a JIRA search?

Thanks.

2 answers

1 accepted

0 votes
Answer accepted
Inactive Stephen
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.
July 19, 2019

Hi @Peter Horner

What are the project keys for the two other tickets? Do they mention GCB anywhere within the ticket?

The other tickets should not appear if you're searching via project key.

Ste

Peter Horner July 19, 2019

Hi @Inactive Stephen 

The other two project keys are WHPAM and WHGI. I've now got a second WHPAM ticket displaying as well, making it three non-GCB project tickets appearing.

None of them mention GCB anywhere in the ticket. The only consistent values with the tickets I want are that they're in the date range I've specified.

The consistencies between the random tickets are that they're all referenced as "Prod_blocker"/"Prod_Blocker" and have either the same ID/label (4...). I tried to filter these out but to no avail.

I've tweaked the way I'd written the date range in a new filter:

project = GCB AND issuetype not in (Epic) AND (duedate = startOfWeek(6d) OR duedate = startOfWeek(7d) OR duedate = startOfWeek(8d)) ORDER BY duedate ASC

This seems to be working for now, but then the last filter was working perfectly until yesterday afternoon, so I assume if it pulled in non-project work before it is possible for it to do so again?

Thanks.

Inactive Stephen
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.
July 19, 2019

Strange - and if you search for "project = WHPAM" do you get any other project tickets in that search?

Was the search just "project = GCB" or did you have any other parts to the query?

Ste

Peter Horner July 23, 2019

The original search was:

project = GCB AND duedate = startOfWeek(8d) OR duedate = startOfWeek(7d) OR duedate = startOfWeek(6d) ORDER BY duedate DESC

That brings in work from other projects.

Tweaking the way I've written the dates seems to have solved it though (for now anyway), so I assume that was the cause.

I still would have thought that searching a specific project would only pull through results from that project though.

Thanks.

Inactive Stephen
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.
July 23, 2019

Hi @Peter Horner

Your original was almost correct - but it's the first OR which is allowing in other projects.

After the first OR you're just looking for any issues with a due date within your search parameters - it's no longer considering the first project search because it's after the OR.

A simple fix would be to put brackets around the due date searches - i.e: 

project = GCB AND (duedate = startOfWeek(8d) OR duedate = startOfWeek(7d) OR duedate = startOfWeek(6d)) ORDER BY duedate DESC

^ Should fix the issue.

Ste

Like # people like this
0 votes
Muhammad Ramzan_Atlassian Certified Master_
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.
July 20, 2019

did you recently changed the project key?

Peter Horner July 23, 2019

Hi @Muhammad Ramzan_Atlassian Certified Master_

None of the project keys had been changed, as far as I'm aware anyway.

Thanks.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events