QuantMatrix Intelligence

Filter & Dashboard Dependency Guard for Jira — Product guide

Install and open

Install the existing Cloud Marketplace app using Jira app administration. Start an active trial or subscription. A Jira administrator opens the Filter & Dashboard Dependency Guard administration page and runs the audit.

How it works

The app reads dashboards and filters visible to the current user, examines accessible dashboard gadgets and filter-related gadget properties, and reports dependency observations with warnings. It uses read-only GET requests as the current user; it does not modify dashboards, filters, gadgets or issues.

Permissions and data

The Forge manifest requests read:jira-work. The administration page is restricted to administrators. The resolver uses asUser() and an explicit read-only endpoint allowlist. The inspected resolver computes results per request without persisting report data. No remotes or external fetch permissions are declared.

Limits and interpretation

Search is bounded to two pages of 50 dashboards and filters. Gadget inspection covers the first 10 dashboards, up to 8 gadgets per dashboard, and up to 5 eligible filter property keys per gadget. Displayed rows are capped at 500. Gadget property availability varies. Missing visibility never proves a filter has been deleted. Warnings and incomplete pagination mean results are not exhaustive.

Troubleshooting

If subscription validation blocks a scan, verify the Marketplace trial or subscription. If access fails, verify the current user permissions and dashboard/filter sharing. Gadget properties may be unavailable even when a dashboard is visible; review warnings and validate dependencies manually before making changes. A Jira HTTP failure is reported rather than silently treating inaccessible data as deleted.

Support

Use the support page below and provide the app name, timestamp and a sanitized error description. Do not include credentials or private Jira content.

Product guide · Privacy · Support · Security