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.
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
did you recently changed the project key?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Muhammad Ramzan_Atlassian Certified Master_
None of the project keys had been changed, as far as I'm aware anyway.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.