Skip to end of banner
Go to start of banner

Box Type - Impact of Settings Changes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Changing Box Type settings can function in three ways:

  • a change applies only to boxes created from that point on - existing boxes are not affected

     Click here to expand...

    For example, changing a Tasks > Scope definition (Box types).

    Boxes of the type "Program" that already exist won't be affected. Their scope will remain the way it was set up during the creation process.

  • a change applies to all boxes, both existing and newly created

     Click here to expand...

    Tasks > Quick filters functioning:

    For example, you have a Program-type Box called "My Project." It contains three Program Increment Boxes.

    "Program Increment" Box type is set up to have quick filters "Own with Inherited." This means that the same filters available in the "My Project" Box (the parent of the Increment) are available in sub-Boxes + you can create new quick filters directly in Program Increments.

    You are inside the Box Configuration of one of the Program Increments in the picture below. Inherited filters are marked with an arrow. When you hover a mouse over any one of them, you can see the Key of the Box they come from (in our example, the Key of My Project is PROG-257). The "Program Increment Filter" has been added directly only to this Box.

    When you change the Box type settings of "Program Increment" and allow only for Inherited filters:

    You can no longer use the "Program Increment Filter" → only inherited filters are available. The tab that allows setting up filters for the Increment is hidden and cannot be accessed.

    Filters from upper-level Boxes are available. That includes all boxes to the top of the hierarchy. In this case, it means filters from Home (root) Box + Filters from "My Project" Box.

  • a change applies to all boxes, both existing and newly created, but the existing setup is not disrupted - future changes will be validated with new rules, but what you already have in place, you get to keep

     Click here to expand...

    For example, changing possible parent types of Boxes:

    "Program Increment" Box type can be nested under the "Program" type.

    If you change possible parent types, the existing structure won't be disrupted, but you won't be able to create new Program Increments under any Program-type Box (including "My Project").


The table below shows how a given change of the Box type settings impacts existing and new Boxes.

SettingsNew BoxesAll BoxesAll Boxes
(validation of future changes,
present setup preserved)
Can Box type settings be overridden for an individual Box
General > Basics > Box type name
X
Yes
General > Basics > PrefixX

NO
General > Basics > Parent types

XNO
General > Basics > IconX

Yes
General > Basics > Icon colorX

Yes
General > Basics > Color
X

General > Advanced > Sequentiality

XNO
General > Advanced > Period mode

XNO
General > ModulesX

Yes
Tasks > Scope definition > Scope typeX

NO
Tasks > Task Structure X

Yes
Tasks > Scheduling > Default period modeX

Yes
Tasks > Workload contouring > Default contouring modeX

Yes
Tasks > Quick Filters > Inheritance mode
X
NO
Tasks > Quick Filters > Default Quick FiltersX

Yes
Resources > Basics > Manually allocated teams
X
NO
Resources > Basics > Auto-inherited upper-level teams


NO
Resources > Basics > Configurable Story Point conversion ratio
X
NO
Security > Basics > Inheritance mode
X
NO
Security > Basics > Default security role assignmentX

Yes
Gantt > Column Views > Inheritance mode
X
NO
Gantt > Task Templates > Inheritance mode
X
NO
Gantt > Task Templates > Default Task templatesX

Yes
Scope > Column Views > Inheritance mode
X
NO
Scope > Column Views > Default Column ViewsX

Yes
Board > Card Views > Inheritance mode
X
NO
Board > Card Views > Default Card ViewsX

Yes
Roadmap > Business value >
X

Roadmap > Colors
X
NO
Risks > Card Views > Inheritance mode
X
NO
Risks > Card Views > Default Card Views
X
Yes




  • No labels