Skip to content

Releases: jazz-community/rtc-workitem-bulk-mover-service

Version 1.5.3

16 Jul 11:16
Compare
Choose a tag to compare

Switch to explicit UTF-8 usage. This allows for proper treatment of content that is not part of the standard eclipse charset, e.g. Japanese characters in project area names (fixes #13 )

Version 1.5.2

03 Jul 13:48
Compare
Choose a tag to compare
  • Added support for removing the Rank attribute on move

Version 1.5.0

23 Nov 15:57
Compare
Choose a tag to compare

This release might introduce a breaking change for consumers that use this service without WIBM UI or using an older version of WIBM UI. So It is best to upgrade to WIBM UI 1.5.0

In this release, the server side service and the UI plugin have been reworked in terms of primitive and custom attribute handling, which should work now in all cases and is a lot more flexible and robust. Please give as feedback in case there are still edge cases that cause trouble.

Version 1.4.5

19 Nov 07:54
Compare
Choose a tag to compare
  • Support for suppressing Email notification on move implemented.

Version 1.4.2 & 1.4.3

15 Jun 07:01
Compare
Choose a tag to compare
  • Support to show iteration in a hierarchical form
  • Catch certain error cases when move fails
  • add a new service to provide the plugin version

Version 1.4.1

27 Apr 13:18
Compare
Choose a tag to compare
  • Improved move within the same project area, add detection for required 'Unassigned' categories

Version 1.4.0

20 Apr 13:46
Compare
Choose a tag to compare

This exciting release addresses the needs of enterprises that have customized work item process templates, with custom required attributes and scenarios, where you want to move work items within the same project area to a new work item type.

New Features

  • General support for custom attributes of type category, interval and deliverable - This means that the service can handle all attributes that refer to categories, iterations and releases
  • General support for most custom attribute types that base on a primitive value - This means you can move items to a project area where attributes with primitive types exist and are required by the process
  • Support moving within the same project area from one type to another - If you are about to deprecate a work item type in your process, support moving those work items to another work item type

Version 1.3.0

28 Mar 08:08
Compare
Choose a tag to compare

New Features

  • The defined value mappings are now kept when a move fails and returned back to the user

API Changes
The following, backward compatible API change has been made:

  • The project-areas endpoint now accepts a comma separated list of project area UUID's that will be ignored in the response. Example /project-areas?ignore=__TZ0cwP5bEeanwOtOCiP3RQ

Version 1.2.1

22 Dec 15:48
Compare
Choose a tag to compare

This release has received some overall refactoring. Additionally, the following quality improvements have been implemented:

  • Never allow a missing target work item type (fixes #9)
  • Target type list is now sorted ascending
  • Make sure that required attributes, where source and target value are 'null', are provided for mapping (fixes #10)
    Please make sure that you also the UI which has received a fix as well

Version 1.2.0

08 Dec 20:57
2a8b00c
Compare
Choose a tag to compare

This release separates the work item type mapping from the other attribute mappings in order to achieve a predictable state mapping when using WIBM UI

Quality Improvements

  • Project area list now shows up in alphabetical order
  • Consistent, improved state and type mapping, including migration