# Feature SPAR-10 - Template or copy a task cluster with all relations

Project: Stream Planning and Reporting
Status: new
URL: https://community.openproject.org/work_packages/SPAR-10

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Votes | 7 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

Current status.

Example hierarchy:

Work package\> Phase\> Feature\> Task

Different tasks are individual tasks that are part of a high-level feature. These can have dependencies on predecessors or successors, block other tasks, etc. Features are groupings that define logical blocks and should be processed in a phase. A phase represents a period or storyline, such as a master's thesis or a sub-project. All tasks that aim at a project-relevant milestone are subordinate to the work package.

It is currently possible to create templates for projects and create them as sub-projects. All relationships between the tasks and the like are adopted. Unfortunately, the start date of the template is also used here as the start date of the newly created sub-project. Thus, all tasks (children) have to be drawn individually by hand to their new start date.

Setting a start date when creating the sub-project means that all relationships that represent subsequent dependencies are overwritten and all tasks are given the same start date.

Suggested solutions:

Part proposal 1:

Templates are created in order to insert them into a project and to have all predefined processes directly at place and time.

a)

A shift function that made it possible for all children to move in correct correlation due to the parent's movement over time.

or

b)

When creating the sub-project from a template, set a global start time that only defines the (sub) project start, but positions the tasks according to their dependencies.

(Example:

Phase \[Master's thesis\]\> Features \[introduction, implementation, results\]

The introduction starts with the beginning of the master thesis. The implementation begins 4 weeks later, but is not a follow-up task to the introduction. But the results follow the implementation.

When creating the sub-project, the start of the master's thesis should now be set. In this context, the introduction also starts, but the implementation only 4 weeks later.\]

Part proposal 2:

a)

Parents can be copied with their children and their respective relationships, provided that they are closed in their parent-child relationship.

or

b)

Parents can be copied and all subordinate children are copied together with all relationships, provided that there is no circular argument.

If a circular argument arises, an error message is issued, what causes this and the copy is completely reversed.