That's not quite what Jobin asked - he asked if they were resolved.
Could you try running a filter for "assignee = me", record the number returned. Then try "assignee = me and resolution is empty" and compare the numbers.
Resolution is a system field that is always there. If you've somehow "hidden" it, you've pretty much broken your Jira installation.
Anyway, try "resolution = unresolved" - that should work despite any dubious hacks that might be hiding it. I expect it to return exactly the same number of issues you see in the "assigned to me" gadget.
What, exactly, is the "error" you keep mentioning when you run this search? "It doesn't work" does not really tell us much.
However resolution has been killed off, it sounds like a really dodgy hack, it should always be available to search, even if it's not visible in some or even all projects.
Also, however it's been killed off, undoing the damage is not actually going to fix the problem, just enable us to get to the bottom of it. Correct and proper usage of the field (even when hidden) is essential to Jira and that sounds like it might need fixing.
I can't find any way to actually break my installations that badly. Hiding it in every project doesn't prevent me searching it or anything.
The things that spring to mind though:
1. Are you using Jira in English? If not, then we might want to try finding out what the translation is. Or, temporarily swap your personal language selection to English and try it again.
2. You need to get your admin to enable your access to the resolution field, whatever they've done to cripple it.
Excellent, that answers your original question then. You're getting nothing in the "assigned to me" gadget because all your issues are resolved (i.e. they have a resolution set - it doesn't matter what the actual value of the field is, if there is *anything* in there, then the issue is resolved)
You've now got two pieces of work to do with your admin
First, you need to establish why things are all having their resolution set, and remove it. Issues should only get resolved when they move from a status that means "needs some attention" to a status that means "yep, we're done with this".
In the default workflow, those "done" status are "resolved" and "closed", but your workflow has probably been customised away from that.
Most importantly, look at the "reopen" transitions - they should clear the resolution. And check the transition screens only contain the resolution field when they're going into a "done" status.
Or, your admin has placed "resolution" on the "create issue" and/or "edit issue" screen - that needs to be removed
Or, your admin has added "unresolved" or some other resolution value that they think means "unresolved", but doesn't because *anything* in the field means "resolved"
Or, some/all of those three!
Once you've fixed the root-cause of these problems..
Second - fix the currently broken issues. You'll need to somehow reopen or edit any "open" issue to remove the resolution.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs