Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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

Dan H January 26, 2021

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 :(

ValueChanges.jpg

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

FieldValue.jpg

1 answer

1 accepted

4 votes
Answer accepted
Gareth Cantrell
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.
January 26, 2021

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 January 28, 2021

Brilliant, thank you very much Gareth!

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

Like Gareth Cantrell likes this
Dan H February 9, 2021

@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
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.
February 9, 2021

@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?

Dan H February 9, 2021

Certainly!

So on a ticket if an Original Estimate value is entered for the first time, it will 'fail' the first condition below (No Actions Performed)


Untitled.jpg

So what I'm trying to achieve is the following;

If Original Estimate value is entered (if blank/zero) OR changed then continue with rule.

 

I've attempted to do this by creating a second Rule with: timeoriginalestimate is greater than 0 (which works!) but now I've run into the problem of both Rules will successfully trigger anytime the value is changed :s

Like Mauricio Cordeiro likes this
Gareth Cantrell
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.
February 9, 2021

Hi @Dan H 

In the rule where you want to check when the field is initially populated, you need to look for {{fieldChange.field}} equal to timetracking.

For checking when the original estimate is updated, you need to look for {{fieldChange.field}} equal to timeoriginalestimate.

This behaviour is peculiar to the time tracking field and you can see this by using the "Log action" component and setting the smart value in the log message.

Like # people like this
Dan H February 9, 2021

Thank you again @Gareth Cantrell this works!

Two separate rules setup to handle both those conditions;

Untitled3.jpg

 

I did initially try to place both of these into ONE rule using If / Else block, but I failed to get that to work lol (screenshot below). What happens for me is that the second IF always fails, but I'm happy if this solution only works by creating two rule :)

Untitled2.jpg

Like Mauricio Cordeiro likes this
Gareth Cantrell
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.
February 9, 2021

I also noticed the else block would not evaluate the condition.

Probably worth raising a bug with Atlassian for this.

Like Dan H likes this
Iryna P.
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 26, 2021

@Dan H could you please share the formula in the "Edit issue field"? I can't find the right one to sum up Original Estimates of child issues

Daniel Ebers
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 29, 2021

Hi @Iryna P.

probably it would be better to ask a new question, unsure if many people will come back to this one here specifically after months having passed.

There is an example Automation rule which could get you started:
https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/1371692/26233950

You could have a look if it meets your needs. The above was an example back then, if I understood it right Dan wanted to send an mail in the end - probably as of now there is no formula for "edit" behind it for him.

Regards,
Daniel

Like Iryna P. likes this
Dan H January 24, 2022

@Iryna P. Certainly, this is what I use as the Edit Issue field:

Action: Edit Issue

Field: Original Estimate

Value: {{#=}}{{issue.subtasks.original estimate.sum}} / 3600{{/}}

 


Like so:

edit.jpg

Like # people like this
Aron Kuch November 2, 2023

Very interesting how a field is stored in seconds, and when you sum it and put the result in the same field, it assumes the inserted value is hours, and so you have to divide by 3600. (eyeroll)

James November 28, 2023

Now how do you use this value in conjunction with another operator? 

{{issue.Start Date.plusDays(issue.original estimate/21600)}}

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events