We have budget changing per Date though the Features, Bug, PBI and Task are scheduled, obviously, per Iteration / Sprint.
Though your support to change a budget per Work Item and even Work Log record is excellent, we have to take some effort to do this.
We have Features assigned to Iterations. Our best practice is to assign Budget per Feature
Since Features may not be complete per Date, but per Iteration, we would need to Duplicate the Feature and it Children and make sure Dev and QA stop working on Feature 1 - Iteration 1 + Budget 1 and start working on Feature 2 - Iteration 1 - Budget 2.
Of course, this is doable. But labor intensive.
Why not change Budget to new Budget? A: all previously entered Work Logs are moved over to new Budget. - also a valid use case, I understand.
When Assigning Budget 2 to Work Item:
[x] keep older work logs to Budget 1 (or something like until date dd.mmm.yy)
almost similar to this post but different https://support.7pace.com/hc/en-us/community/posts/360005373426-Feature-Request-for-Budget-over-Dates-instead-of-Iterations?input_string=Budget%20changes%20per%20CutOver%20date
Our ADO ref: HELP TICKET 610514
Please sign in to leave a comment.