It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
The issue in question let's call ISSUE-1.
assignee: [me] (I am the admin/account holder)
reporter: [me]
status: "In Progress"
statusCagegory: "In Progress"
workflow: [same as all other projects]
Problem
assignee = currentUser() OR reporter = currentUser()
statusCategory = "In Progress"
Combine the two and:
(assignee = currentUser() OR reporter = currentUser()) AND statusCategory = "In Progress"
Dashboard > "Two Dimensional Filter Statistics" Gadget filtered by Assignee / Status
statusCategory = "In Progress" AND assignee is EMPTY
statusCategory = "In Progress" AND assignee is not EMPTY
statusCategory = "In Progress" AND assignee = unassigned
statusCategory = "In Progress" AND assignee = "Unassigned"
Requested from Comments
What I am looking for from comments are:
I am running cloud instance:
JIRA Service Desk Application 3.3.0-OD-1000.2625.0
I can't seem to find "re-indexing".
Search indexing seems to indicate it's at:
Administration > System > Advanced > Indexing
When I follow that path I am presented with the following:
Advanced >
None of these seem to contain the indexing feature.
I didn't know this before, but cloud apparently doesn't have the manual reindexing option visible anymore.
You posted a lot of different JQL options, but I think that just your first example shows there's some kind of instance-specific failure rather than some general bug or incorrect JQL. So I'd recommend you contact support on this. http://getsupport.atlassian.com
Curious if you change the query to this, if ISSUE-1 shows:
assignee = myUsername or reporter = myUsername
assignee = [my username] OR reporter = [my username]
changes to:
assignee = admin OR reporter = admin
I also tried them separately which did not work either.
Thanks for the tip Josh, I'll make my way over to support.
FYI the link you provided is outdated and the page contains a link to:
https://support.atlassian.com/contact
Just to update on the resolution:
My project was set to the Administration > Issues > Issue Type Schemes > "Default Issue Type Scheme". This scheme only has Epic and Story issue types by default. ISSUE-1 was a Task issue type.
This was causing errors in filters because the issue type was not associated with the project "ISSUE". I had another issue let's call ISSUE-2, showing up correctly because it was a Story issue type.
I had already set up a custom Issue Type Scheme for the ISSUE project, but it was not currently associated.
I may have either accidentally, or through testing changed the Issue Type Scheme for the ISSUE project and forgot about it.
Because of the bug: Default Issue Type Scheme does not have all issue types and issues are not migrated to an existing issue type, I would not have been prompted to migrate my project from my custom Issue Type Scheme to the "Default Issue Type Scheme".
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreHey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs