Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to automate creating the value of Due Date to Actual Start Date?

Lisa Hauser
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 1, 2024

I'd like to automate the setting of "Due Date" by taking "Actual Start Date" and adding the "Original Estimate" time to it. So something like:
Due Date = Actual Start Date.value + Original Estimate.value

I've tried various forms of this - 

 

 

 

{{[Actual Start.value].plus[Original Estimate.value]}}

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 1, 2024

Hi @Lisa Hauser -- Welcome to the Atlassian Community!

Please try the date / time functions for plus[some unit of measure]()

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-plus-unit---

Assuming your "Actual Start Date" is a date / time custom field, and that is the correct smart value for the field:

{{issue.Actual Start Date.plusSeconds(issue.timetracking.originalEstimateSeconds)}}

 

To confirm the smart value (or custom field id) for your field, please see this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

 

Kind regards,
Bill

Lisa Hauser
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 6, 2024

Hi Bill, thanks for the quick response.  I've tried the following after finding the fields and values in the Json.  Any other ideas on how to automatically set the due date by adding original estimate days to the start date ?

{{issue.timetracking.Actual Start Date.plusSeconds(issue.timetracking.originalEstimateSeconds)}}

{{issue.Actual Start Date.plusSeconds(issue.timetracking.originalEstimateSeconds)}}

{{issue.customfield_10008 Date.plusSeconds(issue.timetracking.originalEstimateSeconds)}}

{{issue.customfield_10019 Date.plusSeconds(issue.timetracking.originalEstimateSeconds)}}

{{customfield_10008 Date.plusSeconds(issue.timetracking.originalEstimateSeconds)}}

{{customfield_10019 Date.plusSeconds(issue.timetracking.originalEstimateSeconds)}}

{{customfield_10019.customfield_10008 Date.plusSeconds(issue.timetracking.originalEstimateSeconds)}}

Here is the Json sections where I found the fields:

"timetracking": {

      "originalEstimate": "2d",

      "remainingEstimate": "2d",

      "originalEstimateSeconds": 57600,

      "remainingEstimateSeconds": 57600

customfield_10019": "0|i1cx0r:",

And I believe this is the Actual start date -

customfield_10019": "0|i1cx0r:",

   "customfield_10008": "2024-08-06T09:07:00.000-0700",

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 6, 2024

Several of those smart value expressions you show are invalid and will not process. 

The example I provided will work if that is the correct smart value / custom field id for your field.  Have you confirmed the smart value for your field, as I described in my first post?

 

To provide more context, please post images of:

  • your complete automation rule in one single image file
  • your audit log details showing the rule execution, in one single image file

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events