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; } } }

How do I specifically use Original Estimate for Value Changes trigger, instead of Time Tracking?

Dan H_l259rx

Hello we have a rule setup that sends out an email notification anytime a User modifies the Original Estimate field on a ticket while it's in an active Sprint.

The problem with this setup is that the only option available to select for this from the Value Changes trigger is Time Tracking. So of course frustratingly this will also send email notifications out anytime someone modifies the Remaining Estimate field too

So would like to know if it's possible to have this automation setup but only apply specifically for the Original Estimate field?

Accepted answers

Gareth Cantrell_7nagel

Hi @Dan H

The {{fieldChange}} smart value which is set by the Field value changed trigger contains the following fields:

field
fieldType
from
fromString
to
toString

In the case of the Time tracking field, the field item will contain one of:

timeestimate
timeoriginalestimate

You can use these values in an Advanced compare condition to discover which time tracking field was changed as seen in the below image:

Screenshot 2021-01-26 at 14.44.19.png

All comments

Gareth Cantrell_7nagel

Hi @Dan H

The {{fieldChange}} smart value which is set by the Field value changed trigger contains the following fields:

field
fieldType
from
fromString
to
toString

In the case of the Time tracking field, the field item will contain one of:

timeestimate
timeoriginalestimate

You can use these values in an Advanced compare condition to discover which time tracking field was changed as seen in the below image:

Screenshot 2021-01-26 at 14.44.19.png

Dan H_l259rx

Brilliant, thank you very much Gareth!

Appreciate the clear, easy to understand response as well as including screenshot : )

Dan H_l259rx

@Gareth Cantrell Quick question, I use this condition in another very similar Rule but I'm getting in the logs that this doesn't appear to work if the Original Estimate is blank and then a value is entered (i.e. for new tickets created).

e.g. Original Estimate: ---> Original Estimate: 2d

Then no actions performed as it fails this advanced condition.

So not sure if I'm missing something?

Gareth Cantrell_7nagel

@Dan H if you're using a different trigger in your rule then the {{fieldChange}} smart value will not be set.

Could you attach a screenshot of your rule-chain view up to the point of the condition that's failing?

Welcome!

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

Quick Links

Find more posts tagged with

notification

time-tracking

estimate

automation