Stopping 'original estimation' field being changed once an issue enters a Sprint

[Debbie Hall]

I would like to create a rule that doesn't allow the original time estimate field to be amended once the Jira issue enters a Sprint.

Currently if I select 'Field Value Changed', the 'original estimate' field does not exist to be selected (the story point field does however).

Has anyone else had this issue and been able to work out why the original estimate field does not show up on the drop down?

Thank you!

[Bill Sheboy]

Hi @Debbie Hall 

While there are some fields which do not appear in the Field Value Changed list, for the Original Estimate you may select the more generic "Time tracking" and then check the changelog to detect when the Original Estimate was changed.

For example:

• trigger: Field Value Changed, selecting "Time tracking" and for "Edit work item" events
• smart values condition:
  • first value: {{#changelog.timeoriginalestimate}}{{fromString}}{{/}}
  • condition: does not equal
  • second value: {{#changelog.timeoriginalestimate}}{{toString}}{{/}}
• do something...

Kind regards,
Bill