Filters might break


We want to update the priority names in our JIRA instance , but we are worried that any filters saved with old priority names might break. Moreover, if the filters are not shared with everyone, then it makes my job even difficult to assess the impact of my change.

What are my options to avoid this.

What about Updating the database table searchrequest with the new priority names. Is it recommended? Will my support be void if i make this change?

Any other option i have?



1 answer

1 accepted

1 vote
Accepted answer

We tend to avoid direct database manipulation, but it seems to be one of the cases that update the database is the only option. I find it hard to believe that support will be denied to you for doing this, I think that the only recommendation is to be careful, create a database backup and test the modifications in a test environment before executing the operation in production.


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,663 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