Meet the new BigPicture navigation
A faster, smarter, and more intuitive way to work is here. We’ve redesigned BigPicture navigation to give you a smoother experience and better access to what matters most.
→ Discover what’s new, explore key improvements, and review feature name updates on the New navigation page.
→ The rollout will happen gradually, and the previous navigation will be retired in September 2026.
Box types - impact of settings changes
Box types - impact of settings changes (old navigation)
The impact of changes in the box type settings
Changing a box type's settings affects the boxes created with it. Depending on the settings, the change can affect the existing boxes, new boxes created after the change in settings, or both.
Change of the scope type
When you change the default scope type of the box type on the Scope definition page (box type configuration > Tasks > Scope definition), this change applies only to boxes you create afterward. Existing boxes are not affected.
The scope of the current boxes will remain as it was set up during the box creation process.
Change of the inheritance mode of the quick filters
Changes made to the inheritance mode of the quick filters (box type configuration > Tasks > Quick Filters) in the box type affect the existing and future boxes.
Let's consider the case of the theta Iteration box. It has two parents:
Home box (or Main; Portfolio type)
Program of Programs (Iteration box)
The inheritance mode of the quick filters in the Iteration box type settings is set to Own with inherited.
It means that all the current and future Iteration boxes will inherit the quick filters from all the parent boxes (marked with an arrow).
In addition, users can create custom quick filters in their Iteration boxes. The High priority tasks to do at the bottom of the list is theta’s own filter that you will not find in its parent boxes.
In such a case, these custom filters will be present only in the boxes where they were created, but not in the parent boxes.
When you change the inheritance mode of the Iteration box type to Inherited only, the custom filter will disappear from theta and all other Iteration boxes, and you will no longer be able to add any new quick filters.
The settings of the quick filters were changed in the Iteration box type.
|
| As a result, the Quick Filters page is no longer available on the box configuration page in theta (because users can no longer add new quick filters). |
|---|
The same changes will affect all existing and future boxes when you change the inheritance mode to Own. In such a case, the Iteration boxes will only keep their custom filters and lose the inherited ones.
Change in the box parent type
To create more advanced box hierarchies, you can set which box types can be parents to which boxes (box type configuration page > General > Basics > Parent types section). This change affects all the existing and future boxes. However, the change will not disrupt the current box hierarchy.
For example, let’s say you add the Program box type as a parent to the Classic project box type. As a result, you can nest the existing and create new Classic boxes under Home, Portfolio, and Program boxes.
When you nest a Classic box under a Program box, and then remove Program from the Parent type list, the existing nesting will remain unaffected. But once you move a Classic box out of the Program box, you will not be able to nest it back.
See the table at the bottom of this page to learn more about individual box type settings that affect boxes of a given type.
Update rules
The table below presents the rules that govern the changes made to box type attributes.
Update rule | Description | Example |
|---|---|---|
Existing boxes updated | New values for a box type attribute will automatically affect all existing boxes of a given type. | If you change the box type name attribute of an existing box type, a new box type name will be updated in every box of that type. |
Existing boxes affected (no invalidation) | New values for a box type attribute will not recalculate/change boxes according to the existing rules. All existing and new boxes of a given type will follow the new rules from the moment of the change. | You remove a type A and add a new type B in box type C’s Parent types attribute. Existing boxes of a given type will retain their current IDs. For example, PROG-23 will not be changed to PROJ-23. |
How box type settings impact existing and future boxes
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 | Box type settings can be overridden for an individual box of that type |
|---|---|---|---|---|
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 |
Box types - impact of settings changes (new navigation)
The impact of changes in the box type settings
Changing a box type's settings affects the boxes created with it. Depending on the settings, the change can affect the existing boxes, new boxes created after the change in settings, or both.
Change of the scope type
When you change the default scope type of the box type on the Work items from Jira page (box type configuration > Tasks > Work items from Jira), this change applies only to boxes you create afterward. Existing boxes are not affected.
The scope of the current boxes will remain as it was set up during the box creation process.
Change of the inheritance mode of the quick filters
Changes made to the inheritance mode of the quick filters (box type configuration > Tasks > Quick Filters) in the box type affect the existing and future boxes.
Let's consider the case of the theta Iteration box. It has two parents:
Home box (or Main; Portfolio type)
Program of Programs (Iteration box)
The inheritance mode of the quick filters in the Iteration box type settings is set to Own with inherited.
It means that all the current and future Iteration boxes will inherit the quick filters from all the parent boxes (marked with an arrow).
In addition, users can create custom quick filters in their Iteration boxes. The High priority tasks to do at the bottom of the list is theta’s own filter that you will not find in its parent boxes.
In such a case, these custom filters will be present only in the boxes where they were created, but not in the parent boxes.
When you change the inheritance mode of the Iteration box type to Inherited only, the custom filter will disappear from theta and all other Iteration boxes, and you will no longer be able to add any new quick filters.
The settings of the quick filters were changed in the Iteration box type.
|
| As a result, the Quick Filters page is no longer available on the box configuration page in theta (because users can no longer add new quick filters). |
|---|
The same changes will affect all existing and future boxes when you change the inheritance mode to Own. In such a case, the Iteration boxes will only keep their custom filters and lose the inherited ones.
Change in the box parent type
To create more advanced box hierarchies, you can set which box types can be parents to which boxes (box type configuration page > General > Basics > Parent types section). This change affects all the existing and future boxes. However, the change will not disrupt the current box hierarchy.
For example, let’s say you add the Program box type as a parent to the Classic project box type. As a result, you can nest the existing and create new Classic boxes under Home, Portfolio, and Program boxes.
When you nest a Classic box under a Program box, and then remove Program from the Parent type list, the existing nesting will remain unaffected. But once you move a Classic box out of the Program box, you will not be able to nest it back.
See the table at the bottom of this page to learn more about individual box type settings that affect boxes of a given type.
Update rules
The table below presents the rules that govern the changes made to box type attributes.
Update rule | Description | Example |
|---|---|---|
Existing boxes updated | New values for a box type attribute will automatically affect all existing boxes of a given type. | If you change the box type name attribute of an existing box type, a new box type name will be updated in every box of that type. |
Existing boxes affected (no invalidation) | New values for a box type attribute will not recalculate/change boxes according to the existing rules. All existing and new boxes of a given type will follow the new rules from the moment of the change. | You remove a type A and add a new type B in box type C’s Parent types attribute. Existing boxes of a given type will retain their current IDs. For example, PROG-23 will not be changed to PROJ-23. |
How box type settings impact existing and future boxes
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 | Box type settings can be overridden for an individual box of that type |
|---|---|---|---|---|
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 > Work items from Jira > Scope type | X |