The workitem is due on..but is planned to be completed on ?
6 answers
I found the solution to my own problem. Not sure if it addresses the original question. I found that the Work Allocation needed to be adjusted under Work Environment for my user. Once the Work Allocation percentage was set correctly, the calculated start and end dates made sense and the messages went away.
Hi,
I am not sure why the same dates could cause this.
The general issue here is that you have set a due date DD/MM/YYYY but the iteration the work item is planned for ends after the due date. So RTC points out that fact to make you aware of it.
Thanks,
Ralph
I am not sure why the same dates could cause this.
The general issue here is that you have set a due date DD/MM/YYYY but the iteration the work item is planned for ends after the due date. So RTC points out that fact to make you aware of it.
Thanks,
Ralph
This could be a timing issue.
I get the 'problems detected' warning on a plan. It tells me that 'The workitem is due on 12/05/2011 but is planned to be completed on 12/05/2011.'
Why is this a problem ?
What kind of margin should we be using instead ?
Thanks.
Then how come I get a warning message:
The work item is due on 9/22/11 but it is planned to be completed on 9/28/11?
The sprint iteration is 9/18/11 - 10/14/11, so the work item is within the iteration. It shouldn't matter if the work item is planned to be done before the iteration. I actually have several workitems that say something similar to the warning message. The confusion is where it gets the 9/28/11 date from if the iteration is from 9/18-10/14??
The work item is due on 9/22/11 but it is planned to be completed on 9/28/11?
The sprint iteration is 9/18/11 - 10/14/11, so the work item is within the iteration. It shouldn't matter if the work item is planned to be done before the iteration. I actually have several workitems that say something similar to the warning message. The confusion is where it gets the 9/28/11 date from if the iteration is from 9/18-10/14??
That usually means that higher priority work is also scheduled for the
iteration, and given the amount of resources assigned to the team for
that iteration, they won't get to this work item until 9/28, i.e. after
its "due date".
Cheers,
Geoff
On 9/20/2011 2:23 PM, cojeff wrote:
iteration, and given the amount of resources assigned to the team for
that iteration, they won't get to this work item until 9/28, i.e. after
its "due date".
Cheers,
Geoff
On 9/20/2011 2:23 PM, cojeff wrote:
Then how come I get a warning message:
The work item is due on 9/22/11 but it is planned to be completed on
9/28/11?
The sprint iteration is 9/18/11 - 10/14/11, so the work item is within
the iteration. It shouldn't matter if the work item is planned to be
done before the iteration. I actually have several workitems that say
something similar to the warning message. The confusion is where it
gets the 9/28/11 date from if the iteration is from 9/18-10/14??
Any better follow up to this? I see similar behavior.
Version is 4.0.2
Work Item Due Date is 5/10/2013.
Iteration is 5/1/2013 - 5/20/2013
Estimate is 3 days
Messages:
The work item is due on 5/10/13, but it is planned to be completed on 6/12/13.
The work item is planned to be completed on 6/12/2013, while the iteration ends on 5/20/13.
I'm using Formal Project Management Template. The resource assigned to this work item shows 8% allocation.
Yes, this warning issue can be solved by updating their work allocations in individual profiles.
may they are part of multiple teams and their work is equally divided in work allocation but they would have planned activities only on one of the teams. in this case they will have to shift their allocation to that team where they have more amount of work to be done.