...
As projects evolve, it is common for the project scope to change, at times requiring the creation of additional System Elements - . These new elements may be created in a variety of statuses - and alongside that , requiring the creation of additional Task Templates to ensure Task assignment for those new System Elements.
To accommodate project progress and help ensure completion of the entire project scope, Work Package Templates now allow distinguishing between generating Tasks for all distinguish between Task generation for All SE Statuses or future Future SE Statuses. The project administrator can create system elements System Elements in the appropriate status and use a single work package template to generate tasks. To support this functionality, the work package generator will only generate tasks Work Package Template to generate Tasks, and applying this new configuration option, the Work Package Generator will only generate Tasks for "future" statuses of a the System ElementElements.
It is important to note that once a task Task is created, it will not be deleted if the system element System Element transitions to other statuses. The tasks Tasks generated for a specific status will remain open until completed.
| Note | ||
|---|---|---|
| ||
In this context, a "future" status refers to a status that has a higher order number than the current status of the System Element. A System Element Life Cycle can include any number of statuses, and each is assigned an order number. These life cycle configurations are determined by the Instance Administrator. |
| Expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
Enhanced Labor Estimation and Calculation for System Elements
...