Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Post Function due date based on original estimate that triggers on transition

Trying to find a Post-Function groovy script that can accomplish the need to:

  1. set the "Due Date"
    1. Only count Monday to Friday as viable days
  2. based on the "Original Estimate"
  3. But only when the task transitions from "To Do --> In Progress".


I am guessing that i would need to call an event to store the "original estimate" and then add that to the "new Date()" and then copy that to the due date.

Something along the lines of:

import java.text.SimpleDateFormat;
import java.util.Date;
SimpleDateFormat sdf = new SimpleDateFormat("dd/MM/yy");
Date dt = new Date();
long time = (dt.getTime()+(issue.get("timeoriginalestimate")/3600)/8);
String duedate = sdf.format(time);

Currently there are tasks that are estimated but cannot be started due to others in priority, therefore i cannot set a due date on an item.


2 answers

1 accepted

0 votes
Answer accepted

Found this thread in the forums:


The solution that i came up with was to add the groovy script in the:

Post Function inside: To Do --> In Progress, so when the user moves the issue to in progress the following will fire:


Update parameters of the Scripted (Groovy) operation on issue (JMWE add-on) Function for this transition.


import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.event.type.EventDispatchOption
import java.sql.Timestamp;
int days = (issue.get("timeoriginalestimate")/3600/8);
Calendar dueDate = Calendar.getInstance();

while (days > 0) {
dueDate.add(Calendar.DAY_OF_YEAR, 1)

/* Adjust for weekends > set to following Monday */
int dow = dueDate.get(Calendar.DAY_OF_WEEK);
if (dow == 7) {
dueDate.add(Calendar.DAY_OF_YEAR, 2)
} else if (dow == 1) {
dueDate.add(Calendar.DAY_OF_YEAR, 1)

issue.setDueDate(new Timestamp(dueDate.getTimeInMillis()));


I changed the day stamp from "14 days", to instead point to the "timeoriginalestimate" instead which solves the issue of needing to set a due date on anything from a planning standpoint and not knowing when the issue will be completed by.  Instead the due date will now be auto filled in based on the time estimate.

0 votes
Swati Kahol Atlassian Team Oct 02, 2020

Hi @Christian 

We have recently published a kb article to add Orginal estimate to a date field using Automation for Jira. Hope this helps :)


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

199 views 0 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you