---
title: "Duplicate box and box scope"
canonical: "https://support.appfire.com/space/DLP/2211189505/Duplicate%20box%20and%20box%20scope"
format: markdown
---
> Macro (aura-html)
## 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](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212266090) of a box are applied to the new box:
- [security (user roles)](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211580061)
- [modules and their settings](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211971495)
- [connected tools](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211938761) and the scope owner (tool connections get replicated)
> ℹ️ [Inheritance mode](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211125907) impacts the exact setup of the newly created box.
> ℹ️
> ℹ️ If some settings (such as [column views](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212266704) or [quick filers](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212529182)) 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
1. Activate the actions menu
1. by clicking on the three dots menu icon on the right OR
2. by right-clicking on a box row
2. Select **Duplicate configuration. **A box creation pop-up appears.
3. 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.
4. Click **Create**
### What data is duplicated
| **Settings** | **Result** |
| --- | --- |
| **Box scope ** | :cross_mark: Not copied.
The scope configuration is not copied.
Box content is not replicated (projects, tasks, issues etc).
 |
| **Sub boxes** | :cross_mark: Not copied
Child boxes are not duplicated. |
| **Reports** | :cross_mark: Not copied
Existing reports are not duplicated. |
| **Objectives** | :cross_mark: Not copied
Existing objectives are not duplicated. |
| **Box settings **:check_mark: | The following box settings are duplicated:
- Modules - the list of active/inactive modules
- Task structure
- Scheduling
- Task scheduling mode
- Task scheduling mode per task type
- Task period alignment
- Workload contouring settings
- Box roles
- Column views and card views (for Overview, Gantt, Scope, Board, and Risks modules)
- task templates
- Baselines permissions settings
- box lead |
| **Box type settings** | The following are the same for all boxes of a given type and can’t be modified for individual boxes:
- Scope type
- Sequentiality
- Box period mode
- Scheduling
- Story points
- Story point conversion ratio enabled/disabled
- teams enabled (inherited and manually created) |
### 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
Example
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.
1. Configure the box scope - cloned issues will be added to a Jira project listed in the **scope definition**.
2. Click the **+ **button (available in Gantt and Scope modules)
3. Select **Clone existing scope. **A dialog appears.
3. Select:
1. A box that contains tasks to be copied (source of tasks)
2. A Jira project duplicate will be created in (target project)
4. 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.
- :warning: **Epics **and** sub-tasks **are cloned as the **default issue type**. This means that after cloning, your new project doesn’t have any epics or sub-tasks.
- If Jira setup allows, the new issues are cloned with the same issue type.
- Otherwise, the default issue type is used. |
| Task structure | [No]
Structure builders aren’t cloned:
- Epics and sub-tasks are cloned as the default issue type. Therefore, it is not possible for an epic-based structure to be automatically recreated.
- The position of tasks manually moved can’t be recreated.
- Basic tasks aren’t cloned. Therefore, task structure based on basic tasks can’t be recreated.
- Versions, Components, and Sprints aren’t cloned and are not added to the target project during cloning. Therefore, the structure based on those elements cannot be automatically recreated. |
| **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:
- priority
- assignee
- labels
- team |
| Skills | [no] |
| Manual Colors | [yes] |
| Milestones
(based on Jira issues) | [yes] |
| Milestones
(based on basic tasks) | [no] |
| Estimates | - Original estimate [yes]
- Story points [no]
- Remaining estimate [no]
- Time spent [no] |
| 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:
1. Export the issues using Jira
2. 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
1. Prepare the export file
2. Set up a Jira project to which the tasks will be added to
3. Add the new project to the box scope
4. Run import
