Start and end dates variable built into tasks

[teresa mckinnon]

Hello all,

Is there a way to note a task duration in Jira? If I create a work item, can I use a variable to note how long that may take? For example, let's say I add a research epic or task, is there a way for me to note the length of that activity?

I will note that I am using the Templating App, so I will be creating a template of issues for a particular job that others would be able to copy and load onto their own boards or projects. I would like there to be a default time added with each task. Currently there is a date picker variable I can add, but that will only indicate a due date, not a start. 

Thank you for reading, let me know if clarification is needed!

[Robert DaSilva]

Hey @teresa mckinnon ,

As part of Jira's default work log tracking, they allow for tracking the estimated time a task will take. This is captured as part of the "Original Estimate" custom field. Here, you can insert the amount of time you expect a work item to take, and Jira will keep track of that.

Here's a great Community Article about the feature: https://community.atlassian.com/forums/App-Central-articles/Original-Estimate-in-Jira-A-Comprehensive-Guide-for-Better-Time/ba-p/2563458

And here's a screenshot of what the field might look like on your instance:

Hopefully that helps!

Robert

[teresa mckinnon]

Thank you, Robert!

[teresa mckinnon]

Hello Lukas, 

This is exactly what I was trying to set up. I have templating. and I wanted to note the length for each task. Thank you!

[Amit]

Hi @teresa mckinnon ,

If I understand correctly, you’d like to have:

• A field to hold the expected time to complete the task
• Another field (like Due Date or End Date) that gets automatically populated based on that duration

To achieve this, I’d suggest using the “Original Estimate” field to represent how long the task should take. Then, you can set up a Jira Automation rule that runs whenever an issue is created and automatically calculates the end date by adding the estimate to the issue's creation date.

Here’s a short outline:

• Trigger: Issue Created
• Action: Edit the Due Date (or custom End Date field)
• Smart value:
  issue.created.plusBusinessDays(issue.timeoriginalestimate.divide(28800))

(This assumes 8-hour workdays; 28800 seconds = 8 hours)

[teresa mckinnon]

Thank you, Amit!