There are now many things that can be renamed resulting in broken filters. The Atlassian policy seems to be not supporting any way to automatically fix the problems caused. One work-around that covers all cases to a degree would be an administrative edit operation which allows changing constant values in all filters in a project. This would at least let me rename a component or a version or a user and have a way to repair most of the havoc that causes. I don't think this is particularly difficult since you can already parse jql. You just want to attempt a string substitution on every "value". If you want to be more precise you could make the substitution field specific. Or, if even this is too onerous, at least give us an admin ability to search the filters and find the damaged ones.