Epic Clone: Bulk Clone Project Issues for Jira

Find more details about changes in the app as well as a product roadmap on our changelog and roadmap page.

This update makes cloning work better for teams with custom setups. You can now choose to clone child issues one at a time, and child issues link correctly to cloned epics—even if you renamed the epic link field.

Ranking Option for Child Issues

You can now activate a new checkbox labeled Clone child issues in sequence when cloning issues. With this option enabled, child issues will be cloned one after another instead of in parallel. The sequence of child issues is retained. However, with this option enabled the cloning process might take longer.

Correct Child Issue Linking for Renamed Epic Link Field

When cloning an epic with a custom "Feature Link" field replacing the standard epic link, child issues now only link to the newly cloned epic. Child issues are no longer linked to both the source and target epic after cloning when using a renamed epic link field.

Find more details about changes in the app as well as a product roadmap on this new changelog and roadmap page.

Recreate Cross-Epic Links When Cloning Child Issues:

A new option in the Epic Clone configuration allows you to recreate cross-Epic links between child issues when cloning. If the original child issues were linked to child issues under different Epics, these links will automatically be established between all corresponding cloned issues—even if their respective Epics are cloned at different times. This ensures all previous clones of a story are linked accordingly whenever the associated cross-Epic story is cloned later.

Validation of empty 3rd party fields bug fix:

We fixed a bug that caused the cloning operation to fail when certain 3rd party custom fields were existent and empty in the issues.

Find more details about changes in the app as well as a product roadmap on this new changelog and roadmap page.

New feature: Set distinct child issues labels

You can now set labels for child issues exclusively which are independent of the labels set for the epic. Easily add custom labels additionally to your cloned child issues only.

New Feature: Preserve Internal Links Between Child Issues

You can now choose whether to replicate internal links among child issues during cloning. Internal links are connections between issues that belong to the same Epic. When this option is enabled, links between related child issues will be automatically maintained between their corresponding clones.

Find more details about changes in the app as well as a product roadmap on this new changelog and roadmap page.

Bug fixes in Find and Replace Functionality

We identified some minor issues with the new find and replace functionality for child issue summaries introduced with the last release. We fixed them in this new version

Cloning of child issues when Epic Link is required via a workflow validator

In cases where the Epic Link field is required via a validator on the issue create transition, cloning now works as well. In older versions an error occurred in such cases that prevents the epics child issues from being cloned correctly.

Find more details about changes in the app as well as a product roadmap on this new changelog and roadmap page.

Find and Replace Functionality in Child Issue Summaries

With the addition of the Find and Replace feature in child issues summaries and descriptions, you can now seamlessly update text strings across multiple issues when cloning epics. This feature enhances your ability to manage consistent naming conventions or adapt internal codes quickly.

Assignee Search in Jira 9

In Jira 9, a bug affecting the assignee change feature has been identified, limiting your ability to select users. This bug has been fixed in the latest release.

Compatibility with Jira 10.6.0

The app is now compatible with the latest Jira version 10.6.0

Find more details about changes in the app as well as a product roadmap on this new changelog and roadmap page.

During the cloning process, due dates for epics and their child issues are now correctly displayed and automatically copied over to the new cloned issues if you select the new ‘copy due date checkbox’ on the first cloning screen. You will see the existing due date value on the cloning screen, ensuring all timelines are consistently maintained across original and cloned tasks.

Find more details about changes in the app as well as a product roadmap on this new changelog and roadmap page.

During the cloning process, due dates for epics and their child issues are now correctly displayed and automatically copied over to the new cloned issues if you select the new ‘copy due date checkbox’ on the first cloning screen. You will see the existing due date value on the cloning screen, ensuring all timelines are consistently maintained across original and cloned tasks.

Find more details about changes in the app as well as a product roadmap on this new changelog and roadmap page.

• Server side error resolution for cloning child issues: We have addressed and resolved a server-side error that occurred when there is another story points field beside the default one in the Jira instance. Cloning of child issues failed in such cases when the story point field isn’t a number custom field. With the new version, cloning also works in such cases.
• App name and description displayed correctly: We've fixed how app name and descriptions appear on the manage apps page in Data Center deployments. This update ensures that the display of app information is accurate and consistent, improving the overall clarity and usability of app management within your environment.

Epic Clone is now compatible with Jira 10.

Find more details about changes in the app as well as a product roadmap on this new changelog and roadmap page.

Resolved an issue where cloning was unsuccessful if inactive users were selected in user custom fields. The system will now intelligently skip inactive users during the cloning process, ensuring that cloning operations complete smoothly even when certain fields contain inactive users.

Find more details about changes in the app as well as a product roadmap on this new changelog and roadmap page.

We fixed a bug that causes issues during cloning as the story points field wasn't identified correctly in some instances.

• Bug fixed that epic colour wasn't cloned for epics
• Custom issue type icons are now displayed correctly on result screen

• Bug fixed that epic colour wasn't cloned for epics
• Custom issue type icons are now displayed correctly on result screen

• Bug fixed that custom issue type icons weren't displayed on the cloning screens
• Improved error message in case the Parent Link field is required but doesn't have a value for the cloned epic

• Bug fixed that custom issue type icons weren't displayed on the cloning screens
• Improved error message in case the Parent Link field is required but doesn't have a value for the cloned epic

Bug fixed that cloning failed when parent link field is required even though the field has a value for the epic.

• Fixes a bug that sub-task assignees have been cloned although assignees of all child issues should be set to unassigned
• The project select list in admin settings now also contains projects, where an admin doesn't have create issue permission

• Beside setting of new fix version(s) for cloned Epic and issues, you can now also copy existing fix version(s) in Epic and issues in Epic
• Keep issues in Epic in their source project: This new feature allows you to clone child issues in the same project instead of taking them over to a different one when cloning across projects

• Beside setting of new fix version(s) for cloned Epic and issues, you can now also copy existing fix version(s) in Epic and issues in Epic
• Keep issues in Epic in their source project: This new feature allows you to clone child issues in the same project instead of taking them over to a different one when cloning across projects

Bug fixed that cloning failed for linked Epics

Bug fixed that cloning failed for linked Epics

Bug fixed that component field was falsely displayed as required although it isn't required for the Epic

Bug fixed that component field was falsely displayed as required although it isn't required for the Epic

Bug fixed that component field was falsely displayed as required although it isn't required for the Epic

Bug fixed that component field was falsely displayed as required although it isn't required for the Epic