my query is -
project -EFM AND issuetype = incident AND status = Created ORDER BY created DESC
so you are saying that some issues returned by that filter have a Status other than "Created"? That seems very odd unless of course you have a secondary custom Status field which would be bad.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
further on what Joe is getting at here. If you have an actual Status that is named "Closed" and it is showing in your above filter results, something is very strange indeed. However, if by "closed" you are referring to an issue you believe to be closed by some means (resolution value, column on kanban, etc) but the actual Status value = "Created" then things are working as designed.
if you are still seeing issues here please post images of your filter and filter results.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Joe , yes in both Created and Closed they also have resolution , but no mater what resolution I give In Created filter some Closed ones are still showing.
Jack, there are two status value one is created and another is Closed. see these two pics in created and unresolved filter its showing closed issues
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is no resolution value of unresolved unless you have created one. JIRA shows unresolved when the field is NULL in the database. Try changing the search to look for NULL or empty.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agree with joe on the resolution part. I would also suggest you try a simple experiment.
run these two filters and compare them for Any overlap as there should be none.
project = efm and issuetype = incident and status = created
project = efm and issuetype = incident and status = closed
if you any overlap I would be interested in seeing this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.