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

Adding Original Estimate in Issue description

Joe.Craft1

Hello everyone, I have what I believe to be a relatively simple issue that I can't quite figure out. I am trying to determine how to display the original estimate within my issue, such as in the issue description, or to send it via email in project automation. I have tried many variations of {{originalEstimate}}, {{issue.originalEstimate}} to no prevail.

Does anyone have thoughts or a solution? Thank you!

Accepted answers

Stefan Salzl

Hi @Joe.Craft1 and welcome to the community,

seems you were really close. Try with a space between original and estimate.

{{issue.original Estimate}}

Looking forward to your feedback.

Best
Stefan

All comments

Stefan Salzl

Hi @Joe.Craft1 and welcome to the community,

seems you were really close. Try with a space between original and estimate.

{{issue.original Estimate}}

Looking forward to your feedback.

Best
Stefan

Joe.Craft1

Hey Stefan,

Thank you for the help! Getting the small details in the coding has been a fun learning curve for me, glad I was close.

Your solution does work - However, when our users enter original estimate, it's done so in minutes, i.e., 120m. The output I'm seeing is converting that number to seconds so in the case of 120m the output is showing us 7200. Typically I'd handle this via a formula in other programs I use. However, are you familiar with what the best-practice is for this in JIRA? Either if there is a convert function or if I'll need to do it via a formula?

Appreciate the help!

Joe.Craft1

For context, here's what I would typically do to convert seconds back to minutes. Let me know if you have any better options!

{{#=}}{{issue.original Estimate}} / 60 {{/}}

Stefan Salzl

I feel you. You are in good accompany 😂 I don´t see a consistent way of spelling of field names/smart values. And always discovering new properties =D

I don´t know any functionin this case either so would just do it the same way you suggested 👍

Welcome!

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

Quick Links

Find more posts tagged with

jira

automation