---
title: "Preserving Multi-Level WBS Hierarchy When Cloning in BigPicture"
canonical: "https://support.appfire.com/space/SUPPORT/3687383074/Preserving%20Multi-Level%20WBS%20Hierarchy%20When%20Cloning%20in%20BigPicture"
format: markdown
---
# Preserving Multi-Level WBS Hierarchy When Cloning in BigPicture

This article covers multiple methods for duplicating work structures while maintaining hierarchical relationships in BigPicture, including the "Clone from another Box" feature and alternative approaches using Issue Links or BigTemplate imports.

## Summary

When cloning a template Epic or a set of issues in BigPicture, users often find that the custom hierarchical structure (WBS) is lost, resulting in a flat list. This article outlines how to correctly use the built-in cloning features to preserve hierarchy and provides alternative solutions for partial clones or external imports.

---

## Use Case 1: Cloning an Entire Work Structure (Box to Box)

This method is used when you need to duplicate an entire project or Box structure, including multi-level hierarchies, dependencies, and placeholders.

### Solution: "Clone from another Box" Feature

To ensure the hierarchy is preserved during a Box clone, verify the following configuration requirements:

1. **Field Configuration:** Ensure all custom fields in the target Jira project schemes are set to **"Optional"** before starting the cloning process.
2. **Issue Type Mapping:** The target Jira project must contain all issue types used in the template. If an issue type is missing, BigPicture will map it to the project's default issue type (e.g., Task or Story), which may break the intended hierarchy.
3. **Structure Builders:** In the target Box, navigate to **Configuration > Task structure**. Ensure the exact same **Structure Builders** (e.g., Epic links or specific issue link types) are active. This allows BigPicture to interpret Jira links correctly as hierarchy levels.

**Reference Documentation:**

- [Clone tasks / Clone from another box](https://support.appfire.com/space/SPM/1918636677/Clone+tasks+%2F+Clone+from+another+box)
- [Manage task structure & Automatic task structure](https://support.appfire.com/space/SPM/1918667217/Manage+task+structure#Automatic-task-structure)

---

## Use Case 2: Partial Cloning or Selective Structure Copying

If you do not need to clone an entire Box but only specific parts of a template, a full Box clone may be inefficient.

### Solution: Reorganizing via Issue Links

Instead of relying on a flat clone, reorganize the template's task structure to use **Issue Links** as the primary hierarchy driver.

- By defining the hierarchy through specific link types (e.g., "is parent of"), you can copy only the required work items.
- Ensure the target Box's **Task Structure** settings are configured to recognize these link types to automatically rebuild the WBS upon import or link creation.

---

## Use Case 3: Importing WBS via External Files

For users who prefer managing templates externally or need to move structures between disconnected environments.

### Solution: BigTemplate XLSX/CSV Import

You can import a multi-level Work Breakdown Structure into a new Box using the BigTemplate add-on.

1. **Prepare the File:** Use the XLSX/CSV format.
2. **Define Hierarchy:** Use the **"Parent row"** field. Enter the number corresponding to the Excel row where the parent task is located.
3. **Import:** Upload the file via BigTemplate to generate the structured tasks in the target Box.

**Reference Documentation:**

- [Import from a file (XLSX data format)](https://support.appfire.com/space/BGdc/3525018834/Import+from+a+file#XLSX-data-format)