Skip to:

Marketplace

JQL Contract Tests for Jira

works with Jira Cloud

OVERALL RATINGS

SUPPORT

  • Partner Supported

TRUST SIGNALS

Showing details for Cloud

Key highlights of the appTest which examples your Jira filters should include or exclude

hero

Turn filter expectations into checks

Define issue IDs a saved filter must include or exclude, with optional exact-count bounds. Run checks manually using the current user’s Jira permissions. Incomplete or denied evidence never becomes PASS.

Compare a candidate query before changes

Compare a saved contract with a literal candidate query without editing the saved Jira filter. Complete bounded observations reveal membership or count failures; results expire after 60 seconds.

Keep optional personal check history

Keep the latest personal check for each contract revision for 30 days. Reading history rechecks current source permissions. Project contracts and personal history have separate deletion controls.

Supporting media

More details

Project administrators maintain up to 10 versioned contracts per project, with 50 reference issue IDs and optional exact-count bounds. Manually check a saved filter or compare it with a literal candidate query. PASS/FAIL reflect the current user’s complete observation, not every issue in the site or a transactional snapshot. Incomplete, denied, invalid or stale sources never become PASS. Personal history retains the latest check per contract revision for 30 days. Fresh CSV revalidates source access. Safety bounds: 8,000-character JQL, 1,000 visible matches per scan, 128 configuration revisions and a shared 150-call/20-second source budget. Results expire after 60 seconds. currentUser(), relative dates, permissions, indexing and issue changes can alter results. No scheduled monitoring, alerts, Jira writes, AI or external analytics.

Resources

  • App documentation

    Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy and security questionnaire has been filled by the partner

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Integration permissions

JQL Contract Tests for Jira integrates with your Atlassian app

Version information

Version 2.0.0•for Jira Cloud

Release date
Oct 3rd 2026
Summary
Manual membership and exact-count checks for Jira filters
Details

First Marketplace release. Save up to 10 contracts per project with up to 50 reference issue IDs, inclusion/exclusion expectations and optional exact-count bounds. Check a saved filter or compare it with a literal candidate query without modifying Jira. Complete bounded observations produce PASS/FAIL; denied, incomplete, invalid or stale sources do not become PASS. Personal history keeps the latest check per contract revision for 30 days. CSV and history revalidate source access. Manual execution only; 1,000 visible matches per scan and 60-second result freshness.

Payment model
Paid via Atlassian
License type
Commercial

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow