About BigPicture

BigPicture installation and updates

Quick start with BigPicture

BigPicture Sizing Guide

Cloud vs. Server - Key Differences in BigPicture on These Platforms

BigPicture Export

Progress Tracking

Tutorials and tips


Concept of a Program

Setting up BigGantt and BigPicture to support next-gen projects

BigPicture Cloud Backlog

About BigGantt

BigGantt installation and updates

Cloud vs. Server - Key Differences in BigPicture on These Platforms


Knowledge Base

Tutorials and tips

Trust Center

BigPicture 8 is here!

Discover the landmark edition of the Atlassian Marketplace top-selling app! The new version is available to all Cloud, Server and Data Center users. Visit BigPicture 8 Documentation to learn more about it.

Cloning an existing Program

The cloning feature replicates all tasks and relations between them, while following the same synchronization and scope definitions.

Even though Cloning can be a very powerful functionality, it will not replace Program Creation functionality. As it copies Programs only on their highest layer, it is very useful for the purpose of creating Project Portfolio Templates, which we can later re-use for certain types of Programs.



Clone an existing Program

Pick a Program to be cloned.

Basic data

Enter the following information:

    • Program name

    • Program leader - has access to the Program configuration by default.

    • Program duration - determines the Agile schedule and has no impact on the tasks.

    • Privacy settings - when set to private other users, except for the app's admin, will not see the Program in the Program Manager view.

    • Colored logo

Select an existing project where the cloned issues will be created.

Click the "Let's get it started!' button.

Which data can be cloned?

The most common cases and limitation are described in the table below:

DataCloning result (Yes / No)
Jira issueYes. The cloned issues can be linked using a link type selected in Global configuration - Gantt configuration. By default it is a 'Clone' link.
Task structureYes.
Issue types


If the project does have the required issue types in the issue type scheme.

If a new project with different issue types (issue scheme) is used the default issue type will be used for all tasks which can not be matched.

Epics and sub-tasks will be cloned as default issue types.

Summary fieldYes.
Start / End date synchronized fields


The fields selected as Start / End date in Global configuration - Task configuration.

Other fields beside Summary and synchronized date fieldsNo.
Required fields


The required fields can not be populated by the app, hence before cloning the Program make sure all possible fields are set as optional

Version or Component


The app is capable of creating Jira Issues and recreating the structure. It is not capable of creating anything that is not a Jira Issue while cloning, therefore it will automatically replace the original Version or Component with an Artificial Task.