Bug tracking, issue tracking, and project management application
developed to make this process easier for your team.
Problem when updating a search filter
I'm not sure what's going on exactly under the hood, but when I edit some search filters I created earlier I got the following error screen when saving the filter:
The filter is based on a custom field I added which represent the actual Sprint number of the task (Scrum methodology).
The following warnings appear in the catalina.out logfile:
2008-02-27 12:37:32,605 http-8070-Processor22 WARN [webwork.view.taglib.IteratorTag] Value is null! Returning an empty set.
2008-02-27 12:37:32,657 http-8070-Processor22 WARN [webwork.view.taglib.IteratorTag] Value is null! Returning an empty set.
2008-02-27 12:37:32,657 http-8070-Processor22 WARN [webwork.view.taglib.IteratorTag] Value is null! Returning an empty set.
2008-02-27 12:37:32,657 http-8070-Processor22 WARN [webwork.view.taglib.IteratorTag] Value is null! Returning an empty set.
I searched the Jira bug tracking system, but I didn't find anything related.
So, I had to solve the problem somehow.
Update Jira Filters in the MySQL database.
All filter queries are stored in the table searchrequest inside the Jira database:
SELECT * FROM searchrequest s LIMIT 0,1000
To change a filter, just edit the reqcontent field by hand.
In my case, I just had to change the numeric value in one of the first lines:
<customfield name="customfield_10020" value="3">
If you are a MySQL guru, this will be no problem for you, but if not I recommend to use the visual query browser.
- Open your local MySQL data connection, mostly on localhost:3306.
- Double click the jiradb schema (or whatever your associated database is called).
- Double click the searchrequest table and press Ctrl-Return.
- Now you can see all stored filters.
- Scroll to the right to see the reqcontent column.
- Push Start Edition and click on the edit icon right to the field you want to modify.
- After changing the filter content press Apply modifications.
Now return to Jira's web interface and check that the filter works as expected.
It isn't necessary to restart Jira itself!
