Allow work item budget inheritance with different iteration paths
Officially AnsweredIn our DevOps setup, we use iterations for tracking product releases as well as development sprints. I've attached a screenshot that illustrates our iteration hierarchy. In this setup, we align Epics, Features, and Backlog Items to the release iterations while tasks are worked in sprints (example screenshot attached). For 7pace we would like to setup budgets for each release by adding the release iteration to the budget definition and relying on inheritance through the epics and features to pick up the hours worked on each task. However, when the task is in a different iteration than the parent backlog item, 7pace does not seem to be able to resolve the inheritance from the backlog item iteration properly.
-
Hi Michael
if I understand this correctly, your task is not inheriting the budget from its parent work item because they are in different iterations. This is by design, the idea being that if you assign an iteration to a budget then that becomes the criteria we use to define what work should count against that budget. For a budget to be inherited from the Epic to the Task level, regardless of the iterations, you would need to assign it to the Epic itself. Would that be a viable option for you?
Kind Regards,
Andrea
Product Owner - www.7pace.com
Please sign in to leave a comment.
Comments
1 comment