JQL Integration & Issue Entity Properties

Dual Point Estimation stores estimate data directly inside Jira using Jira Entity Properties. Because entity property indexes are natively registered with Jira's search engine, you can query your range estimates using standard Jira JQL across custom search filters, board queries, Jira dashboard gadgets, and Jira Automation rules.

Entity Property Schema

The entity property is registered with key dualpoint-estimate:

• Property Key: dualpoint-estimate
• Property Values:
  • lowEstimate (number, stored in seconds)
  • highEstimate (number, stored in seconds)

JQL Syntax

In Jira JQL, access these properties using the issue.property[propertyKey].field syntax:

Note: Because values are stored canonically in seconds, query durations in seconds (e.g. 1 hour = 3600, 1 day / 8 hours = 28800).

Practical JQL Examples

1. Find All Unestimated Issues

Find issues in an active project that have no range estimate:

project = "PROJ" AND issue.property[dualpoint-estimate].highEstimate is EMPTY

2. Find Issues Exceeding 3 Days High Estimate

Filter for large tasks where the worst-case ceiling exceeds 3 working days (3 * 28800 = 86400 seconds):

project = "PROJ" AND issue.property[dualpoint-estimate].highEstimate > 86400

3. Find Tasks with High Spread / Uncertainty

Identify tasks where the High estimate is significantly greater than the Low estimate:

project = "PROJ" AND issue.property[dualpoint-estimate].highEstimate >= 57600 AND issue.property[dualpoint-estimate].lowEstimate <= 14400

4. Combine with Jira Agile Boards

You can use these JQL expressions as Jira Board Quick Filters or in Jira Automation triggers (e.g., auto-flagging tickets or sending a Slack alert when a high estimate exceeds a defined milestone threshold).