Forums

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

Issues having a blank resolution

Steffen Neumann
July 31, 2020

The resolution field of all my issues is blank. Therefore, they do not show up in the dashboard under my assigned issues. It is my understanding that the resolution should be displayed as unresolved if the resolution field is empty. I thus suspect that the resolution is set to an empty string for whatever reason.

Tickets don't show up in search when searching for Resolution IS EMPTY.

I did read a few threads about similar issues and ruled out the usual suspects: There is no custom resolution named Unresolved added. Re-indexing the project did not help. Finally, there is no post-function that manipulates the resolution.

Anything else I could check? Is there a way to search for empty strings in JQL to confirm my suspicion? Perhaps it's possible to work around this issue by auto-clearing the resolution field in a post-function?

4 answers

0 votes
valentina mannara
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 27, 2015

Hi I got also this problem. I think it's a bug for some type of customfield as SelectList, instead for Select List Cascade without associate searcher sorting works well.

Indeed a customfield w/o searcher is not searchable but it is sortable.

0 votes
Edgar Garcia
March 27, 2015

I got this issue too. The problem is that the Custom Field had no searcher defined, once the searcher was set I had to re-index the instance. That fixed it.

0 votes
John Hodgens
August 27, 2013

I should also point out that we are using the download version of JIRA and that it happens every time I try to sort.

0 votes
Jobin Kuruvilla [Adaptavist]
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 Champions.
August 27, 2013

Look at the atlassian-jira.log file. There must be some error that will help you indetify the issue.

John Hodgens
August 27, 2013

From the atlassian-jira log file, I believe this is the location of the error:

------------------------

2013-08-28 10:50:05,677 http-bio-8080-exec-9 ERROR hodgens 650x33945x2 1u65tct 172.16.3.80 /rest/issueNav/1/issueTable [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service

java.lang.ClassCastException: com.atlassian.jira.issue.customfields.option.LazyLoadedOption cannot be cast to java.lang.String

-------------------------

There is additional informational log info that I could also include if necessary.

Thanks

Suggest an answer

Log in or Sign up to answer