Project name change is not reflected in filters

When you change a project name, the JQL of any filter referencing the original project name is not updated. The result is broken filters.

Short of having to go into every filter and update the JQL, does any one have a workaround for this?

4 answers

1 accepted

0 votes
Accepted answer

This is a known problem in filter. Renaming things like issue type, versions, and etc could break the save filter. In this case, I suggest to save the filter using the project key instead of project name in Advance Searching.

Use always Project Key :)

0 votes

The only thing I can think of would be to export an XML backup, open it, use 'Search and Replace' on them and re-import the XML backup.

Or to try to update the 'reqcontent' column in the 'searchrequest' table of the database to change this - however, I'm not sure if this would break anything, so please backup JIRA before doing so.

I hope this helps!

Have there been any improvements to this known issue in newer versions?  We are using 6.2 and need to change a project name that's widely used in filters by thousands of users.  Please advise if there is a way to do so without breaking all the filters.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,653 views 18 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you