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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Where is the original estimate field for next gen project issues?


My team's sprints typically encompass about seven legacy, and one next gen project on the same board. 

In the legacy projects, tasks have an original estimate field.  In the next gen project, they do not. 

Although you can log time against next gen project tasks, they are all listed as "unestimated" and original estimate is always given as zero.  This implies that one should be able to set original estimate for next gen project tasks; however, there is no field in which to do so. 

I have confirmed that for the current sprint, "Estimation" is set to "Remaining Estimate and Time Spent."

Is this a bug, a hidden config setting, or intentional?



1 answer

0 votes
Alexey Matveev
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.
Aug 02, 2019


You can estimate issues in next-gen projects only in Story Points. You should go to project settings -> Features and enable the Estimation option.

HUH?? how does this make sense?

Like # people like this

Alexy that is insufficient.  Atlassian has removed a capability key to our process, and thereby made things much more difficult to manage, apparently all without consulting their client base.  We rely on estimates in hours, AND in story points.  Hours estimated vs. actual hours is the most important metric in many respects.  Atlassian needs to restore this key functionality.

Like # people like this

Your right Jeremy. I understand Story Point estimations, however not having time estimations means as a Team we have lost the ability to select between the two, ultimately Jira has decided for us, for better or for worse. 

I think you should let us as users of the product decide if we want to use time estimation or story points, don't limit our choice! 

Like # people like this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events