Box Type - Impact of Settings Changes
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
For example, changing a Tasks > Scope definition (Box types).
Boxes of the existing "Program" won't be affected. Their scope will remain as it was set up during the creation process.
a change applies to all boxes, both existing and newly created
Tasks > Quick filters functioning:
For example, you have a Program-type Box called "My Project." It contains three Program Increment Boxes.
The "Program Increment" Box type is set up with 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 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 only been added 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. This means filters from the Home (root) Box + Filters from the "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
For example, changing possible parent types of Boxes:
The "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 in the Box type settings impacts existing and new Boxes.
Settings | New Boxes | All Boxes | All Boxes | Can Box type settings be overridden for an individual Box |
---|---|---|---|---|
General > Basics > Box type name | X | Yes | ||
General > Basics > Prefix | X | NO | ||
General > Basics > Parent types | X | NO | ||
General > Basics > Icon | X | Yes | ||
General > Basics > Icon color | X | Yes | ||
General > Basics > Color | X | |||
General > Advanced > Sequentiality | X | NO | ||
General > Advanced > Period mode | X | NO | ||
General > Modules | X | Yes | ||
Tasks > Scope definition > Scope type | X | NO | ||
Tasks > Task Structure | X | Yes | ||
Tasks > Scheduling > Default period mode | X | Yes | ||
Tasks > Workload contouring > Default contouring mode | X | Yes | ||
Tasks > Quick Filters > Inheritance mode | X | NO | ||
Tasks > Quick Filters > Default Quick Filters | X | 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 assignment | X | Yes | ||
Gantt > Column Views > Inheritance mode | X | NO | ||
Gantt > Task Templates > Inheritance mode | X | NO | ||
Gantt > Task Templates > Default Task templates | X | Yes | ||
Scope > Column Views > Inheritance mode | X | NO | ||
Scope > Column Views > Default Column Views | X | Yes | ||
Board > Card Views > Inheritance mode | X | NO | ||
Board > Card Views > Default Card Views | X | Yes | ||
Roadmap > Business value > | X | |||
Roadmap > Colors | X | NO | ||
Risks > Card Views > Inheritance mode | X | NO | ||
Risks > Card Views > Default Card Views | X | Yes |