Content

Added by Bernd Petraus almost 7 years ago

Hi there,

I’m just testing the scrum functionality at the moment. And I like it very much. While playing around two questions came in my mind:

Is there a way to create constraints re. the work package hierarchy, depending on the work package typ? For example, a type “subtask” can only be splitted in other “subtasks” or “tasks” and a task can only be splitted in “process”, like it is done in classical project management approaches.

Furthermore, is there a way to create aconstraint re. the version? For example, that just work packages of type “task” can have a version.

That seems quite straight, but that would be necessary to fit in our acutal project management methodology.

Best regards

Bernd

Replies (2)

RE: Constraints in work package hierarchy and versions - Added by Robin Wagner almost 7 years ago

Hi Bernd,

it’s not directly possible to configure which work package can be set as a parent or a child but you can use a workaround to at least configure which types can or cannot have child work packages.
To do this you can configure a type to be a “milestone”. (“Administration” > “Work package types” > “Select type” > Check box “Is milestone”).
Types which are defined as milestones cannot have any sub work packages (you’ll receive an error message when trying to set a milestone as a work package parent).

Constraints regarding versions are currently not possible. You can only define whether or not work packages can be added to a version: When a version is set to “locked” or “closed” it is not possible to assign a work package to it.

Best regards,
Robin

RE: Constraints in work package hierarchy and versions - Added by Bernd Petraus almost 7 years ago

Hi Robin,

thank you for the hint. (using milestones as lowest hierarchy element) Unfortunately milestones are limited to one day, so there’s no way to define durations. But, good to know.

So, others may find this feature useful as well. I will create a feature on the wish list on tomorrow.