Identify all saved filters using "issuetype = Theme"

Question

Hi all,

Way back when our version of Jira Server was installed, we thought it would be a good idea to rename the issue type "Epic" to "Theme" (don't ask why). 3 years later we now realise this was a bad idea and want to revert back to "Epic".

I know that if I simply edit this issue type and change the name back to "Epic" it's going to break any saved filters currently using it. Does anyone know of a way in which I can identify all the saved filters which are going to be impacted by this name change?

I also need to avoid impacting dashboards and Agile boards (Scrum & Kanban) and Confluence pages which use filters containing the issue type of "Theme" (originally known as "Epic").

Any advice would be much appreciated.

Thank you.

unknown · Answer

Hi Andy,

This is really useful, thank you :-)

I'll ask my DBA to run the query and let you know how it goes.

Adam

Andy Heinzer · Answer

Hi Adam,

It would probably be best to use some SQL to locate all the of the saved filters that would be affected by a change like this.  Even if you are a Jira admin, it is possible that other users have saved private filters that are only visible to them in the Jira web interface.  So I would not expect you to be able to find all the filters that contain this term via the Jira web interface.

Instead, accessing the database Jira is using, you can run a query like this

select * from searchrequest where reqcontent like '%Theme%';

This should return all the saved filters that have that specific term in it.  Given that JQL can have optional spacing between terms and that you could use type or issuetype to make this search, it might just be better to use the single word to find these.  I know this works on my postgresql database, the syntax could be slightly different for other database types.  This can at least give you back a list of all those filters.

I would recommend that you update these if possible through the web interface of Jira.  It might be possible to update the database directly, but these kinds of direct SQL changes are not supported by Atlassian.  If you want to go that route, I would recommend that you stop Jira first, and create a SQL backup before trying to do any SQL update commands.

I hope this helps.

Andy