Filters and dashboards

Filters lists every filter and the dashboards TuneCraft can see, with Jira's evidence of their use, and lets a Jira admin give them a new owner or delete them after a preview. It is the first tool that changes Jira.

Before you start

Filters is for Jira admins. A Jira admin turns on its background checks in Filters settings. TuneCraft then reads the filters about once a week, and the dashboards once a week as well. On a large site this takes days or weeks, within TuneCraft's points budget. To see which flows use a filter, scan your automation export first. A filter that flows use is never deleted.

The Filters page

Each filter shows:

• its owner, and whether Jira shows the owner as an active person;
• when it was last used (Jira's approximate day), its favourites, subscriptions and shares;
• whether Jira still accepts its JQL. Jira checks each filter's JQL strictly, so a filter whose JQL names a field, a value or a function Jira no longer has shows as refused;
• its copies: filters with the same JQL, whatever its case and spaces;
• the flows of the last scan that use it, for example a flow that searches with filter = 10001, or by the filter's name.

You can filter by "not used for" a number of months, which a Jira admin sets in Filters settings. The list downloads as CSV.

The Dashboards page

Dashboards shows the dashboards TuneCraft can see, the least favoured first: their owner, favourites, gadgets, shares and state (In use, Archived or Deleted). Gadgets are counted when you ask, dashboard by dashboard.

Jira shows dashboards only to their owner and the people they are shared with, with no admin override. A private dashboard of someone who left is therefore not listed. Jira lets only a dashboard's owner delete it.

Change an owner or delete

Select the filters or dashboards, then choose to give them a new owner or to delete them.

1. TuneCraft shows a preview, read from Jira as you.
2. For a delete, it first downloads a record file to your computer, with each object's name, owner, description, JQL, shares and gadgets. Jira keeps nothing of a deleted filter or dashboard. TuneCraft keeps none of that record.
3. You confirm. Just before the change, TuneCraft reads the object from Jira again. If it was used, favourited or changed owner since, nothing is changed and you preview again.
4. The change is made as you. Jira's audit log records it under your name.

A dashboard that someone else owns is deleted in Jira's own dashboards page. A filter that flows use cannot be deleted, and giving it a new owner needs a tick box to confirm.

Changes and undo

The Changes page lists every change TuneCraft made in Jira with this tool, newest first. For 30 days it can give a filter or a dashboard back to its previous owner, unless the owner changed again since. Undo works without a licence and does not count toward a trial limit.

What Filters cannot see

• Boards that use a filter, and dashboard gadgets that name one, are not checked. Open the filter in Jira before you delete it.
• Jira lets no app remove another person's subscription.

What it costs and what it keeps

A reading costs about 2 Jira points for each filter and 1 for each dashboard (measured). For each filter TuneCraft keeps its id, its owner's account id and whether Jira shows them as active, its last use as a day, its counts, how it is shared, whether Jira accepts its JQL, a code made from its JQL to find copies (never the JQL), and what its JQL names, by id. It keeps no filter or dashboard name. Records of changes are removed after 400 days, and each change's objects after 30 days.

During a trial, every report works and changes are limited to 10 objects for this tool. See Licence and trial.

Questions about the app? Write to info@plugincraft.ca.