Date Issue!
Hi,
We've noticed that when setting the dates for the milstone and release plan, one can set a date for the release plan which is prior to the end of a milestone plan. This also occurs when creating parents and children workitems links. that is: parent due date is before the childs due date. is there a way to control such thing from the process specification?
thanks
We've noticed that when setting the dates for the milstone and release plan, one can set a date for the release plan which is prior to the end of a milestone plan. This also occurs when creating parents and children workitems links. that is: parent due date is before the childs due date. is there a way to control such thing from the process specification?
thanks
4 answers
Our current implementation only marginally pays attention to the
semantics of dates. This is true inside single components (see your work
item example or inconsistencies you can produce between iterations of
the same project area) and between components (see your planning example).
In order to improve the situation we need to assess which of constraints
are 'natural' and therefore would have to be implemented by the
components. I'd put the dates of the iterations of a project area into
this category. Other constraints don't hurt the system but users might
want to enforce them. Those should be definable in the process
specification as you propose. We have most of the hooks in place (i.e.
most of the relevant operations can be impacted by the process
specification) but we are missing the right advisors/precondition
checkers at this point in time.
Cheers, Kai
farrugiarobert wrote:
semantics of dates. This is true inside single components (see your work
item example or inconsistencies you can produce between iterations of
the same project area) and between components (see your planning example).
In order to improve the situation we need to assess which of constraints
are 'natural' and therefore would have to be implemented by the
components. I'd put the dates of the iterations of a project area into
this category. Other constraints don't hurt the system but users might
want to enforce them. Those should be definable in the process
specification as you propose. We have most of the hooks in place (i.e.
most of the relevant operations can be impacted by the process
specification) but we are missing the right advisors/precondition
checkers at this point in time.
Cheers, Kai
farrugiarobert wrote:
Hi,
We've noticed that when setting the dates for the milstone and release
plan, one can set a date for the release plan which is prior to the
end of a milestone plan. This also occurs when creating parents and
children workitems links. that is: parent due date is before the
childs due date. is there a way to control such thing from the
process specification?
thanks
- consistency between dates of iterations is on the 0.6 plan
- aligning the semantics of dates across components in general is not on
the 0.6 plan, however individual components may look into some of the
issue for 0.6 but have to tell themselves what they will do
- you can not specify your constraints in the process specifications as
we are missing the necessary advisors/precondition checkers, providing
those is not on the 0.6 plan
Cheers, Kai
farrugiarobert wrote:
- aligning the semantics of dates across components in general is not on
the 0.6 plan, however individual components may look into some of the
issue for 0.6 but have to tell themselves what they will do
- you can not specify your constraints in the process specifications as
we are missing the necessary advisors/precondition checkers, providing
those is not on the 0.6 plan
Cheers, Kai
farrugiarobert wrote:
Hi,
So will the date issue be arranged or do we need to specify the
criteria within the process specification.... If so, is there a way
to view how this can be done.
Thanks in advance