nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Auto populate Original Estimate

sai chinamuthevi

Hello Guys,

we have two fields with name Start date(ID:10038) and end date(ID:10039). Both are date pickers

now my requirement is we want to auto populate value of original estimate based on difference between these two dates.

For example : issue created on september 2nd 2024, and end date mentioned as september 4,2024. i want to auto populate originall estimate as 2d

Accepted answers

Trudy P Claspill

Hello @sai chinamuthevi

Have you tried to create this rule? Please show us what you have so far.

What event do you want to trigger the setting of the Original Estimate field? Will that be when the issue is created?

What if Start date or end date is changed? Do you want the Original Estimate changed?

What if Start date or end date is cleared; how should that affect the Original estimate?

Should the calculation consider only Business days or all calendar days?

All comments

Trudy P Claspill

Hello @sai chinamuthevi

Have you tried to create this rule? Please show us what you have so far.

What event do you want to trigger the setting of the Original Estimate field? Will that be when the issue is created?

What if Start date or end date is changed? Do you want the Original Estimate changed?

What if Start date or end date is cleared; how should that affect the Original estimate?

Should the calculation consider only Business days or all calendar days?

sai chinamuthevi

Hi Trudy,

Yes i have created automation rule. But its showing success but Original Estimate is not updating. Please find my Rule screenshot for reference.
Yes when ever Target start and end date gets changes i want Original Estimate to be changed automatically too and it should consider business days only like 5days a week.

Screenshot 2024-09-17 114240.png

Trudy P Claspill

Hello @sai chinamuthevi

The original estimate is not updating because your syntax is wrong.

It appears that you are first trying to verify that both fields actually contain values. You can do that by adding Conditions to the rule rather than over-complicating the JSON code.

(I used Start date and End Date in my example. Replace those with the date fields you are using.)

Screenshot 2024-09-17 at 12.35.40 PM.png

Next, you don't need to use JSON at all. You can select the Original Estimate field and then set the value using a smart value.

Screenshot 2024-09-17 at 12.37.14 PM.png

The smart value you would use is:

{{issue.Start date.diff(issue.End Date).days.abs}}d

Again, substitute in the names (or customfield_##### designations) for the fields you actually use.

The .days.abs functions indicate you want the difference in days (vs. hours or any other time period) and you want the absolute value (not a negative value).

The d at the end is so that the number calculated will be submitted into the Original Estimate field as a value of days, just as if you manually entered 3d

sai chinamuthevi

Hi Trudy,
Its not working as expected. I'm getting below error

TP-35 (Specify a valid value for Original estimate (timetracking_originalestimate), Specify a valid value for Original estimate (timetracking))

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud