Changeset View
Changeset View
Standalone View
Standalone View
src/docs/user/userguide/projects.diviner
| Show First 20 Lines • Show All 178 Lines • ▼ Show 20 Lines | |||||
| Subprojects can have their own subprojects, milestones, or both. If a | Subprojects can have their own subprojects, milestones, or both. If a | ||||
| subproject has its own subprojects, it is both a subproject and a parent | subproject has its own subprojects, it is both a subproject and a parent | ||||
| project. Thus, the parent project rules apply to it, and are stronger than the | project. Thus, the parent project rules apply to it, and are stronger than the | ||||
| subproject rules. | subproject rules. | ||||
| Subprojects can have normal workboards. | Subprojects can have normal workboards. | ||||
| The maximum subproject depth is 16. This limit is intended to grossly exceed | |||||
| the depth necessary in normal usage. | |||||
| Objects may not be tagged with multiple projects that are ancestors or | |||||
| descendants of one another. For example, a task may not be tagged with both | |||||
| {nav Stonework} and {nav Stonework > Masonry}. | |||||
| When a project tag is added that is the ancestor or descendant of one or more | |||||
| existing tags, the old tags are replaced. For example, adding | |||||
| {nav Stonework > Masonry} to a task tagged with {nav Stonework} will replace | |||||
| {nav Stonework} with the newer, more specific tag. | |||||
| This restriction does not apply to projects which share some common ancestor | |||||
| but are not themselves mutual ancestors. For example, a task may be tagged | |||||
| with both {nav Stonework > Masonry} and {nav Stonework > Sculpting}. | |||||
| This restriction //does// apply when the descendant is a milestone. For | |||||
| example, a task may not be tagged with both {nav Stonework} and | |||||
| {nav Stonework > Iteration II}. | |||||
| Milestones | Milestones | ||||
| ========== | ========== | ||||
| Milestones are simple subprojects for tracking sprints, iterations, versions, | Milestones are simple subprojects for tracking sprints, iterations, versions, | ||||
| or other similar blocks of work. Milestones make it easier to create and manage | or other similar blocks of work. Milestones make it easier to create and manage | ||||
| a large number of similar subprojects (for example: {nav Sprint 1}, | a large number of similar subprojects (for example: {nav Sprint 1}, | ||||
| {nav Sprint 2}, {nav Sprint 3}, etc). | {nav Sprint 2}, {nav Sprint 3}, etc). | ||||
| Milestones can not have direct members or policies. Instead, the membership | Milestones can not have direct members or policies. Instead, the membership | ||||
| and policies of a milestones are always the same as the milestone's parent | and policies of a milestones are always the same as the milestone's parent | ||||
| project. This makes large numbers of milestones more manageable when changes | project. This makes large numbers of milestones more manageable when changes | ||||
| occur. | occur. | ||||
| Milestones can not have subprojects, and can not have their own milestones. | Milestones can not have subprojects, and can not have their own milestones. | ||||
| By default, Milestones do not have their own hashtags. | By default, Milestones do not have their own hashtags. | ||||
| Milestones can have normal workboards. | Milestones can have normal workboards. | ||||
| Objects may not be tagged with two different milestones of the same parent | |||||
| project. For example, a task may not be tagged with both {nav Stonework > | |||||
| Iteration III} and {nav Stonework > Iteration V}. | |||||
| When a milestone tag is added to an object which already has a tag from the | |||||
| same series of milestones, the old tag is removed. For example, adding the | |||||
| {nav Stonework > Iteration V} tag to a task which already has the | |||||
| {nav Stonework > Iteration III} tag will remove the {nav Iteration III} tag. | |||||
| This restriction does not apply to milestones which are not part of the same | |||||
| series. For example, a task may be tagged with both | |||||
| {nav Stonework > Iteration V} and {nav Heraldry > Iteration IX}. | |||||
| Parent Projects | Parent Projects | ||||
| =============== | =============== | ||||
| When you add the first subproject to an existing project, it is converted into | When you add the first subproject to an existing project, it is converted into | ||||
| a **parent project**. Parent projects have some special rules. | a **parent project**. Parent projects have some special rules. | ||||
| **No Direct Members**: Parent projects can not have members of their own. | **No Direct Members**: Parent projects can not have members of their own. | ||||
| ▲ Show 20 Lines • Show All 101 Lines • Show Last 20 Lines | |||||