Closing an WI before Start No Earlier Than constraint leads to error message in Planning Problem Check (RTC 4.0.6: Traditional Planning Problems Check)
When creating a Release WI, we automatically create related Milestone WI with a constraint “Start No Earlier Than” (calculated from due date of the Release). As not all projects need all milestones, we defined a status “not applicable” (in OSLC Group “Closed”). Our Problem: when a Milestone (having a future start date, e.g. Oct, 15th,14) is set from initial status “new” to “not applicable” (e.g. on Oct, 1st), the “Traditional Planning Problem Check” creates an error message: ”The work item has a Start No Earlier Than constraint for 15.10.14, but it is planned to start on 01.10.14.” What other possibility do we have to “delete” unneeded work items? |
One answer
Ralph Schoon (63.1k●3●36●46)
| answered Oct 06 '14, 11:41 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I would suggest to remove the constraint “Start No Earlier Than” before closing the work item. It should not have the constraint in the first place, since you close it anyway. Alternatively you can make the state not a closed state. I assume you don't want that however.
I am not sure about this, but does this happen in the work item UI or only in the plan UI. If it happens in the work item UI as well, you could try to remove the constraint checking from the plan, but I assume you want it where applicable. Comments Unfortunately, your proposals don't solve our problem.
Heike, this has, for all I know, been designed that way.
There is a possibility to get less checks: "Planning Problems Checks". When using this check, the error message described above is not shown any more.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.