Community
Q&A
Jira
Questions
Why can't I add the aggregated Original Estimate field to an Issue card

Why can't I add the aggregated Original Estimate field to an Issue card

This is a ridiculous limitation. I've spent hours try to build an automation to overcome this limitation to no avail. I want my team to be able to see the total estimate including the story/task estimate and the combined subtask estimates at the parent task or story level. Why isn't this an out of the box feature? I can't be the only person that needs this.

3 answers

1 accepted

4 votes

Answer accepted

You're definitely not the only one. This comes up quite a bit, especially for teams that estimate both parent issues and subtasks and want that total visible directly on the board.

I'd be interested to hear whether anyone has found a clean native workaround. It seems like a good candidate for a feature request, especially now that Jira is investing more in calculated fields like the new Formula Fields.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I ended up creating a custom field called Total original estimate and two convoluted automations that added up the original estimate on the parent task/story and the sum of any associated subtask. to populate the field on my card layouts. It took me hours of back and forth iterations with ChatGPT and only worked on items updated after I deployed the flow. It was very painful. I had to create a one time automation to update all of my existing issues. Teams managed projects have some ridiculous and painful limitations for things that seem very necessary to manage :( p.s. I tried to do this with Rovo but gave up. My experience with Rovo is it promises many things and sends me on wild goose chases only to end up telling me it can't actually do something.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

2 votes

Hello @Xenia Chilkowich

Did you tried this ?

Jira automation template showing how to sum up story points | Atlassian

Jira has a native aggregate field for this called Σ Original Estimate, available on company-managed Scrum and Kanban boards. You can enable it via Board settings → Card layout for both your Backlog and Active sprints views.

It acts as a read-only aggregate that automatically sums the parent item's estimate with all of its subtasks (for example, a 2-hour story with subtasks of 3 and 4 hours will display as 9 hours). Keep in mind this is purely for visual tracking on the card and won't overwrite the parent's own editable Original Estimate field.

Cheers,

Arek 🤠

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I am aware of this field. The limitation is that I cannot add it to the issue layout so it's only visible in list views. I need my team to be able to see this value when they open the relevant task or story. Also I am in a team managed project, which I am coming to see has many silly limitations. Thanks anyway

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Σ Original Estimate exists on company-managed Scrum and Kanban boards. You add it in Board settings → Card layout. It is a read-only display of parent plus subtask estimates. It does not write into the parent’s Original Estimate field, and it is not available on the issue layout when you open the work item.

Team-managed projects do not get that field at all. There is no setting that puts a rolled-up original estimate on the issue view in that project type.

If the team needs original / spent / remaining on the parent while they are looking at the work, that is a hierarchy view over the real issues, not a card-layout field.

Disclosure: I work on Aneto WBS.

Listing: https://marketplace.atlassian.com/apps/1219682/wbs-work-breakdown-structure

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Yes I learned the hard way that team-managed projects do not and in general I am unhappy with all the limitations of team-managed projects. I had to write a complex automation that caused me to exceed our flow limit. I wish JIRA would not limit team managed boards as much as it does. There is much room for improvement.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

We're moving! The community forums are migrating to a new platform on September 22. Learn more

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Why can't I add the aggregated Original Estimate field to an Issue card

3 answers

1 accepted

Suggest an answer

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PRODUCT PLAN

TAGS

Community showcase

Atlassian Community Events