Data Center to Cloud migration

With the Advanced Template Cloner, migration is seamless. Since our app doesn’t retain specific internal data, there’s no need to migrate any app data when migrating from a Data Center to Jira Cloud. As with the Data Center version, simply install the app in the...

End User License Agreement

Please read this End-User License Agreement („Agreement”) carefully before downloading or using Template (Epic) cloner for JIRA (“Application”). By downloading or using the Application, you are agreeing to be bound by the terms and conditions of this...

Privacy Policy

The following Privacy Policy sets out how Vilisoft Sp. z o.o. treats your personal data. Vilisoft Sp. z o.o. collects information when you buy an application from the Marketplace or when you generate a trial license.Then, Atlassian provides Vilisoft Sp. z o.o. with...

Cloning process

Step 1 – Cloning option In the More menu in any Issue, you can find option Clone issue template. R Clone template option is available for any issue. If you click on Clone template option, system displays form where issues details can be edited before cloning...

Template structure

The template is composed of: Main Issue Any issues linked to the main issue Any sub-tasks in the main issue or issues linked to it An example of a template looks like on the picture below:  To create issues linked to Main Issue you can use any issues type you have...

Initial setup

New custom field During the installation process, a new custom field is added to your JIRA instance.  After the installation process, the new position Template issue is available on the Custom fields list like in the picture below. This custom field can be added to...