Filter "approximateLastUsed" datapoint accuracy

[Gary Spross]

I'm using the Search for filters API call to get a list of all filters within my instance so I can determine which ones are unused and therefore can be deleted. The datapoint "approximateLastUsed" is provided. How accurate do we really think this datapoint is? Accurate enough to use as the deciding factor on if a filter hasn't been used since last year and can therefore be deleted?

If this isn't a viable method for determining if filters are still being utilized, what methods are you using to audit the filters within your instance?

[Mohamed Benziane]

Hi Gary,

as stated by the documentation

Experimental] Approximate last used time. Returns the date and time when the filter was last used. Returns nullif the filter hasn't been used after tracking was enabled. For performance reasons, timestamps aren't updated in real time and therefore may not be exactly accurate.

so I will not use this data to make decision about deleting filter.

Since filter are used in dashboard and/or board it will be hard to audit filter whitout involving users

[Gary Spross]

Thanks @Mohamed Benziane. I saw that in the documentation which is what made me feel the need to pose this question about it.

So if that datapoint is potentially useless, then do you have any suggestions on how an admin can maintain the filters/dashboards/project boards within their instance?