Why does custom hierarchy issue display in plan sprint capacity and is also alert that issue is not assigned to sprint? Issue TTEG-12 OKR 1 is showing on the sprint capacity with 0 days even though it is a parent issue to the Epic. Did I miss a setting somewhere for the custom hierarchy?
Solved! Go to Solution.
This may be expected behavior but I'm not thrilled that our highest level hierarch is showing in the sprint capacity view. May need to submit an enhancement request on this one.