How to auto-populate original estimate field based on two date picker fields?

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

How to auto-populate the Original estimate field based on two date picker fields on any Jira issue?

We will make use of Automation for Jira to achieve this use case.

Solution

  1. Let's assume there are two date picker fields available on the issue screen namely start_date  and duedate. To calculate Original estimate we need to find the difference between the duedate and start_date field. Every time start_date or duedate is edited, the rule should recalculate the Original estimate on the corresponding issue. To achieve this, here are the steps we need to follow:

    1. Navigate to Project Settings > Automation and click on the Create Rule button.

    2. Select the Trigger as Field value changed  and put start_date  and duedate  under Fields to monitor for changes  box.

      (Auto-migrated image: description temporarily unavailable)
    3. Then under action, select Edit Issue and choose the field Original Estimate  from the dropdown. Set the expression below

      1 {{start_date.diff(duedate).days}}d

      Feel free to refer to Jira smart values - date and time.

    4. Now, add or edit the start_date or due date fields on any issue, and the Original estimate will be calculated automatically based on the difference between these two fields.

      (Auto-migrated image: description temporarily unavailable)
    5. Rule details and execution will look something like below:

      (Auto-migrated image: description temporarily unavailable)

Updated on March 20, 2025

Still need help?

The Atlassian Community is here for you.