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!


Plan seems to ignore unestimated work with later fixversion

Deleted user Oct 06, 2017
I have an epic spanning fixversions with the latest version only containing unestimated work. I have unestimated item scheduling based on target dates. I expected in this scenario for portfolio to honour the fixversion dates, however it doesn't. Neither does it honour the target start and end dates if set. The only way I can find to get portfolio there is work in the later release and hence extend the timeline to incorporate that release is by assigning an estimate.
I must be doing something wrong or maybe there is a bug somewhere. Can anyone help?

2 answers

Hi, has this problem been solved? Thanks

0 votes
Olivier Dubois
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 13, 2017 • edited

Dear @Paul Smith,
When you have Unestimated item scheduling set to Base on target dates, an unestimated issue should be shown if it is assigned to a sprint, a release, or has target dates itself.
Try turning off Sprints in the Schedule settings (to right of the Calculate button) or have a look at the Target schedule. 
If this is not what you are looking for, please provide screenshots so we can better understand the problem. 
I hope this helps!
The Portfolio team

Deleted user Oct 22, 2017

Hi thanks for the response, and apologies maybe I was not as clear as I could have been.

My issue is purely with the end date of the epic in portfolio view. In the situation I described where there is no estimated work in the epic, however there are fixversions attached with dates against them, I would expect the epic duration to extend to the latest date of the fixversion attached to the epic.

Can you advise why this behaviour would not occur?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events