Changing the JQLs in Oracle Database

[Priyanka]

I am trying to change the custom field values  to a new set of values and want to make sure the end users are not affected by the changes, i.e., I want to make sure the JQLs are not broken for them with the change in all the projects.

For example, I want to change the value in a custom field Environment from Test to QA.

Note that I have issue type = Test Case, Test

What is the best way to check and update the JQL in the database so that it does affect the JQLs that have issue type = Test or Test Case rather only replace Test of Environment field  as simple replace of the word does not work?

[Andy Heinzer]

Jira stores all the JQL saved filters in the database table called 'searchrequest'.  I'd recommend starting with

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

I know this works on postgres, but I'm not certain if Oracle has a different syntax here.

The reqcontent field in that table contains the specific JQL query being used for each filter.  I believe this SQL query will return all the filters that are currently using the term 'test'.  As for updating these, you could do this via SQL, but if you do so, I would recommend that you create a backup of your data, AND stop Jira before you make changes to this table.  Jira has a number of caches and updating SQL directly circumvents the way Jira is aware of these changes to the database.  By stopping Jira and making the direct SQL changes, you can be more certain that when you start Jira these previous caches are cleared.

[Priyanka]

Thank you Andrew. I will try your suggestion and let you know