Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

How can I automate the Baseline end date field when input Original estimate?

I would like to automate the Baseline end date field when I input the original estimate data. In "original estimate" I would like to input the working days needed to complete the task. If Original estimate is not the correct field, please can you tell me which is the best one?

Thanks 

1 answer

1 vote
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 11, 2022

Hi @Chiara Bonello and welcome to the community!

You could go about it with automation like this:

  • TRIGGER: Field Value Changed (Original Estimate)
  • ACTION: Edit Issue (Baseline End)
    • {{now.plusDays(issue.Original Estimate)}}

Hi Mark thank you.

I tried to do it, but unfortunately when it comes to input Original Estimate I cannot find it (check the pic below). When i start typing, above the drill down menu there is the following writing: "SHOWING 50 OF 132". This means that I cannot see all the available fields.

Can you help me in solving this trouble? 

Thank you

Immagine1.png

Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 12, 2022

I have to be honest... I haven't worked specifically with the Original Estimate field and had to do some research.  It looks like it's intended for boards that are configured for time tracking and specific to Time Tracking reporting:

Time Tracking Report *

Shows time tracking information on issues for a particular version of a project.

The table in the report shows the issues within the version:

  • There are four time tracking fields as follows:
    • Original Estimate - The original estimate of the total amount of time it would take to complete this issue.
    • Estimated Time Remaining - The current estimate of the remaining amount of time it would take to complete this issue.
    • Time Spent - The amount of time spent on the issue. This is the aggregate amount of time that has been logged against this issue.
    • Accuracy- The accuracy of the original estimate compared to the current estimate for the issue. It is the difference between the sum of the Time Spent and Estimated Time Remaining fields, and the Original Estimate field.

Here's more info:

https://support.atlassian.com/jira-software-cloud/docs/generate-a-report/

I recommend you use a different numeric field to capture this information.  What I shared in my initial answer would still work the same, you'd just need to substitute Original Estimate for whatever field you end up using.

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events