Bug fixed that cloning of child issues didn't work when they are sub-tasks and no Epic child issues.

Minor UI improvements including renaming of "Run" button to "Submit".

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

Bug fixed that cloned issues in epic had leading and trailing spaces if no prefix/suffix has been added.

Bug fixed that cloned issues in epic had leading and trailing spaces if no prefix/suffix has been added.

Bug fixed that cloned issues in epic had leading and trailing spaces if no prefix/suffix has been added.

Bug fixed that cloned issues in epic had leading and trailing spaces if no prefix/suffix has been added.

Compatible with Jira 9

Compatibility with Jira 9

• Bug fixed that sub-tasks of issues in epic have been cloned in the wrong project when cloning to another project
• Bug fixed that sub-tasks weren't visible after cloning for certain configurations

• Bug fixed that sub-tasks of issues in epic have been cloned in the wrong project when cloning to another project
• Bug fixed that sub-tasks weren't visible after cloning for certain configurations

New Feature:

You can now decide whether you want to set the component(s) selected on the first cloning screen on epic and issue in epic. As alternative you can also decide to clone the component field for issues in epic as it is done for other fields.

Bug fix: Sequence of sub-tasks of issue in epic is retained after cloning

Bug fixed that number custom fields couldn't be cloned correctly when language is set to German.

Bug fixed that number custom fields couldn't be cloned correctly when language is set to German.

Bug fixed that setting assignee for all issues did not work correctly for some cases.

Bug fixed that setting assignee for all issues did not work correctly for some cases.

Bug fixed that configuration made on the configuration page was not saved on the first attempt.

Bug fixed that configuration made on the configuration page was not saved on the first attempt.

Bug fixed that unassigned issues in epic weren't displayed correctly on epic clone screens and cloned issues have been assigned instead of remaining unassigned.

Bug fixed that unassigned issues in epic weren't displayed correctly on epic clone screens and cloned issues have been assigned instead of remaining unassigned.

Added compatibility for Elements Connect (formerly nfeed) fields. If the epic or issues in epic contain such fields as required fields, they are correctly taken over to the new issue if they have a value in the source issue.

Added compatibility for Elements Connect (formerly nfeed) fields. If the epic or issues in epic contain such fields as required fields, they are correctly taken over to the new issue if they have a value in the source issue.

Bug fixed that app did not load correctly if epic name field is missing.

UI Improvements:

• Back button removed when cloning is successful
• Clone linked issue information on results screen removed when linked issues aren't cloned

Bug fixed that app did not load correctly if epic name field is missing.

UI Improvements:

• Back button removed when cloning is successful
• Clone linked issue information on results screen removed when linked issues aren't cloned

New Feature

Jira administrators are now able to limit access to epic clone to

• Jira administrators
• Project administrators
• User groups
• Projects

Furthermore, attachment cloning can be disabled completely if necessary. With this feature we allow more security regarding cloning of epics as those restrictions might become necessary in larger instances. For more details related to this new feature, see this page in our documentation.

Bug fix

Bug fixed that multi-line text fields are not taken over to the cloned epic if they are required and have a value in the source issue.

New Feature

Jira administrators are now able to limit access to epic clone to

• Jira administrators
• Project administrators
• User groups
• Projects

Furthermore, attachment cloning can be disabled completely if necessary. With this feature we allow more security regarding cloning of epics as those restrictions might become necessary in larger instances. For more details related to this new feature, see this page in our documentation.

Bug fix

Bug fixed that multi-line text fields are not taken over to the cloned epic if they are required and have a value in the source issue.

Bug fix: Loading times for assignee fields have been very long for large list of assignable users. This has been improved so you can search for possible assignees quickly.

New Feature: Add custom label(s) to your cloned issues. The inserted labels will be added to the existing labels in all cloned issues (Epic, issues in Epic, linked issues). For more information on this feature, please have a look at our documentation

Bug fix: Loading times for assignee fields have been very long for large list of assignable users. This has been improved so you can search for possible assignees quickly.

New Feature: Add custom label(s) to your cloned issues. The inserted labels will be added to the existing labels in all cloned issues (Epic, issues in Epic, linked issues). For more information on this feature, please have a look at our documentation

Bug fixed that default assignees where not set correctly.

Bug fixed that default assignees were not set correctly.

Minor bug fixes of logo display and license validation.

Minor bug fix of logo display and license validation.

• Bug fixed that cloning of labels did not work correctly
• Improvement: Links of issues in epic can be cloned also if epic itself doesn't have links

• Bug fixed that cloning of labels did not work correctly
• Improvement: Links of issues in epic can be cloned also if epic itself doesn't have links

Bug fixed that list of selectable users gets cropped for large number of assignable users in a project.

Bug fixed that list of selectable users gets cropped for large number of assignable users in a project.

Bug fixed in custom field validation which caused cloning to fail

Bug fixed in custom field validation which caused cloning to fail

Bug fixed that cloning did not work for issues with required custom fields even if the source issue has a value for those fields.

Improved Custom Field validation to display to users which custom fields are required and why cloning might not work.

Bug fixed that cloning did not work for issues with required custom fields even if the source issue has a value for those fields.

Improved Custom Field validation to display to users which custom fields are required and why cloning might not work.

The release introduces the following new features:

• Set Epic Assignee: It is now possible to set also the new Epic Assignee during cloning. Furthermore, you can decide if the selected user should be assigned to all newly created issues in bulk
• Set Security Level: Beside other system fields, it is possible to define the Security Level to be set on cloning in target project. With this feature you are able to clone Epics without security level to a project where the security level is required
• Set Story Points for Stories: For issues in Epic of type Story the Story Points can be defined for the issues to be cloned (Story points are only displayed for Stories and if the Story Point custom field hasn't been renamed in your Jira instance)

Beside those features, minor UI improvements have been implemented.

The release introduces the following new features:

• Set Epic Assignee: It is now possible to set also the new Epic Assignee during cloning. Furthermore, you can decide if the selected user should be assigned to all newly created issues in bulk
• Set Security Level: Beside other system fields, it is possible to define the Security Level to be set on cloning in target project. With this feature you are able to clone Epics without security level to a project where the security level is required
• Set Story Points for Stories: For issues in Epic of type Story the Story Points can be defined for the issues to be cloned (Story points are only displayed for Stories and if the Story Point custom field hasn't been renamed in your Jira instance)

Beside those features, minor UI improvements have been implemented.

Fixed a bug that attachments of issues in Epic couldn't be cloned if the Epic itself doesn't have attachments.

Fixed a bug that attachments of issues in Epic couldn't be cloned if the Epic itself doesn't have attachments.

Bug fixed that cloning of Epic custom fields didn't work correctly on some instances.

Bug fixed that cloning of Epic custom fields didn't work correctly on some instances.

New Features:

• Clone Component(s) of Epic and set them for cloned Epic and all issues in Epic
• Option to copy Links: Beside cloning of linked issues to Epic, you can now decide if you want to copy only the links existing in the source Epic (cloned Epic will be linked to same issues than the source Epic); works for inward and outward links

Improvements:

• Validation of required Epic system fields: If fields like component(s), due date or fix version(s) are required in the target project you need to provide values for those fields to proceed. Otherwise you can't continue with the cloning process
• Validation of required fields for Issues in Epic: As for the Epic, also for the system fields in issues in Epic a validation has been added.

By this improved validation you can immediately see if cloning will work or what might be missing for a successful cloning operation.

New Features:

• Clone Component(s) of Epic and set them for cloned Epic and all issues in Epic
• Option to copy Links: Beside cloning of linked issues to Epic, you can now decide if you want to copy only the links existing in the source Epic (cloned Epic will be linked to same issues than the source Epic); works for inward and outward links

Improvements:

• Validation of required Epic system fields: If fields like component(s), due date or fix version(s) are required in the target project you need to provide values for those fields to proceed . Otherwise you can't continue with the cloning process
• Validation of required fields for Issues in Epic: As for the Epic, also for the system fields in issues in Epic a validation has been added.

By this improved validation you can immediately see if cloning will work or what might be missing for a successful cloning operation.

Added compatibility to Jira version 8.13

Added compatibility to Jira Version 8.13

Bug fixed that cloning fails for certain date format settings in some instances if due date is set on cloning.

Bug fixed that cloning fails for certain date format settings in some instances if due date is set on cloning.

Bugs fixed in this release:

• Cloned Issues in Epic are displayed in source- and cloned epic on some Data Center instances
• 'Unassigned' wasn't available as selection for Assignee field

Bugs fixed in this release:

• Cloned Issues in Epic are displayed in source- and cloned epic on some Data Center instances
• 'Unassigned' wasn't available as selection for Assignee field

Bugs fixed in this release:

• License validation error on Jira 7
• Cloning doesn't fail if Jira system fields (components, labels, affects versions) are required in target project
• Bug solved that cloning fails due to epic name field in Jira Data Center

Improvements:

• Improved error handling and messages if cloning fails for some reason (e.g. required fields)
• Components, Labels and Affects versions are now cloned as well if they are required

Bugs fixed in this release:

• License validation error on Jira 7
• Cloning doesn't fail if Jira system fields (components, labels, affects versions) are required in target project
• Bug solved that cloning fails due to epic name field in Jira Data Center

Improvements:

• Improved error handling and messages if cloning fails for some reason (e.g. required fields)
• Components, Labels and Affects versions are now cloned as well if they are required

Implementation of minor UI Improvements and bug fixed that time spent was cloned for Sub-tasks of Epic.

App was renamed from Epic Clone Pro to Epic Clone.

Implementation of minor UI Improvements and bug fixed that time spent was cloned for Sub-tasks of Epic.

App was renamed from Epic Clone Pro to Epic Clone.

Bug fixed that cloning might fail for certain language settings of Jira user.

Bug fixed that cloning might fail for certain language settings of Jira user.

Bug fixed that cloning might fail for different target project where assignees of issues in epic don't have assignable user permission.

Bug fixed that cloning might fail for different target project where assignees of issues in epic don't have assignable user permission.

New Feature:

Clone...

• Epic
  • Epic Sub-Tasks
  • Issues in Epic
    • Sub-Tasks of Issues in Epic

With this release we introduce that you are now able to clone also sub-tasks of issues in epic. Now you are able to clone an entire issue hierarchy from epic (and its sub-tasks) via issue in epic to sub-tasks of issues in epic with Epic Clone Pro. As for issues in epic you can decide individually for each sub-task if you want to clone it or not.

UI Improvements:

The result screen of the cloning operation has been improved to get a better and more structured overview of your cloned issues

New Feature:

Clone...

• Epic
  • Epic Sub-Tasks
  • Issues in Epic
    • Sub-Tasks of Issues in Epic

With this release we introduce that you are now able to clone also sub-tasks of issues in epic. Now you are able to clone an entire issue hierarchy from epic (and its sub-tasks) via issue in epic to sub-tasks of issues in epic with Epic Clone Pro. As for issues in epic you can decide individually for each sub-task if you want to clone it or not.

UI Improvements:

The result screen of the cloning operation has been improved to get a better and more structured overview of your cloned issues

• Bug fixed that cloning might fail for some users if they don't have access to certain issues in epic or linked issues to epic. Those issues are now no longer considered for cloning
• Change of Header of Epic Sub-tasks and linked issues to Epic to clarify that those are sub-tasks and linked issues of Epic and not of issues in Epic

• Bug fixed that cloning might fail for some users if they don't have access to certain issues in epic or linked issues to epic. Those issues are now no longer considered for cloning
• Change of Header of Epic Sub-tasks and linked issues to Epic to clarify that those are sub-tasks and linked issues of Epic and not of issues in Epic

Initial Release for Jira Datacenter

Bug was fixed that cloning of Epic failed for some configuration with "Server side Error"

Bug fixed that epic cloned failed for some configurations with "Server Side Error"