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

Hours estimate by Month

Jimaline I'm New Here Nov 29, 2022


Been checking whether Jira is capable of capturing data - Hours estimates per month.

Undestood that, time tracking  -  original estimates is a cumulative hours , but we require to break down to months.


Any workaround to do this?



1 answer

1 accepted

0 votes
Answer accepted
Dave Mathijs Community Leader Nov 29, 2022

Hi @Jimaline welcome to the Atlassian Community!

The original estimate is the total amount of hours estimated for an issue, independent of the month. I don't see any use case where it would be relevant to break this down per month. You can however plan time (in Tempo f.e.) in hours on days which can be rolled-up by month.

The time spent is the actual which - of course - can be broken down per month.

Suggest an answer

Log in or Sign up to answer