JQL
Use comparisons anywhere JQL is accepted
Save the query as a filter, use it on boards, add it to dashboard gadgets, reference it in reports or use it in Jira automation rules.
JQL Compare Fields for Jira Cloud
Extend Jira JQL with field comparisons.
Use custom JQL functions to find issues where actual work exceeds estimates, dates slip, or numeric fields disagree. The queries work wherever Jira accepts JQL: filters, boards, dashboards, reports, automations and Issue Navigator.
Early access: contact support.jira@mederak.app from a company email address.
Jira CloudAtlassian ForgeJQL functionsWorks in Jira filtersNo issue write permissionCustom fields
Problem
Jira has the data. Standard JQL is missing field-to-field comparisons.
Teams often need questions like “is time spent greater than original estimate?” or “is due date later than target date?”. JQL Compare Fields adds functions for those searches, so the result stays usable inside normal Jira views and workflows.
>
Compare real fields
Use operators such as >, >=, = and != across dates, numbers and durations.
F
Works with supported custom fields
Compare supported custom date, datetime and numeric fields by name or field ID.
Core capabilities
Built around JQL functions, with UI help when you need it
The app extends Jira search with reusable functions. Project checks and the visual builder help users create valid JQL, but the JQL itself is the portable output.
1
spentOverEstimate()Find issues where logged time is greater than the original estimate.
2
compareField()Compare the field on the left side of a JQL expression with another Jira field.
3
compareFields()Compare two named fields and return matching issues with one function call.
4
Optional builderUse the UI to create and preview syntax, then use the generated JQL wherever Jira accepts it.
Product views
Write JQL directly, or let the app help you build it
Use the function syntax by hand, start from a project quick check, or preview matching issues before reusing the query in Jira filters and dashboards.
Examples
Useful searches without spreadsheet exports
| Question | Generated JQL example | Use case |
|---|---|---|
| Which issues are over estimate? | issue in spentOverEstimate() | Quick delivery review. |
| Which open project issues are over estimate? | issue in spentOverEstimate("project = ABC AND statusCategory != Done") | Focused project cleanup. |
| Which due dates slipped past target date? | duedate > compareField("Target date", "project = ABC") | Schedule control. |
| Which numeric fields do not match? | issue in compareFields("Story Points", ">", "Planned Points", "project = ABC") | Planning consistency. |
Where it appears
Use the JQL in the Jira context you already rely on
- Saved filters and shared filter subscriptions.
- Board filters, swimlanes and quick filters that accept JQL.
- Dashboard gadgets and reporting views based on JQL filters.
- Jira automation conditions, branches or lookups that accept JQL.
- Issue Navigator searches and project-focused quick checks.
Questions before Marketplace launch
Is the Marketplace listing available?
Not yet. The listing is being prepared for Atlassian review. For early access, contact support.jira@mederak.app from a company email address.
Does the app edit Jira issues?
No. The app is designed around search and comparison. It does not request issue write permissions.
Where can I use the JQL?
Use it anywhere Jira accepts normal JQL, including Issue Navigator, saved filters, boards, dashboard gadgets and automation features that run JQL.
Why should searches be scoped?
Scoped searches are faster and clearer, especially on larger Jira sites. Start with a project, status or updated range.
Find mismatched Jira issues without leaving Jira.
Use early access while the Marketplace listing is under review. Please contact from a company email address and include your Jira use case.