Page Comparison

The article below refers to a situation when a task has been added to a single "Own scope" Box. 

For example, the following situation:

• Main Program-type Box has its "own" scope (tasks are added to scope definition of the Box)
• The project Box can be further divided ( for example, into Program Increments and Iterations)
• If Program Increments and Iterations are set up to function as "sub-scope" Boxes = their scope is based on the main Box.

In the example below, a task can be in the OMEGA Box (own scope) + Program Increment 1 (sub-scope Box) + Iteration 2 (sub-scope Box)
 

Start/end date not specified

When you create a task and don't specify start/end dates:

To find out more about tasks without start/end dates, click here. 

Start/end date overwritten

Based on scheduling rules, the App can make changes to:

• task duration
• task placement on the timeline

Priority of scheduling rules

General priority of scheduling rules:

1. Scheduling mode
2. Dependencies
3. Task period alignment

In reality, when you create a new task:

1. WBS is determined by:
   1. Structure builders
      1. structure builders can be based on dependencies
   2. Manual task placement (adding a task in a particular spot in the task structure)
2. Task period alignment applies
1. rules of the "own scope" Box
2. rules of the "sub-scope" Box → auto-assignment (sync with a selected field) 
3. Scheduling mode rules apply (based on WBS)
   1. auto top-down > auto bottom-up
4. Dependencies apply
   1. Strong dependencies dictate the placement of start/end dates
   2. Scheduling mode rules are prioritized. Dependency will still exist, but the outcome will be limited by scheduling mode

A newly created task changes based on other tasks, but it can also force other existing tasks to change.

Task creation (field values) - scheduling mechanisms involved in task period calculation

When adding a task, the fields you fill in determine what scheduling mechanisms apply and how they will position a task.

Depending on:

• the setup of a Box
• task fields filled in

Position in WBS

Task position in the tree structure will affect what scheduling rules apply. 

Position in the tree is vital, as it determines what task is in a role of a 'parent' and 'child.' Tree relationships determine how the scheduling mode rules are executed. 

Task place in WBS is affected by:

• structure builders
• where the task was manually created

Structure Builders

Example:

"Epic link" is listed as a structure builder:

The task is created directly in Jira. "Epic link" field has been filled in:

The task is nested according to structure builder settings of a Box:

Even when you try to create a task in a particular spot in the structure, it will be moved according to existing structure builders: 

Changing an existing task can result in a task being moved based on structure builders:

Inline task creation

Two key things to keep in mind:

• Between what tasks are you adding a task
• Is the structure expanded

Between same level tasks

When you create a task between the same level tasks (collapsed structure = two tasks on the same level), you will create a same-level task:

Task added:

Between different level tasks

The "add task" inline button can be positioned between different level tasks when the task structure is expanded. The resulting task is always created at the more indented level (nested lower in the structure):

Task added:

Additional example:

Add task button

Click on a task to select it (it will be highlighted in blue). A same-level task will be created when you use the "Add task" button, regardless of whether the tree is expanded.

Resulting task

Directly in Jira

When you create a task directly in Jira, it will be positioned at the least indented level possible and placed at the bottom of the list.

Task position in WBS will depend on the structure builder settings of a Box. 

Scheduling mechanisms

In the sections below, you can find an explanation of what each scheduling rule is trying to accomplish.

Scheduling mode

Tasks can be in one of four modes:

• Locked = task duration can't be changed (task unaffected by other scheduling rules; task limits period of children)
• Manual = task duration has to be changed manually (task unaffected by other scheduling rules)
• Auto top-down = task has to fit within the period of its parent 
• Auto bottom-up = task period changes the period of its parent
  
  

What is the scheduling mode of newly created tasks?

Box settings determine the scheduling mode of newly created tasks.

"Auto top-down" parent task

An "auto top-down" parent task forces a child to fit within its period. 

Affected tasks:

• other "auto top-down" tasks
• "auto bottom-up" tasks

During task creation:

"Locked" parent task

A "locked" parent task forces a child to fit within its period. 

Affected tasks:

• "auto top-down" tasks
• "auto bottom-up" tasks

During task creation:

"Auto bottom-up" parent task

An "auto bottom-up" parent task is affected by the period of any child (regardless of their scheduling mode).

Dependencies

Strong dependencies move a task on a timeline.

Without the involvement of another mechanism, dependencies don't alter the task period.

Dependencies have a lower scheduling priority than scheduling mode.

The source of a dependency remains in its original position - the target of a dependency is moved.

Task period alignment

Task period alignment settings of a Box regulate the relationship between a task and a Box it's in. 

Task period alignment won't be realized if it conflicts with parent task period mode requirements. 

Conflicts

Starting state to which scheduling mechanisms are applied:

Scheduling mode vs. dependency

Order of execution:

1. Scheduling mode is executed
   1. auto top-down parent = child adjusted to fit
   2. auto bottom-up parent = parent changed based on the child
2. Dependencies are executed
   1. task moved according to a dependency
   2. if the "auto bottom-up" parent period has been changed during the scheduling mode execution, it won't be further changed (for example, if the parent has been lengthened to encompass the new child, it won't 'shrink' back down, even if it would be possible after dependency moved the task)

Scheduling mode vs. task period alignment

Order of execution:

1. Task period alignment is executed
2. Scheduling mode is executed - it overwrites the previous changes if necessary

Dependency vs. task period alignment

Order of execution:

1. The task period alignment is executed.
2. The task is moved according to the dependency.

This means that based on task period alignment, a task can be shortened/extended and then moved on a timeline. Since dependencies themself don't modify the task period, task duration will be determined by task period alignment, but the position will be based on strong dependencies.

Dependency vs. task period alignment vs. scheduling mode

Order of execution:

1. Task period alignment is executed
2. Scheduling mode is executed
3. Dependency is executed