Check the examples your Jira filter must include—or exclude.
Save a small set of issue IDs and their expected membership. Run the saved filter, or compare it with a literal candidate query, before changing a board or report.
In development. Not yet submitted, approved or available for purchase on Atlassian Marketplace.
Keep repeatable expectations
Project administrators manage up to ten versioned contracts. Each contract uses a saved filter or draft JQL, up to fifty reference issues and optional exact-count bounds.
See the reason for a failed check
Read each example’s expected and observed membership. Incomplete or inaccessible sources produce no successful conclusion. A syntax or field-validation error is separate from an unmet expectation.
Compare before changing a filter
Compare the saved contract with a candidate query under your own permissions. The app reads both queries again and compares their common tested examples. It does not edit filters, boards or issues.
Keep a minimal personal history
Optionally retain your latest result for each contract revision for 30 days. Fresh permissions are required to read old counts. Copy a freshly generated CSV when needed.