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.
Duplicate box and box scope
Duplicate box and box scope (old navigation)
Overview
You can create a new box by duplicating an existing box.
When you duplicate a box, the box configuration is copied. The app copies as much of the box setup as possible. Box type settings and defaults are ignored in favor of the exact setup of the box you are making a copy of.
You can't duplicate a box with all its contents and tasks.
You can use a Configuration of an existing box, duplicate it, and create a new box with an identical configuration. However, the scope of a box (tasks inside a box) isn't duplicated—tasks have to be added to the new box scope afterward.
Box configuration settings of a box are applied to the new box:
connected tools and the scope owner (tool connections get replicated)
Inheritance mode impacts the exact setup of the newly created box.
If some settings (such as column views or quick filers) were inherited from the upper-level boxes, if you move a new box to a different place in the box hierarchy, inherited settings can be lost. Inherited settings are always based on upper-level boxes and depend on placement within the box hierarchy.
Duplicate a box
Activate the actions menu
by clicking on the three dots menu icon on the right OR
by right-clicking on a box row
Select Duplicate configuration. A box creation pop-up appears.
The following fields are pre-filled:
Type (can’t be changed)
Name
Icon
Start date
End date
Jira Projects (not required)
available only for project boxes (can’t be filled in for boxes without their own scope, such as portfolio). Box scope can be adjusted later in a box configuration.
Click Create
What data is duplicated
Settings | Result |
|---|---|
Box scope | Not copied. The scope configuration is not copied. Box content is not replicated (spaces, tasks, issues etc). |
Sub boxes | Not copied Child boxes are not duplicated. |
Reports | Not copied Existing reports are not duplicated. |
Objectives | Not copied Existing objectives are not duplicated. |
Box settings | The following box settings are duplicated:
|
Box type settings | The following are the same for all boxes of a given type and can’t be modified for individual boxes:
|
Box type defaults and templates
When you duplicate a box, settings are duplicated directly from the box you are making a copy of. The box type templates are ignored.
Applies to:
Box roles
Column views and card views
Task templates
Default task templates are configured for the “LeSS Requirement Area” box type.
When a box is duplicated, default task templates of a box type are ignored. The actual task templates from a box are copied.
Inherited settings
Inherited settings are based on a position in a box tree and can’t be duplicated.
Clone a box scope
Scope cloning creates duplicates of tasks. This action creates tasks in a box you are currently in.
Configure the box scope - cloned issues will be added to a Jira project listed in the scope definition.
Click the + button (available in Gantt and Scope modules)
Select Clone existing scope. A dialog appears.
Select:
A box that contains tasks to be copied (source of tasks)
A Jira project duplicate will be created in (target project)
Click Clone
What data can be cloned
Data | Cloning result (Yes / No) |
|---|---|
Jira issue | yes |
Basic tasks | no |
Issue types | if possible When possible, the new issue has the same type as the one being copied.
|
Task structure | No Structure builders aren’t cloned:
|
Dependencies | yes |
Summary | yes |
Start / End date | yes The position of tasks on the timeline is preserved. Data is cloned according to field mapping.
|
Baseline start/end date | yes |
Other fields besides Summary and synchronized date fields | no Examples:
|
Skills | no |
Manual Colors | yes |
Milestones (based on Jira issues) | yes |
Milestones (based on basic tasks) | no |
Estimates |
|
Status | no The initial status of a project workflow is applied to all copied tasks. |
Version, Component, Sprint. | no During cloning, only Jira issues are created. The app does not make any other changes in the target Jira project; no other items, such as versions, components, or sprints, are created. |
Scheduling mode | no The scheduling mode of duplicated tasks is set based configuration of the target box. |
Clone failure - required fields
For a Jira issue to be created, all required fields must be filled in. The required fields are based on Jira settings and can vary from project to project.
The app copies a limited number of fields during cloning. If any required fields in the target project aren’t filled in during cloning, issues can’t be created.
Solution 1: make fields optional (adjust Jira settings)
Solution 2: import issues instead of cloning the scope
Export and import using Jira
You can use Jira to duplicate tasks:
Export the issues using Jira
Import data to the new target project
Import from a file
You can import data from the following files:
mpp
mpx
csv
xlsx
xlsx
ods
Prepare the export file
Set up a Jira project to which the tasks will be added to
Add the new project to the box scope
Run import
Duplicate box and box scope (new navigation)
Overview
You can create a new box by duplicating an existing box.
When you duplicate a box, the box configuration is copied. The app copies as much of the box setup as possible. Box type settings and defaults are ignored in favor of the exact setup of the box you are making a copy of.
You can't duplicate a box with all its contents and tasks.
You can use the configuration of an existing box, duplicate it, and create a new box with an identical configuration. However, the scope of a box (tasks inside a box) isn't duplicated—tasks have to be added to the new box scope afterward.
Box configuration settings of a box are applied to the new box:
connected tools and the scope owner (tool connections get replicated)
Inheritance mode impacts the exact setup of the newly created box.
If some settings (such as column views or quick filers) were inherited from the upper-level boxes, if you move a new box to a different place in the box hierarchy, inherited settings can be lost. Inherited settings are always based on upper-level boxes and depend on placement within the box hierarchy.
Duplicate a box
Activate the actions menu
by clicking on the three dots menu icon on the right OR
by right-clicking on a box row
Select Duplicate configuration. A box creation pop-up appears.
The following fields are pre-filled:
Type (can’t be changed)
Name
Icon
Start date
End date
Jira spaces (not required)
available only for project boxes (can’t be filled in for boxes without their own scope, such as a portfolio). The box scope can be adjusted later in a box configuration.
Click Create.
What data is duplicated
Settings | Result |
|---|---|
Box scope | Not copied. The scope configuration is not copied. Box content is not replicated (spaces, tasks, work items, etc.). |
Sub boxes | Not copied Child boxes are not duplicated. |
Reports | Not copied Existing reports are not duplicated. |
Objectives | Not copied Existing objectives are not duplicated. |
Box settings | The following box settings are duplicated:
|
Box type settings | The following are the same for all boxes of a given type and can’t be modified for individual boxes:
|
Box type defaults and templates
When you duplicate a box, its settings are copied directly from the box you are duplicating. The box type templates are ignored.
Applies to:
Box roles
Column views and card views
Task templates
Default task templates are configured for the “LeSS Requirement Area” box type. When a box is duplicated, the default task templates of a box type are ignored. The actual task templates from a box are copied.
Inherited settings
Inherited settings are based on a position in a box tree and can’t be duplicated.
Clone from another box
Scope cloning creates duplicates of tasks. This action creates tasks in the box you are currently in.
Configure the box scope - cloned work items will be added to a Jira space listed on the Work items from Jira page.
In the Gantt or Scope module, click Tasks.
Select Clone from another box. A dialog appears.
Select:
A box to clone the scope from.
A Jira space duplicate will be created in (target space).
Click Clone.
What data can be cloned
Data | Cloning result (Yes / No) |
|---|---|
Jira work items | yes |
BigPicture tasks | no |
Work item types | if possible When possible, the new work item has the same type as the one being copied.
|
Task structure | No Structure builders aren’t cloned:
|
Dependencies | yes |
Summary | yes |
Start / End date | yes The position of tasks on the timeline is preserved. Data is cloned according to field mapping.
|
Baseline start/end date | yes |
Other fields besides Summary and synchronized date fields | no Examples: |