Delete filter associated with a deleted board

[Linda Korpås]

I have several filters that I wold like to delete but apparently is still associated with boards. I get this message:

"Before it can be deleted, remove its association to: XXX"

However I have tried to find the board to remove the association or to delete the board but the boards are no way to be found. I have searched in several places including System > Shared Items > Dashboards and also  using the search field on the top and then go to Boards , All Boards etc. 

What can I do? There must be a way to find the boards or to delete the filters anyway? 

I can add that when I click on the board mentioned I get to the information that the Project has been archived. But since this problem related to several projects/boards/filters I am not very happy about having to restore all these archived projects to be able to remove the filters. If this is what is needed I just might as well keep the filters. If I keep the "no-longer-needed-filters" , and I need to delete a user that happens to be the owner of such a filter, will the filter still be there but just now work if the owner is deleted? 

[Dave Mathijs · Accepted solution]

Hi @Linda Korpås 

Archived projects may indeed cause conflicts when trying to delete objects. So yes, you might have to restore possibly all archived projects to complete your action.

When a user is deleted in Jira, it can have several impacts on filters, depending on whether the user owned or was referenced in those filters. Here are some key areas to consider:

1. Filter Ownership

• Filter Deletion: If the deleted user owned any filters, those filters will no longer have an owner. In some configurations, this may cause the filter to be deleted automatically, or it may require manual reassignment.
• Reassignment of Filters: Jira admins may need to reassign the filters to a different user, or the filters may become unusable until ownership is reassigned.

2. Filters Shared by the User

• Shared Filters: If the deleted user had shared filters with other users or groups, the shared filters might become inaccessible, depending on how permissions were set up.
• Permission Issues: Other users may lose access to these filters, or the filters may no longer run as intended if the deleted user had unique permissions.

3. Filter References

• References to the User: If the deleted user was referenced in any JQL queries (e.g., assignee = "username" or reporter = "username"), those queries will break. The system won't be able to resolve the deleted user, causing errors in the filters that use such references.
• JQL Errors: Filters relying on user-specific data will need to be updated to remove references to the deleted user.

4. Gadgets and Dashboards

• Gadgets or Dashboards Using Filters: Any dashboard gadgets using filters created by or referencing the deleted user could stop working, showing errors or not displaying data as expected.

5. Notifications and Subscriptions

• Filter Subscriptions: If the user had active subscriptions to filters (scheduled filter emails, etc.), those subscriptions will stop being sent. Additionally, other users subscribed to filters owned by the deleted user might also experience interruptions.

Recommendations:

• Reassign Filters Before Deletion: It is good practice to reassign any critical filters, dashboards, or tasks owned by a user before deleting them from Jira.
• Review JQL Queries: Ensure that all JQL queries referencing the deleted user are updated to prevent errors in saved filters.

Handling these elements proactively helps prevent disruption to workflows and reporting within Jira.