Bulk Clone Professional for Jira

Hi Jira Community

In this release we have;

fixed an issue where the issuetype field was not working in some scenarios. If you for instance used unusal characters in your issue type name it sometimes did not pick it up during cloning, this has now been fixed

Happy Bulk Cloning

Bulk Clone Team

Hi Jira Community

In this release we have;

1. Added even more extensive logging while bulkcloning “labels”
2. Changed the mechanism for adding labels to the end of the cloning process.

Happy Bulk Cloning

Bulk Clone Team

Hi Jira Community

In this release we have fixed an issue of missing labels on some of the cloned set by indexing the cloned issues in the replicated index store as well.

We essentally trying to reload from the Database as much as possible so the index and the Database stored entity are kept in synch.

Happy Bulk Cloning

Bulk Clone Team

Hi Jira Community

• In this release we have fixed a minor bug in the way Indexing is done for cloned Issues, when we add a label to the issues
• We also added more extensive logging for debugging during the reindexing operation.

Happy Bulk Cloning

Bulk Clone Team

Hi Jira Community

In this release we have fixed a minor UI Velocity whitelist error while mapping “Statuses”

Happy Bulk Cloning

Bulk Clone Team

Hi Jira Community

In this release we have fixed a minor UI Velocity whitelist error while mapping “Statuses”

Happy Bulk Cloning

Bulk Clone Team

Hi Jira Community

In this version we have made the following imporvements

• Added suport for Velocity Allowlist module to adress UI issues in Velocity templates
• Addes support for Bulk Clone to have support for “Dark Theme” mode

Happy Bulk Cloning

Bulk Clone Team

Hi Jira Community

In this version we have made the following imporvements

·        Added suport for Velocity Allowlist module to adress UI issues in Velocity templates

·        Addes support for Bulk Clone to have support for “Dark Theme” mode

Happy Bulk Cloning

Bulk Clone Team

Hi Jira Community

In this version we have made an improvement on “Reporter” & “Assignee” fields.

·        If the permission schemes are different between source project(s) and target project who can “Modify Reporter” and “Assign User” it is enough to have the permission for the target project

Previously both source project(s) and target project had to have the same permission in order to carry out altering of these field values during a Bulk Clone operation. This limitation is now gone.

Happy Bulk Cloning

Bulk Clone Team

Hi Jira community,

In this version we have made an improvement on “Reporter” & “Assignee” field.

·        If the permission schemes are different between source projects and target project who can “Modify Reporter” and “Assign User” it is enough to have the permission for the target project

Previously both source project(s) and target project had to have the same permission in order to carry out altering of these field values during a Bulk Clone operation. This limitation is now gone.

Happy Bulk Cloning

Hi,

In this version we have made an improvment on “Reporter” field.

• When “Set Reporter as Me” option is checked, the Reporter is removed from the fields that require mapping.

Happy Bulk Cloning

Hi,

In this version we have made an improvement on “Reporter” field.

• When “Set Reporter as Me” option is checked, the Reporter is removed from the fields that require mapping.

Happy Bulk Cloning

Hi,

In this version we fixed a Build Environment Error, All downloaded Version 6.0.4 should be replaced with this version instead.

Happy Bulk Cloning

Hi,

In this version we fixed a Build Environment Error, All downloaded Version 6.0.4 should be replaced with this version instead.

Happy Bulk Cloning

Hi,

In this version we have introduced the following improvements:

• If you are Bulk Cloning issues that has archived versions or components set, those values are then ignored, not copied over in the Bulk Cloning process
• This applies for fields: Fix Version, Affects Version & Components

Happy Bulk Cloning

Hi,

In this version we have introduced the following improvements:

• If you are Bulk Cloning issues that has archived versions or components set, those values are then ignored, not copied over in the Bulk Cloning process
• This applies for fields: Fix Version, Affects Version & Components

Happy Bulk Cloning

Hi,

In this version we have introduced the following new Features

• Possibility to alter System & Custom Fields on associated Subtasks to Parent Issues in a Bulk Cloning Operation.
• A neat little option when you BulkClone has been introduced - “Set Reporter as Me”
  • Use Case Scenario: If the Reporter is not changed, the persons who has created the source issues will be notified each time there is a Bulk Cloning operation which may be anoying for them - Simply “Set Reporter as Me” takes care of the problem.

Happy Bulk Cloning

Hi,

In this version we have fixed a bug that resolves the problem of a Parent Link not being properly rebuilt in Jira Roadmaps during heavy CPU usage.

Happy Bulk Cloning

Hi,

In this version we have introduced the following improvements

• Usage of "Multithreading" while BulkCloning will speed up the process significantly especially if you have many custom fields included in your BulkCloning Operation.
• Added support manage different Priority Schemes - We have added an option to map values between different priority schemes if you are BulkCloning between Jira Projects.

Happy Bulk Cloning

Hi,

In this version we have introduced the following improvements

• Usage of "Multithreading" while BulkCloning will speed up the process significantly especially if you have many custom fields included in your BulkCloning Operation.
• Added support manage different Priority Schemes - We have added an option to map values between different priority schemes if you are BulkCloning between Jira Projects.

Happy Bulk Cloning

We have now ported our popular plugin to be compatible with Jira 10

We have now ported our popular plugin to be compatible with Jira 10

Hi,

In this release we have introduced some new improvements.

1. You can now also include/alter the content of the "Description" field in the BulkCloning process if you so desire.

2. Custom fields for choosing to BulkClone are now visible/invisible depending on what the Field configuration schemes in the target project(s) dictate.

3. Subtask types that has been reordered by the user are now also BulkCloned in the right order, before Subtasks where BulkCloned in the physical order they were created

Hi,

In this release we have introduced some new improvements.

1. You can now also include/alter the content of the "Description" field in the BulkCloning process if you so desire.

2. Custom fields for choosing to BulkClone are now visible/invisible depending on what the Field configuration schemes in the target project(s) dictate.

3. Subtask types that has been reordered by the user are now also BulkCloned in the right order, before Subtasks where BulkCloned in the physical order they were created

Hi,

In this release we have added the possibility to Bulk Clone both Parent issue types as well as their contained SubTask issue types in preserved "physical order" without the need to include the Subtasks in the JQL Query. Simply add the ".. ORDER BY IssueKey ASC" at the end of your JQL query and all issue types are preserved in "physical order"

Example 1: Bulk Cloning an Epic (SCRUM-254) and its Stories (SCRUM-1 to 6) with their contained SubTasks

• JQL Query: "project = SCRUM AND key in (SCRUM-254, SCRUM-1, SCRUM-2, SCRUM-3, SCRUM-4, SCRUM-5, SCRUM-6) ORDER BY key ASC"

Alternative JQL Query

• "project = SCRUM AND "Epic Link" in (SCRUM-254, SCRUM-1, SCRUM-2, SCRUM-3, SCRUM-4, SCRUM-5, SCRUM-6) OR IssueKey in (SCRUM-254, SCRUM-1, SCRUM-2, SCRUM-3, SCRUM-4, SCRUM-5, SCRUM-6) ORDER BY key ASC"

Hi,

In this release we have added the possibility to Bulk Clone both Parent issue types as well as their contained SubTask issue types in preserved "physical order" without the need to include the Subtasks in the JQL Query. Simply add the ".. ORDER BY IssueKey ASC" at the end of your JQL query and all issue types are preserved in "physical order"

Example: Bulk Cloning an Epic (SCRUM-254) and its Stories (SCRUM-1 to 6) with their contained SubTasks

• JQL Query: "project = SCRUM AND key in (SCRUM-254, SCRUM-1, SCRUM-2, SCRUM-3, SCRUM-4, SCRUM-5, SCRUM-6) ORDER BY key ASC"

Alternative JQL Query

• "project = SCRUM AND "Epic Link" in (SCRUM-254, SCRUM-1, SCRUM-2, SCRUM-3, SCRUM-4, SCRUM-5, SCRUM-6) OR IssueKey in (SCRUM-254, SCRUM-1, SCRUM-2, SCRUM-3, SCRUM-4, SCRUM-5, SCRUM-6) ORDER BY key ASC"

In this version we have introduced a built in function that hides all related xRay operations, if xRay is not installed on your Jira instance, otherwise it will pop up with all of its additional xRay Bulk Cloning options.

In this version we have introduced a built in function that hides all related xRay operations, if xRay is not installed on your Jira instance, otherwise it will pop up with all of its additional xRay Bulk Cloning options.

In this release we have implemented support for Polish language. Just change your local language in your User profile in Jira and Bulk Clone will change with it. If your language is not supported, it defaults to English.

If you wish to have Bulk Clone in your local language and it is not yet supported?, No problem, If you are willing to support us for a few hours in translating the product dialogues and we will bring the product into your local language, Contact us on: productenquires@lbconsultinggroup.org

With this release, we sincerely acknowledge Dorota Rajska who was in charge of the Polish Translations, without your contribution this release wouldn’t have been possible.

Regards

Bulk Clone Team

In this release we have implemented support for Polish language. Just change your local language in your User profile in Jira and Bulk Clone will change with it. If your language is not supported, it defaults to English.

If you wish to have Bulk Clone in your local language and it is not yet supported?, No problem, If you are willing to support us for a few hours in translating the product dialogues and we will bring the product into your local language, Contact us on: productenquires@lbconsultinggroup.org

With this release, we sincerely acknowledge Dorota Rajska who was in charge of the Polish Translations, without your contribution this release wouldn’t have been possible.

Regards

Bulk Clone Team

In this version we have addressed and fixed a tricky memory leak that could appear in some rare use case scenarios.

• When the user would run another (JQL) Search in parallel in Jira before proceeding with the current Bulk Clone Operation, memory is now preserved and a notification is prompted to the user that respects the initiating JQL Search Request

In this version we have addressed and fixed a tricky memory leak that could appear in some rare use case scenarios.

• When the user would run another (JQL) Search in parallel in Jira before proceeding with the current Bulk Clone Operation, memory is now preserved and a notification is prompted to the user that respects the initiating JQL Search Request

In this version we have added support for XRay Test Step Custom Fields.

The custom columns in your test steps can now be cloned in a different target project as long as:

• The targeted project(s) Test Step Custom Fields include the same field names and types as the source project
• The number of Test Step Custom Fields can be larger in the target project, but it must include the fields from the source project. If there is a mismatch in the Test Step Custom Fields, then the target Test won't have any value in the field

In this version we have added support for XRay Test Step Custom Fields.

The custom columns in your test steps can now be cloned in a different target project as long as:

• The targeted project(s) Test Step Custom Fields include the same field names and types as the source project
• The number of Test Step Custom Fields can be larger in the target project, but it must include the fields from the source project. If there is a mismatch in the Test Step Custom Fields, then the target Test won't have any value in the field