Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

Release notes

• Security updates - we upgraded some of the 3rd party libraries used by the app.
• Minor improvements.

Release notes

• Security updates - we upgraded some of the 3rd party libraries used by the app.
• Minor improvements.

Release notes

The Short Term license option is not supported from this version onwards. If you have a current short term license active do not upgrade to this version.

The Short Term license option is not supported from this version onwards. If you have a current short term license active do not upgrade to this version.

• A user would get a 500 error if XML had any syntax problem or unrecognised tag. Now a proper display with this feedback will be relayed to him.
• When "config.xml" was not present in the complete import zip, a 500 error would appear. Now a proper display with this feedback will be relayed to the user.

• A user would get a 500 error if XML had any syntax problem or unrecognised tag. Now a proper display with this feedback will be relayed to him.
• When "config.xml" was not present in the complete import zip, a 500 error would appear. Now a proper display with this feedback will be relayed to the user.

• Fixed a bug where PC considered spaces in some args of the SR4J “send custom email” workflow post function to be always list separators, which is not the case.
• PC now supports references in ScriptRunner's Field required workflow validators and conditions.
• PC now supports references in ScriptRunner's "Linked issues" condition.

• Fixed a bug where PC considered spaces in some args of the SR4J “send custom email” workflow post function to be always list separators, which is not the case.
• PC now supports references in ScriptRunner's Field required workflow validators and conditions.
• PC now supports references in ScriptRunner's "Linked issues" condition.

• Compatibility with Jira 8.18.X
• Support for new Script Runner workflow functions: clear field post function, user in field validator and user condition.

• Compatibility with Jira 8.18.X
• Support for new Script Runner workflow functions: clear field post function, user in field validator and user condition.

When doing a complete import, if the complete import zip contained more xml files other than the configuration one, it could lead to errors selecting the right one.

When doing a complete import, if the complete import zip contained more "xml" files other than the configuration one, it could lead to errors selecting the right one.

• Introduced a new feature that will display the specific changes an existing workflow will experience on the import tree.
• Added a missing translator for the "Jira Workflow Toolbox" plugin which prevented the “Field required” condition and “Field required or changed” validator from being exported.
• Added a missing translator for Sprint Health Gadget needed to correctly export the associated agile board.
• Fixed a bug where the user would get a 500 error if the import XML has any syntax problem or unrecognised tag.
• Fixed a bug where for workflows created automatically for Software projects, Jira introduced a number of spaces and line breaks that broke the post-function display. This also led to PC being unable to properly import those post-functions.
• Fixed a bug that produced an error while reading workflows when certain external plugins were not present.

• Introduced a new feature that will display the specific changes an existing workflow will experience on the import tree.
• Added a missing translator for the "Jira Workflow Toolbox" plugin which prevented the “Field required” condition and “Field required or changed” validator from being exported.
• Added a missing translator for Sprint Health Gadget needed to correctly export the associated agile board.
• Fixed a bug where the user would get a 500 error if the import XML has any syntax problem or unrecognised tag.
• Fixed a bug where for workflows created automatically for Software projects, Jira introduced a number of spaces and line breaks that broke the post-function display. This also led to PC being unable to properly import those post-functions.
• Fixed a bug that produced an error while reading workflows when certain external plugins were not present.

• Added support for references to Script Runner for Jira’s workflow functions: Conditions (project role, user, group, regular expression) and Validators (regular expression).
• Fixed an issue with kanban/scrum board imports: default sub-filters were being created on import, even when the value was empty in the source XML file.
• Improved error-handling: during an import, existing screens that contain a field entry associated with a field that no longer exists (e.g. a custom field depending on an app that has been uninstalled), will make Project Configurator throw an error with a NullPointerException. Project Configurator now proactively tries to check if the field is null, and if so, ignores it and avoids the error.

• Added support for references to Script Runner for Jira’s workflow functions: Conditions (project role, user, group, regular expression) and Validators (regular expression).
• Fixed an issue with kanban/scrum board imports: default sub-filters were being created on import, even when the value was empty in the source XML file.
• Improved error-handling: during an import, existing screens that contain a field entry associated with a field that no longer exists (e.g. a custom field depending on an app that has been uninstalled), will make Project Configurator throw an error with a NullPointerException. Project Configurator now proactively tries to check if the field is null, and if so, ignores it and avoids the error.

What's New

• Updates made to the Integration Toolkit that include improvements to simplify reference handling and the creation of properties

Fixes & Improvements

• Fixed a bug that caused a 'ClassCastException' error on export for some users

What's New

• Updates made to the Integration Toolkit that include improvements to simplify reference handling and the creation of properties

Fixes & Improvements

• Fixed a bug that caused a 'ClassCastException' error on export for some users

• Fixed a bug that prevented the Import Simulation report from loading for some users in version 3.7.3
• Fixed a bug that was displaying incorrect differences in <p> </p> tags in Field configurations; this resulting in false representation that modifications would be applied to the target instance
• Fixed a bug that displayed incorrect information about non-existent changes to workflow layouts
• Updated in-app links for new documentation site`

• Fixed a bug that prevented the Import Simulation report from loading for some users in version 3.7.3
• Fixed a bug that was displaying incorrect differences in

  tags in Field configurations; this resulting in false representation that modifications would be applied to the target instance

• Fixed a bug that displayed incorrect information about non-existent changes to workflow layouts
• Updated in-app links for new documentation site

• Fixed a bug introduced in version 3.7.1 which prevented users from applying changes after a successful complete project import simulation.
• Fixed a bug where it was not possible to save settings which had a high number of elements for the "skip configurations" import option or the "Projects to export" export option.

• Fixed a bug introduced in version 3.7.1 which prevented users from applying changes after a successful complete project import simulation.
• Fixed a bug where it was not possible to save settings which had a high number of elements for the "skip configurations" import option or the "Projects to export" export option.

Bug fixes

• Fixed a bug where older versions of Jira were displaying empty import trees and errors while importing.
• Fixed a bug involving translated custom fields. On import, Project Configurator was considering the translated values for custom fields instead of the original custom field name, resulting in duplications of custom fields in the target instance.

Bug fixes

• Fixed a bug where older versions of Jira were displaying empty import trees and errors while importing.
• Fixed a bug involving translated custom fields. On import, Project Configurator was considering the translated values for custom fields instead of the original custom field name, resulting in duplications of custom fields in the target instance.

• Fixed several bugs that prevented a limited number of customers from performing certain actions such as importing.

• Fixed several bugs that prevented a limited number of customers from performing certain actions such as importing.

Fixed security vulnerabilities in accordance with our Bug Bounty program. These vulnerabilities affect all versions of Project Configurator released prior to this one, so we strongly advise that you upgrade to this or later versions.

Fixed security vulnerabilities in accordance with our Bug Bounty program.

These vulnerabilities affect all versions of Project Configurator released prior to this one, so we strongly advise that you upgrade to this or later versions.

• Project Configurator is now compatible with Jira 8.14
• Small UI fixes to Getting Started page and Export and Import screens

• Project Configurator is now compatible with Jira 8.14
• Small UI fixes to Getting Started page and Export and Import screens

Fixes two bugs that impacted how the default issue type scheme is handled during imports.

Fixes two bugs that impacted how the default issue type scheme is handled during imports.

More ScriptRunner features supported, now including Script Fields. Also fixed: JSD report bug, some synchronous methods in the Java API and improved integration framework to allow export of extension objects regardless of their relation to exported projects.

More ScriptRunner features supported, now including Script Fields. Also fixed: JSD report bug, some synchronous methods in the Java API and improved integration framework to allow export of extension objects regardless of their relation to exported projects.

Newest improvements

• New licensing option for short term migrations.
• Export file default naming was lost after changes in the UI and is now recovered.
• Support references to Application links for ScriptRunner integration.

Newest improvements

• New licensing option for short term migrations.
• Export file default naming was lost after changes in the UI and is now recovered.
• Support references to Application links for ScriptRunner integration.

Fixes & Improvements

• Fixed an issue where an error was prompting the user to install a missing plugin when the true error was a missing custom field
• Enhanced the colours that represent modified objects and warnings in the import simulation tree

Fixes & Improvements

• Fixed an issue where an error was prompting the user to install a missing plugin when the true error was a missing custom field
• Enhanced the colours that represent modified objects and warnings in the import simulation tree

Technical Improvement

• Improved the design of the "Getting Started" page

Bug

• Fixed an issue where not all properties were being considered as a source of pre-conditions when creating an object
• Fixed an issue where export may fail with the error "java.lang.IllegalArgumentException: object is not an instance of declaring class"

Technical Improvement

• Improved the design of the "Getting Started" page

Bug

• Fixed an issue where not all properties were being considered as a source of pre-conditions when creating an object
• Fixed an issue where export may fail with the error "java.lang.IllegalArgumentException: object is not an instance of declaring class"

Change

• [PCDEV-1702] - Compatibility with Jira 8.11.0

Bug fixes

• [PCDEV-1703] - Sometimes exporting a complete project fails while copying the zip file from the temp directory to its final destination
• [PCDEV-1690] - Occasionally part of specific pages, even from other plugins, become hidden if PC is installed

Change

• [PCDEV-1702] - Compatibility with Jira 8.11.0

Bug fixes

• [PCDEV-1703] - Sometimes exporting a complete project fails while copying the zip file from the temp directory to its final destination
• [PCDEV-1690] - Occasionally part of specific pages, even from other plugins, become hidden if PC is installed

New Features

• History log for exports & imports is now available in the menu. Select it to check the import and exports that have been executed and easily access their result files.

Bug

• Some customers could not use import functionality due to a very rare bug in the form properties.
• The error msg “ERROR: This data appears to be from an older version of JIRA ...” was being added to the complete export result even though it was successful.

Other improvements

• Internal optimisations.
• Added PC Compatibility with Jira 8.10 JSD 4.10.
• Integration Framework updates.

New Features

• History log for exports & imports is now available in the menu. Select it to check the import and exports that have been executed and easily access their result files.

Bug

• Some customers could not use import functionality due to a very rare bug in the form properties.
• The error msg “ERROR: This data appears to be from an older version of JIRA ...” was being added to the complete export result even though it was successful.

Other improvements

• Internal optimisations.
• Added PC Compatibility with Jira 8.10 JSD 4.10.
• Integration Framework updates.

Added compatibility with Jira 8.9.0

Added compatibility with Jira 8.9.0

* Texts were improved so user experience is slightly clearer in this page.

* Minor fixes and internal updates.

* Texts were improved so user experience is slightly clearer in this page.

* Minor fixes and internal updates.

Feature

• Saving import options is now possible.

Change

• Will now issue a meaningful message when the project context of a custom field configuration scheme is about to change.
• Improved messaging for custom field related fields so it’s easier to understand possible errors while importing.

Bug Fix

• JMWE - Current Status Condition was not being properly exported/imported.
• The import and export project screen was not working for some users and that should be fixed now.

Feature

• Saving import options is now possible.

Change

• Will now issue a meaningful message when the project context of a custom field configuration scheme is about to change.
• Improved messaging for custom field related fields so it’s easier to understand possible errors while importing.

Bug Fix

• JMWE - Current Status Condition was not being properly exported/imported.
• The import and export project screen was not working for some users and that should be fixed now.

• Some permissions in a scheme were incorrectly removed in certain cases.
• Unexpected warnings were received during export with projects using JSD items.
• Some messages were confusing and have been modified for better comprehension.

• Some permissions in a scheme were incorrectly removed in certain cases.
• Unexpected warnings were received during export with projects using JSD items.
• Some messages were confusing and have been modified for better comprehension.

• Fixed Project Configurator giving a string out of range error when a different file path is specified.
• Fixed problem with Script Runner compatibility in post function : Assign to first member of role
• Fixed JSU compatibility problem with the postfunction : Copy Value From Other Field (JSU)
• Fixed problem with the text-box to choose projects which are being exported not showing on the screen

• Fixed Project Configurator giving a string out of range error when a different file path is specified.
• Fixed problem with Script Runner compatibility in post function : Assign to first member of role
• Fixed JSU compatibility problem with the postfunction : Copy Value From Other Field (JSU)
• Fixed problem with the text-box to choose projects which are being exported not showing on the screen

• Zip file button doesn't work properly
• JWT problem compatibility with the postfunction "Update Issue field"
• Error msg improvement: " Cannot read property ‘slice’ of undefined" changed.

Improvements:

• Update in-app doc links

Bug fixes:

• Zip file button doesn't work properly
• JWT problem compatibility with the postfunction "Update Issue field"
• Error msg improvement: " Cannot read property ‘slice’ of undefined" changed.

Improvements:

• Update in-app doc links

Saving standard settings in export screen

Fix compatibility issue with OpenJDK 11

Saving standard settings in export screen

Fix compatibility issue with OpenJDK 11

Bug fix:

When importing a service desk project into an instance with Jira Service Desk 4.6.0 or higher, some operations on SD queues will fail, including creation of new queues.

Bug fix:

When importing a service desk project into an instance with Jira Service Desk 4.6.0 or higher, some operations on SD queues will fail, including creation of new queues.

We keep improving the error messages for better clarity in your exports and imports. This release contains mostly improvements to configuration import messages.

Bug fixes:

• [PCDEV-1511] - Export fail with ""JWT - Update issue fields"
• [PCDEV-1517] - One error is shown when a multiuser picker with filters is importing
• [PCDEV-1524] - Export failure with Jira Misc Workflow Extensions with parameter pointing to "any" link type

We keep improving the error messages for better clarity in your exports and imports. This release contains mostly improvements to configuration import messages.

Bug fixes:

• [PCDEV-1511] - Export fail with ""JWT - Update issue fields"
• [PCDEV-1517] - One error is shown when a multiuser picker with filters is importing
• [PCDEV-1524] - Export failure with Jira Misc Workflow Extensions with parameter pointing to "any" link type

First set of improved error messaging

First set of improved error messaging

Bug fixes:

• [PCDEV-1310] - JWT - Update issue fields function keeps source field value pointing to the ID of the field in the source instance and not the ID of the migrated field in the target instance
• [PCDEV-1333] - Importing error : Custom field must exist"
• [PCDEV-1506] - PC and JWT integration fail in postfunction with date parameters

Bug fixes:

• [PCDEV-1310] - JWT - Update issue fields function keeps source field value pointing to the ID of the field in the source instance and not the ID of the migrated field in the target instance
• [PCDEV-1333] - Importing error : Custom field must exist"
• [PCDEV-1506] - PC and JWT integration fail in postfunction with date parameters

Fixed bugs related to third party plugins imports.

Fixed bugs related to third party plugins imports.

Minnor improvements for app tracking

Minnor improvements for app tracking

Features

• New notification when performing an import with an evaluation license of Project Configurator

Compatibility

• Jira 8.4.0
• JSD 4.4.0

Bug fixes

• Error fixed related to new entities that assigned to existing
• This version of Project Configurator addresses a medium severity security vulnerability that was recently identified in Project Configurator. The vulnerability affects all versions of Project Configurator prior to 3.0.9. The vulnerability means that a user with Jira System Administrator permissions read files and network resources (such as http) accessible to the Jira server via an XML external entity (XXE) flaw. If you have any questions, please feel free to raise a support request at https://productsupport.adaptavist.com/servicedesk/customer/portal/37/create/225 referencing PCDEV-1331.

Features

• New notification when performing an import with an evaluation license of Project Configurator

Compatibility

• Jira 8.4.0
• JSD 4.4.0

Bug fixes

• Error fixed related to new entities that assigned to existing
• This version of Project Configurator addresses a medium severity security vulnerability that was recently identified in Project Configurator. The vulnerability affects all versions of Project Configurator prior to 3.0.9. The vulnerability means that a user with Jira System Administrator permissions read files and network resources (such as http) accessible to the Jira server via an XML external entity (XXE) flaw. If you have any questions, please feel free to raise a support request at https://productsupport.adaptavist.com/servicedesk/customer/portal/37/create/225 referencing PCDEV-1331.

UI changes:

• [PCDEV-1292] - Change the name of Used By Report
• [PCDEV-1293] - Change the description in Used By Report
• [PCDEV-1298] - Getting Started page links won't open in new tab
• [PCDEV-1299] - Change the order of the Project Configurator menu

Bug fixes:

• [PCDEV-1286] - Workflow Configuration for the Assign to Project Role Post function provided by the Jira Workflow Toolbox plugin is not migrated correctly
• [PCDEV-1325] - Project Configurator gives a string out of range error on Windows OS

UI changes:

• [PCDEV-1292] - Change the name of Used By Report
• [PCDEV-1293] - Change the description in Used By Report
• [PCDEV-1298] - Getting Started page links won't open in new tab
• [PCDEV-1299] - Change the order of the Project Configurator menu

Bug fixes:

• [PCDEV-1286] - Workflow Configuration for the Assign to Project Role Post function provided by the Jira Workflow Toolbox plugin is not migrated correctly
• [PCDEV-1325] - Project Configurator gives a string out of range error on Windows OS

Bug fixes

• [PCDEV-1200] - Jira Suite Utilities no longer compatible with Project Configurator
• [PCDEV-1248] - Wrong First Time link
• [PCDEV-1253] - Error in ImportJobRunner Error Handling
• [PCDEV-1257] - Recalculate button causes the Import Operations Tree to disappear

Improvements

• [PCDEV-1252] - Disable PC analytics when user disables Jira analytics

Bug fixes

• [PCDEV-1200] - Jira Suite Utilities no longer compatible with Project Configurator
• [PCDEV-1248] - Wrong First Time link
• [PCDEV-1253] - Error in ImportJobRunner Error Handling
• [PCDEV-1257] - Recalculate button causes the Import Operations Tree to disappear

Improvements

• [PCDEV-1252] - Disable PC analytics when user disables Jira analytics

Improvements:

• [PCDEV-1172] - Adapt to Jira 8.2

Bug fixes:

• [PCDEV-1164] - Notification and issue security schemes cause import errors with PC 3.0
• [PCDEV-1171] - Problem migrating some types of dashboard gadgets that apply to project categories
• [PCDEV-1176] - When some JQL references an object by a string that is not acceptable as a valid object key (as a filter name), the import breaks
• [PCDEV-1179] - References to subordinate objects (versions, components, issue security levels) in a JQL query trigger a NPE in the simulated import
• [PCDEV-1181] - MissingMethodException when trying to change the help text of a JSD request type

• [PCDEV-1064] - The global order of resolutions and priorities may not be imported correctly

Improvements:

• [PCDEV-1172] - Adapt to Jira 8.2

Bug fixes:

• [PCDEV-1164] - Notification and issue security schemes cause import errors with PC 3.0
• [PCDEV-1171] - Problem migrating some types of dashboard gadgets that apply to project categories
• [PCDEV-1176] - When some JQL references an object by a string that is not acceptable as a valid object key (as a filter name), the import breaks
• [PCDEV-1179] - References to subordinate objects (versions, components, issue security levels) in a JQL query trigger a NPE in the simulated import
• [PCDEV-1181] - MissingMethodException when trying to change the help text of a JSD request type

• [PCDEV-1064] - The global order of resolutions and priorities may not be imported correctly

New features:

• [PCDEV-1116] - ‘Getting Started’ page with the essential information to quickly and easily start using Project Configurator.

Improvements:

• [PCDEV-1023] - Allow data migration with custom field plugins in different versions
• [PCDEV-1150] - Ignore changes to required/optional status of assignee field in field configurations

Bug fixes:

• [PCDEV-1159] - Complete project import: setting of version order within projects always failed
• [PCDEV-1163] - Error when importing a filter that references a project by its name
• [PCDEV-1151] - Warning when new issue type / priority scheme does not cover all existing issues in a project
• [PCDEV-1153] - NullPointerException when trying to import a filter without columns
• [PCDEV-1155] - Sometimes working hours and holidays of JSD calendars not imported correctly
• [PCDEV-1156] - Some JSD request types not updated correctly
• [PCDEV-1165] - Some SLA conditions not imported correctly
• [PCDEV-1169] - Filter attributes not always updated correctly

New features:

• [PCDEV-1116] - ‘Getting Started’ page with the essential information to quickly and easily start using Project Configurator.

Improvements:

• [PCDEV-1023] - Allow data migration with custom field plugins in different versions
• [PCDEV-1150] - Ignore changes to required/optional status of assignee field in field configurations

Bug fixes:

• [PCDEV-1159] - Complete project import: setting of version order within projects always failed
• [PCDEV-1163] - Error when importing a filter that references a project by its name
• [PCDEV-1151] - Warning when new issue type / priority scheme does not cover all existing issues in a project
• [PCDEV-1153] - NullPointerException when trying to import a filter without columns
• [PCDEV-1155] - Sometimes working hours and holidays of JSD calendars not imported correctly
• [PCDEV-1156] - Some JSD request types not updated correctly
• [PCDEV-1165] - Some SLA conditions not imported correctly
• [PCDEV-1169] - Filter attributes not always updated correctly

We are delighted to announce a major release for Project Configurator for Jira (PC4J 3.0). This release brings major functionality and user experience improvements to help make project migrations and configuration changes easier than ever:

- More comprehensive error detection during import simulations.

- Flexibility to select/deselect objects from the import simulation UI, rather than wasting time editing the XML file or redoing the export phase.

- Individual errors will no longer interrupt an import. When the error makes a required object unavailable, the dependent operations will be automatically skipped.

- New user interface for imports: tree-like structure and colour coding now makes all import reports much easier to analyse.

- Easily identify the creation of new objects and changes to existing ones, and enable/disable them separately.

We are delighted to announce a major release for Project Configurator for Jira (PC4J 3.0). This release brings major functionality and user experience improvements to help make project migrations and configuration changes easier than ever:

- More comprehensive error detection during import simulations.- Flexibility to select/deselect objects from the import simulation UI, rather than wasting time editing the XML file or redoing the export phase.

- Individual errors will no longer interrupt an import. When the error makes a required object unavailable, the dependent operations will be automatically skipped.

- New user interface for imports: tree-like structure and colour coding now makes all import reports much easier to analyse.

- Easily identify the creation of new objects and changes to existing ones, and enable/disable them separately.

• [PCDEV-1141] - Verify compatibility with Jira 8.1
• [PCDEV-1036] - Export/Used by Report error when projects use a Fields Required Validator by JWME

• [PCDEV-1141] - Verify compatibility with Jira 8.1
• [PCDEV-1036] - Export/Used by Report error when projects use a Fields Required Validator by JWME

• [PCDEV-1061] - Project Configurator may remove priorities from the Default Priority Scheme
• [PCDEV-1065] - In some cases default values for hidden fields in JSD request types are not imported

• [PCDEV-1061] - Project Configurator may remove priorities from the Default Priority Scheme
• [PCDEV-1065] - In some cases default values for hidden fields in JSD request types are not imported

Version 2.4.6 is now compatible with Jira 8.0 and Jira 7.X (for 7.2.0 or newer).

Starting from version 2.4.6, Project Configurator is using analytics tracking that collects anonymous usage data. This data will help us to take the right actions needed to make your experience the best possible. More information please visit our EULA.

Version 2.4.6 is now compatible with Jira 8.0 and Jira 7.X (for 7.2.0 or newer).

Starting from version 2.4.6, Project Configurator is using analytics tracking that collects anonymous usage data. This data will help us to take the right actions needed to make your experience the best possible. More information please visit our EULA.

Fixed bugs:

• [PCDEV-916] - Filters referencing non-existing objects stop an export
• [PCDEV-919] - Comment Properties not maintained upon Import in the Jira Issue View

• [PCDEV-988] - JWME Set Issue security Level throw an error when set to no security level

Fixed bugs:

• [PCDEV-916] - Filters referencing non-existing objects stop an export
• [PCDEV-919] - Comment Properties not maintained upon Import in the Jira Issue View

• [PCDEV-988] - JWME Set Issue security Level throw an error when set to no security level

New Feature

• [PCDEV-868] - Allow for data import between different versions of Jira

Bug fixes:

• [PCDEV-958] - Improvements in handling extensions from recent versions of Jira Workflow Toolbox
• [PCDEV-920] - Organization field imported as null/blank.

New Feature

• [PCDEV-868] - Allow for data import between different versions of Jira

Bug fixes:

• [PCDEV-958] - Improvements in handling extensions from recent versions of Jira Workflow Toolbox
• [PCDEV-920] - Organization field imported as null/blank.

Change

• [PCDEV-859] - Extend the set of system groups to include those that define users with access to applications
• [PCDEV-872] - Some dependencies/libraries used by PC had security vulnerabilities

Bug

• [PCDEV-832] - Service Desk Show Transition to Customer Workflow option breaks the export.
• [PCDEV-843] - Error on importing boards when setting fields in the backlog view.
• [PCDEV-864] - Request types with same name and different issue types are not exported correctly

Change

• [PCDEV-859] - Extend the set of system groups to include those that define users with access to applications
• [PCDEV-872] - Some dependencies/libraries used by PC had security vulnerabilities

Bug

• [PCDEV-832] - Service Desk Show Transition to Customer Workflow option breaks the export.
• [PCDEV-843] - Error on importing boards when setting fields in the backlog view.
• [PCDEV-864] - Request types with same name and different issue types are not exported correctly

New Feature

• [PCDEV-853] - Extend support for sharing filters and dashboards to include shares with users and view/edit permissions

Bug

• [PCDEV-824] - "Create issue" and "Write to Linked Issues" post functions in recent JWT versions sometimes break export
• [PCDEV-842] - Jira Misc Workflow Extensions Workflow conditions cause export to fail

New Feature

• [PCDEV-853] - Extend support for sharing filters and dashboards to include shares with users and view/edit permissions

Bug

• [PCDEV-824] - "Create issue" and "Write to Linked Issues" post functions in recent JWT versions sometimes break export
• [PCDEV-842] - Jira Misc Workflow Extensions Workflow conditions cause export to fail

Support Escalation

Each of our DC Apps has it's own support escalation process, together with an improved SLA (24 hr - reasonable responses).

Robust DC Testing Framework

Our new DC Testing Framework means that when customers raise support tickets against our new DC offering we can more easily try to reproduce their problem in an actual DC environment.

Data Center Testing Framework

Developed our own process to enable us to spin up DC instances of BitBucket, Confluence and JIRA in a cluster. This allows us to quickly and easily test the performances of our Apps in different DC environments.

Performance Testing

We developed solutions using tools like nGrinder, JMeter and Gatling to help us measure the performance of BitBucket, Confluence and JIRA with and without our Apps so we can be sure we have the best offering at scale.

Large Data Sets

We invested in scripts to help us create larger data sets so that our Atlassian instances better reflect larger instances our DC customers are using.

Improvements:

• [PCDEV-40] - Highlight "X users could not be created" links at the import results view
• [PCDEV-819] - Display an improved error message when a zip file cannot be parsed

Bug fixes:

• [PCDEV-814] - Importing 24/24 SLA Calendars causes an error
• [PCDEV-818] - Field order not maintained on request type screens
• [PCDEV-820] - Filters that contain JQL functions sometimes are not correctly exported
• [PCDEV-844] - Simulating an import fails with a Cannot get property 'name' on null object" error

Changes:

• [PCDEV-810] - Compatibility with Jira 7.11
• [PCDEV-813] - Import trace now shows if a request type field is visible or hidden

New Feature:

• [PCDEV-711] - Support new version of 'Write field on linked issues or subtasks' and similar JWT post-function

Bug fix:

• [PCDEV-791] - Null pointer exception related to import of Request Type icons

Features

Change

• [PCDEV-772] - JIRA 7.10 compatibility

Bug fixes

• [PCDEV-720] - Simulations fail on references to a request type that has not been created yet
• [PCDEV-748] - Better error handling when an Agile board being exported does not have a filter
• [PCDEV-749] - Export errors are now added to the Jira log
• [PCDEV-766] - Export form freezes in IE11
• [PCDEV-770] - Export of JMWE - "Comment On Issue Post Function" fails with Number Format Exception

New Feature

• [PCDEV-699] - Remove permission checks in Agile board imports

Bug fixes:

• [PCDEV-733] - Ability to migrate organisations data (Jira Service Desk)
• [PCDEV-737] - Bug involving Automation rules default event User

Change

• [PCDEV-38] - Pressing 'enter' in the 'export project' form makes the browser go to the previous page instead of progressing to the next step
• [PCDEV-736] - Adding filename validation in export form

Improvements:

• [PCDEV-726] - Ensure compatibility with Jira 7.9
• [PCDEV-727] - Support new configuration in Kanban boards to hide done issues older than set limit
• [PCDEV-714] - Improve the error message for JQL parse errors
• [PCDEV-719] - Clarify extent of the options "Continue on errors with dashboard or filters"

Bug fixes:

• [PCDEV-635] - Can't remove the default priority of a priority scheme
• [PCDEV-720] - Simulations fail on references to a request type that has not been created yet
• [PCDEV-721] - Satisfaction survey results not migrated for Jira Service Desk
• [PCDEV-723] - Errors that occur in the simulated phase for complete imports cause a 404 error
• [PCDEV-725] - Changes to request type fields may error during the simulation if the request type has to be created
• [PCDEV-728] - Service desk automation rules involving components are not being handled correctly

New Feature

• [PCDEV-705] - Customer Satisfaction Configuration

• [PCDEV-7] - Support migration of portal features
• [PCDEV-9] - Support email configuration of a service desk
• [PCDEV-11] - Support migrating KB integration
• [PCDEV-32] - Migrate Service Desk reports

Improvement

• [PCDEV-709] - Improve performance of filtering custom fields by values used in exported projects on large databases

Bug

• [PCDEV-648] - Temporary files removal improvements

• [PCDEV-695] - Compatibility with Jira 7.8

Bugs

• [PCDEV-689] - Import of service desk request type fields failed in some cases on JIRA 7.7.2 (JSD 3.10.2)
• [PCDEV-647] - Task map replication fails in a Data Center environment with a ClassNotFoundException

New Feature

• [PCDEV-30] - Support transfer of automation rules
• [PCDEV-31] - Support approval steps
• [PCDEV-658] - Support transfer of notification rules

Bug

• [PCDEV-644] - Support new IssueCreate post function from Jira Workflow Toolbox Plugin
• [PCDEV-657] - Import Conflict Detection not progressing with ZIPs
• [PCDEV-666] - The mention about created values for "Customer request type" custom fields appears even for software projects
• [PCDEV-678] - Request Type icons are not imported correctly in Service Desk 3.10.0
• [PCDEV-683] - Can't import JSD project
• [PCDEV-685] - Project Versions Import - start date doesn't get imported (Complete Imports only)
• [PCDEV-686] - Service desk changes must be selected as "skipped" when the user chooses to skip "Project changes"

Change

• [PCDEV-688] - Update images to new logos

Improvement

• [PCDEV-669] - Adapt to JIRA 7.7 and Jira Service Desk 3.10.0

Bug

• [PCDEV-670] - Data import failed with a NPE when the source had some custom fields created by JSD not in the target

New Feature

• [PCDEV-101] - Add support for JIRA Service Desk (stage 1)

This version is able to export and import these configuration items in a Service Desk:

• Request types (including fields and status mappings)
• Request type groups
• Queues
• SLAs (including calendars, goals and conditions)

The rest of the configuration in a Service Desk project will be covered in other versions to be released during next weeks.

This version is also able to move a complete Service Desk project with its issue data to another instance.

See the linked issue for full details.

New Feature

• [PCDEV-621] - Add support for priority schemes (new in Jira 7.6)

Bug

• [PCDEV-626] - When the first configuration import in a complete import process fails, users may get 404 HTML error
• [PCDEV-622] - Choice of object types to be skipped does not persist between invocations of the "Import complete project" process
• [PCDEV-624] - In a Data Center environment a message appears in the logs saying that class ImportTaskContext cannot be found

Improvements:

• [PCDEV-34] - Re-enable option to filter custom fields used by project without considering custom field values
• [PCDEV-504] - Change "Do not load" label to "Skip"
• [PCDEV-534] - Permit skipping all object types in a complete project import
• [PCDEV-391] - Change links to the documentation shown by the plugin to point to the new doc site in adaptavist.com

Bug

• [PCDEV-54] - A subquery optimization bug in MySQL 5.5 halts the export when detecting values for custom fields
• [PCDEV-223] - Unable to export a project - NumberFormatException: For input string: ""

Improvements:

• [PCDEV-34] - Re-enable option to filter custom fields used by project without considering custom field values
• [PCDEV-504] - Change "Do not load" label to "Skip"
• [PCDEV-534] - Permit skipping all object types in a complete project import

Bug

• [PCDEV-54] - A subquery optimization bug in MySQL 5.5 halts the export when detecting values for custom fields
• [PCDEV-153] - Some classes that should be serializable are not
• [PCDEV-223] - Unable to export a project - NumberFormatException: For input string: ""
• [PCDEV-391] - Change links to the documentation shown by the plugin to point to the new doc site in adaptavist.com

Compatibility with Jira 7.5

Improvements:

• [PCP-728] - After a complete project import, warn the user if the import of filters, dashboards or Agile boards failed.
• [PCP-681] - Remove temporary files after export of complete projects
• [PCP-682] - Extend removal of temporary files to imports that do not complete the process.

Bugs

• [PCP-725] - Cannot export due to SQL error "Invalid object name 'jiraissue'"
• [PCP-734] - "Used by" report: if a null custom field is found while analyzing custom field values for exported projects, an exception prevents correct error reporting

Improvements:

• [PCP-728] - After a complete project import, warn the user if the import of filters, dashboards or Agile boards failed.
• [PCP-681] - Remove temporary files after export of complete projects
• [PCP-682] - Extend removal of temporary files to imports that do not complete the process.

Bugs

• [PCP-725] - Cannot export due to SQL error "Invalid object name 'jiraissue'"
• [PCP-734] - "Used by" report: if a null custom field is found while analyzing custom field values for exported projects, an exception prevents correct error reporting

New Features

• [PCP-627] - Name conflict detection
• [PCP-659] - Display report that shows where configuration objects are used

Improvements

• [PCP-677] - Import filters, dashboards and Agile boards after importing project data

• [PCP-619] - References to missing priorities or issue types in the card colors of an Agile board break the export

Bug

• [PCP-671] - Replace sprint IDs used in JQL queries by the sprint name

New Features

• [PCP-627] - Name conflict detection
• [PCP-659] - Display report that shows where configuration objects are used

Improvements

• [PCP-677] - Import filters, dashboards and Agile boards after importing project data

• [PCP-619] - References to missing priorities or issue types in the card colors of an Agile board break the export

Bug

• [PCP-671] - Replace sprint IDs used in JQL queries by the sprint name

Compatible with Jira 7.4, it supports "extended project administration" in permission schemes. This means that a permission scheme will keep the same value (extended or not) for this attribute when imported into another instance.

Improvement

• [PCP-668] - Improve and reorganize data import trace around projects
• [PCP-676] - Remove temporary files after successful import of complete project
• [PCP-529] - Improve error reporting when an exception occurs during transformation of workflows

Bug

• [PCP-408] - A reference to a nonexistent user would crash export of default users for project role, regardless of the option chosen for exporting users
• [PCP-521] - Some validation errors that stop data import are not clearly identified (exceeding maximum text field size)
• [PCP-653] - Huge time for import of large custom fields

Improvement

• [PCP-668] - Improve and reorganize data import trace around projects
• [PCP-676] - Remove temporary files after successful import of complete project

• [PCP-529] - Improve error reporting when an exception occurs during transformation of workflows

Bug

• [PCP-408] - A reference to a nonexistent user would crash export of default users for project role, regardless of the option chosen for exporting users
• [PCP-653] - Huge time for import of large custom fields

Improvement

• [PCP-614] - Adapt to newer versions of Jira Workflow Toolbox
• [PCP-615] - Adapt to newer versions of Jira Misc Workflow Extensions

Bug

• [PCP-578] - Creates users marked "inactive" as "active" during import
• [PCP-594] - Detection of postfunction order changes
• [PCP-618] - Workflow publish link for workflow name containing "-" and "+" leads to dead 404 link
• [PCP-637] - The message when members of groups jira-users or jira-administrators are going to change is not accurate

Improvement

• [PCP-614] - Adapt to newer versions of Jira Workflow Toolbox
• [PCP-615] - Adapt to newer versions of Jira Misc Workflow Extensions
• [PCP-617] - Detect if the user is trying to export/import Agile boards and Jira Agile version is unsupported by PC

Bug

• [PCP-578] - Creates users marked "inactive" as "active" during import
• [PCP-594] - Detection of postfunction order changes
• [PCP-618] - Workflow publish link for workflow name containing "-" and "+" leads to dead 404 link
• [PCP-637] - The message when members of groups jira-users or jira-administrators are going to change is not accurate

Improvements

• [PCP-597] - Automate export and load of projects (configuration AND data)
• [PCP-600] - Import filters, dashboards and Agile boards after configuring projects (configuration only import)
• [PCP-601] - Permit columns in Agile boards without associated statuses
• [PCP-602] - Add workflow schemes to the list of object types that can be skipped in a complete project import

Improvements

• [PCP-597] - Automate export and load of projects (configuration AND data)
• [PCP-600] - Import filters, dashboards and Agile boards after configuring projects (configuration only import)
• [PCP-601] - Permit columns in Agile boards without associated statuses
• [PCP-602] - Add workflow schemes to the list of object types that can be skipped in a complete project import

Improvements

• [PCP-572] - Show progress bar when uncompressing zip file and performing first checks on it
• [PCP-571] - Better initial checks about the availability of zip file for a complete import
• [PCP-585] - Permit skipping custom field and workflow configurations when importing complete projects
• [PCP-529] - Improve error reporting when an unexpected exception happens during transformation of workflows

Bugs

• [PCP-563] - Some workflow extensions defined by Jira Suite utilities plugin are not supported
• [PCP-556] - Workflow processing breaks with message "javax.xml.transform.TransformerConfigurationException: Cannot find external method"
• [PCP-583] - Warning about resource not found in the logs

Improvements

• [PCP-572] - Show progress bar when uncompressing zip file and performing first checks on it
• [PCP-571] - Better initial checks about the availability of zip file for a complete import
• [PCP-585] - Permit skipping custom field and workflow configurations when importing complete projects
• [PCP-529] - Improve error reporting when an unexpected exception happens during transformation of workflows

Bugs

• [PCP-563] - Some workflow extensions defined by Jira Suite utilities plugin are not supported
• [PCP-556] - Workflow processing breaks with message "javax.xml.transform.TransformerConfigurationException: Cannot find external method"
• [PCP-561] - Unable to enable addon after successful install on Java 1.7
• [PCP-583] - Warning about resource not found in the logs

• [PCP-549] - Verify compatibility with Jira 7.3

New Feature

• [PCP-501] - Check plugin availability during the simulation import for Custom Fields

Improvement

• [PCP-539] - Improve wording of message about orphaned custom field values
• [PCP-548] - Add support for filters shared with any logged in user
• [PCP-557] - Improved error handling so that errors when fetching and parsing zip files for complete project imports are reported earlier

Bug

• [PCP-514] - When new project versions are created as part of a configuration import, in some cases they are not created exactly as described in the XML file
• [PCP-535] - Missing status when changing agile board columns is not reported properly
• [PCP-538] - If the data import fails, in some cases recovering the missing users will cause a NPE

New Feature

• [PCP-501] - Check plugin availability during the simulation import for Custom Fields

Improvement

• [PCP-539] - Improve wording of message about orphaned custom field values
• [PCP-557] - Improved error handling so that errors when fetching and parsing zip files for complete project imports are reported earlier

Bug

• [PCP-535] - Missing status when changing agile board columns is not reported properly
• [PCP-538] - If the data import fails, in some cases recovering the missing users will cause a NPE

New Feature

• [PCP-206] - Add export and import of Agile boards

Improvement

• [PCP-274] - Avoid error in export when trying to order duplicate items in schemes (permission, notification, issue security,...)

Bug

• [PCP-518] - Presence of locked custom fields in screens and field configurations is not exported

New Feature

• [PCP-206] - Add export and import of Agile boards

Improvement

• [PCP-274] - Avoid error in export when trying to order duplicate items in schemes (permission, notification, issue security,...)

Bug

• [PCP-518] - Presence of locked custom fields in screens and field configurations is not exported

Improvement

• [PCP-506] - Locked custom fields are ignored and not included in the configuration

Bug

• [PCP-510] - Some issue types are not found when their name has leading or trailing whitespace
• [PCP-511] - A user filter that references a role that will be created during the load, breaks the simulated import
• [PCP-513] - Import complete project: setting to run first a simulated configuration import does not persist

Improvement

• [PCP-506] - Locked custom fields are ignored and not included in the configuration

Bug

• [PCP-510] - Some issue types are not found when their name has leading or trailing whitespace
• [PCP-511] - A user filter that references a role that will be created during the load, breaks the simulated import
• [PCP-513] - Import complete project: setting to run first a simulated configuration import does not persist

Improvements

• [PCP-495] - Show users that could not be created during data import, especially mandatory ones
• [PCP-505] - In case of error during data import continue with remaining projects
• [PCP-493] - Improve information of the HTTP header when downloading a XML config file

Bug

• [PCP-503] - Sometimes attachments are not exported with the complete project

Improvements

• [PCP-495] - Show users that could not be created during data import, especially mandatory ones
• [PCP-505] - In case of error during data import continue with remaining projects
• [PCP-493] - Improve information of the HTTP header when downloading a XML config file

Bug

• [PCP-503] - Sometimes attachments are not exported with the complete project

Improvement

• [PCP-479] - Improve logging for the data import stage (when importing complete projects)

Bug fixes:

• [PCP-379] - Can't export a project due to a SQL error
• [PCP-482] - In some cases export errors are displayed without location message
• [PCP-485] - Permission scheme created with 'empty Single User' when user doesn't exist

Improvement

• [PCP-479] - Improve logging for the data import stage (when importing complete projects)

Bugs

• [PCP-379] - Can't export a project due to a SQL error
• [PCP-482] - In some cases export errors are displayed without location message

Functionally identical to version 2.0.1-J7, just adds compatibility with Jira 7.2.

Bug

• [PCP-453] - Can't export entire project: net.lingala.zip4j.exception.ZipException: java.lang.IndexOutOfBoundsException
• [PCP-455] - Clicking on the "Configure" link in the UPM entry for Project Configurator returns a 404 (not found error)

Other minor fixes

Bug

• [PCP-453] - Can't export entire project: net.lingala.zip4j.exception.ZipException: java.lang.IndexOutOfBoundsException
• [PCP-455] - Clicking on the "Configure" link in the UPM entry for Project Configurator returns a 404 (not found error)

Other minor fixes.

New Feature

• [PCP-433] - Import and export complete projects, not only their configuration

The new version automates the process of moving projects from one instance to another. Instead of following the process described in this page, the user of the new version can perform a single export of "configuration and data" at the source instance, and then "Import complete project" at the destination instance with the created .zip file.

Some points to consider:

• Attachments (if they exist) are automatically included in the process.
• The user can transfer one project, all the projects or a selected group in a single operation.
• Data belonging to other projects different to those exported, will be excluded from the generated export file.

Have a look at the Getting started guide!

Improvement

• [PCP-283] - Ability to change names of export files

New Feature

• [PCP-433] - Import and export complete projects, not only their configuration

The new version automates the process of moving projects from one instance to another. Instead of following the process described in this page, the user of the new version can perform a single export of "configuration and data" at the source instance, and then "Import complete project" at the destination instance with the created .zip file.

Some points to consider:

• Attachments (if they exist) are automatically included in the process.
• The user can transfer one project, all the projects or a selected group in a single operation.
• Data belonging to other projects different to those exported, will be excluded from the generated export file.

Have a look at the Getting started guide!

Improvement

• [PCP-283] - Ability to change names of export files

[PCP-450] - Some dashboard gadgets imported using plugin does not show up appropriate filter/project defined

[PCP-450] - Some dashboard gadgets imported using plugin do not show up appropriate filter/project defined

Improvements

• [PCP-439] - Early detection of some anomalous permissions and notifications
• [PCP-442] - Include in export objects referenced by Jira default workflow

Bug

• [PCP-440] - Trying to assign a permission to a user that does not exist creates an inconsistent permission
• [PCP-438] - In some cases 'Workflow' and 'Resolve issue' screens aren't exported
• [PCP-441] - Sometimes the location message is lost when an error happens during export

Improvements

• [PCP-439] - Early detection of some anomalous permissions and notifications
• [PCP-442] - Include in export objects referenced by Jira default workflow

Bug

• [PCP-440] - Trying to assign a permission to a user that does not exist creates an inconsistent permission
• [PCP-438] - In some cases 'Workflow' and 'Resolve issue' screens aren't exported
• [PCP-441] - Sometimes the location message is lost when an error happens during export

New Feature

• [PCP-430] - Automated publishing of worklow scheme drafts and workflow drafts

Improvement

• [PCP-429] - Create drafts of active workflow schemes, instead of copies

Bug

• [PCP-424] - Possible loss of data integrity when assigning a workflow scheme to an existing project

New Feature

• [PCP-430] - Automated publishing of worklow scheme drafts and workflow drafts

Improvement

• [PCP-429] - Create drafts of active workflow schemes, instead of copies

Bug

• [PCP-424] - Possible loss of data integrity when assigning a workflow scheme to an existing project

[PCP-422] - When context path is not "jira", a 404 (not found) error is shown instead of results page at the end of import

[PCP-422] - When context path is not "jira" a 404 (not found) error is shown instead of results page at the end of import

Improvement

• [PCP-421] - New user interface for exporting configurations
• [PCP-242] - Ability to export/import selected projects
• [PCP-419] - Add an indicator (progress bar) that shows progres of import
• [PCP-418] - Renderers are no longer considered mandatory

Bug

• [PCP-415] - Export fails on Scriptrunner CloneIssue with empty issue type
• [PCP-416] - Export fails on Scriptrunner CloneIssue with inward link type

Improvement

• [PCP-421] - New user interface for exporting configurations
• [PCP-242] - Ability to export/import selected projects
• [PCP-419] - Add an indicator (progress bar) that shows progres of import
• [PCP-418] - Renderers are no longer considered mandatory

Bug

• [PCP-415] - Export fails on Scriptrunner CloneIssue with empty issue type
• [PCP-416] - Export fails on Scriptrunner CloneIssue with inward link type

• [PCP-396] - Map users across instances by username instead of mapping by the user key
• Verified compatibility with Jira 7.1.0

• [PCP-396] - Map users across instances by username instead of mapping by the user key

New Feature

• [PCP-393] - Option to ignore invalid filters or dashboards during import

Improvement

• [PCP-392] - Do not show box with warnings in the import page when the user has already run an import

Bug

• [PCP-388] - Default project creation takes the username of the user that is running the import as if it were its key

• [PCP-393] - Option to ignore invalid filters or dashboards during import

Improvement

• [PCP-392] - Do not show box with warnings in the import page when the user has already run an import

Bug

• [PCP-388] - Default project creation takes the username of the user that is running the import as if it were its key

New Feature

• [PCP-207] - Add support for Workflow Layouts
• [PCP-378] - Add options to export only global filters/dashboards or those associated to exported projects

Improvement

• [PCP-376] - Make export more robust in the face of internal problems in custom field contexts
• [PCP-386] - Issue warning when spaces are trimmed around issue constant names

New Features:

• [PCP-207] - Add support for Workflow Layouts
• [PCP-378] - Add options to export only global filters or dashboards or those associated to exported projects

Improvements:

• [PCP-376] - Make export more robust in the face of internal problems in custom field contexts
• [PCP-386] - Issue warning when spaces are trimmed around issue constant names

Improvements

• [PCP-370] - Prevent users from submitting more than one import request at the same time
• [PCP-372] - Better detection of available project types
• [PCP-385] - New visual identity for Awnaba and Project Configurator
• [PCP-384] - Issue informative message when a null custom field is found with values for issues in the exported projects

Bugs

• [PCP-381] - The username was taken as a reference to users that own filters or dashboards

Improvements

• [PCP-370] - Prevent users from submitting more than one import request at the same time
• [PCP-385] - New visual identity for Awnaba and Project Configurator
• [PCP-384] - Issue informative message when a null custom field is found with values for issues in the exported projects

Bugs

• [PCP-381] - The username was taken as a reference to users that own filters or dashboards

[PCP-353] - Do not publish ClearCacheEvent at the end of the import

See this issue for an important usage notice and enjoy the new version!

• [PCP-365] - Adapt plugin to Jira 7
• [PCP-353] - Do not publish ClearCacheEvent at the end of the import

IMPORTANT: See notice at PCP-353

Improvements

• [PCP-338] - Improve handling of field configurations
• [PCP-360] - Provide meanigful error message when a "legacy" portlet is found
• [PCP-361] - Show in Jira log stack traces of errors found during export

Bug

• [PCP-357] - Project lead is searched by user name instead of user key
• [PCP-363] - Users that own a dashboard were not exported

Improvement

• [PCP-310] - Add option to skip System Dashboard import
• [PCP-315] - Handle version start dates

Bug

• [PCP-309] - Function arguments in exported filter queries are not always quoted correctly
• [PCP-311] - Projects referenced in dashboard gadgets user preferences are exported
• [PCP-318] - Prevent custom field translations from creating new custom field for different languages
• [PCP-325] - Renamed users were not supported