Versions Compared

Old Version 1

changes.mady.by.user Anna Ciepłota

Saved on

compared with

New Version Current

changes.mady.by.user Piotr Koszela

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of contents

Table of Contents

...

In this section, you can determine how time periods of the new tasks added to the scope react to other changes (e.g., task dependencies or parent/child relationship in the task structure) and align your tasks with the start/end dates of created Boxes.

Security and Access

  • Only a user with a minimum Box admin security role can access and change the Box configuration.

...

Configuration

  • You can set the period mode for each

    of the Boxes

    Box in Box Configuration > Tasks > Scheduling.

     To

    To access this page, you need the Box Administrator security role.

Info

You can set the default period mode used whenever you create when creating a new Box by configuring a Box type in App administration > Box types. To access the Box type configuration, you need an App admin security role.

  • The period mode can synchronize with Jira using a custom field - Select List (single choice) type, created during the installation. You can add this field to issue screens and change the period mode by editing the issue without opening the App.

Scheduling mode

Default scheduling mode is applied to new tasks (added to the scope of the Box for the first time).  If If a task is already within a the scope of any other Box, its scheduling mode will not be overwritten.

There are different ways to add tasks that will be treated as new. These include:

  • using the '+' (add task) button in different modules,

  • changing the Box scope - for example,

    add

    adding a new filter to the automatic rules,

  • we are updating the task

    so that it fits

    to fit within the Box scope definition - for example,

    move

    moving the task to a project added to the Box scope.

Info

We recommend using the 'Manual' period mode to assure ensure that your task will not be automatically rescheduled based on the configuration of structure builders and dependencies. You can always enable the automation at any time but you might not be able to easily revert changes quickly.

For example: , All tasks are in the auto bottom-up period mode, and the manual mode is set for newly added tasks - OA-135: Image Removed

...

Task period alignment

You can adjust the start and end dates of the task assigned to a Box (or sub-Box) so that they start and finish within the Box period.  Switching Switching to 'Precise alignment' or 'Smart adjustment' will reschedule all the tasks which were already assigned to those Boxes.

Info

This configuration applies to the Box which is configured and not to its sub-Boxes. If you want to align tasks only on, for example. the The Iteration level use uses the option - 'Set alignment on lower levels" described below.

...

Info

Please note , that this sync mechanism is:

  • unidirectional: planning tasks

    in

    using Boxes (for example

    :

    , Program Increments or Iterations) updates the tasks' to fit within the Boxes' duration. However, updating the tasks' date estimates does not add a task to the Box.

  • single-shot operation: a task period is

    always

    constantly updated once the task is planned for a Box (e.g., using the Board module), but if you adjust the task's period once it is

    planned

    scheduled for a box (e.g., on the Gantt module), the app will not validate the adjustment even if the new period would not fit the Box's period.

The update mentioned above -mentioned update of the task period will be appropriately executed properly only if all task scheduling rules (parent-child relation, period mode, inward dependency, etc.) allow executing execution of the operation. E.g. For example, if a Story has a parent task in the task structure that has with a "lock" mode set, the app may not update the Story period if it exceeds the parent period after the update. 

Please note , that once a task period is rescheduled, it may trigger a rescheduling of related tasks (linked tasks or parent/children in the task structure).

Set alignment on lower levels

This configuration applies to the sub-Boxes, and you can set the alignment for two levels of sub-Boxes.   For example: , the PI Planning Program Box consists of Program increment sub-Boxes -  which, in turn, consist of Iteration sub-Boxes. Image Removed

...

Task scheduling options

Info

To learn more, go to Task period alignment.

To Use the Precise alignment or Smart adjustment to update the date estimates at the task level use the Precise alignment or Smart adjustment.

Feature

Description

No alignement

Task's period will not align with the box's period. The fields mapped as start and end dates will not get updated when a task is planned in one of the Timeboxes.

Precise

alignement

alignment

(see Iteration 1)

Task's period will align

exactly

precisely with the box's period. The fields mapped as start and end dates will get updated to match the boxes start and end dates when a task is planned in one of the Timeboxes.

Smart adjustment

(see Iteration 2)

Task

The task's period will align to the ‘x's start or end

date of the box without changing the tasks duration (if possible). The fields mapped as start and end dates will get updated, when a task is planned in one of the Boxes, such that the task will start on the start date of the box (when moved to a future box) or end on the end date of the box if moved to a previous Box.

 The two Iterations have different Task alignment settings:

...

.” In this case, the task's duration will remain unchanged unless it exceeds the duration of the Timebox.

...

Other rules

...

that apply

...

are described in task period alignment (smart adjustment section of the document). 

...