v2.3.1

With the new release, we have introduced a new field mapping option to map rendered values. To use the new mapping add "mapper":"MapRendered" for description or comment field.

In addition to this feature, we have fixed several issues in the migration tool.

Changes:

• 02b61b3 Updated version to 2.3
• f3ae6f0 Links were not added on migration because true and false conditions were in the incorrect order (#138)
• 53fdc56 When building executionplan and updating times for workitem revisions before we update current revision time we should keep the scope when comparing times to the specific workitem. (#137)
• 9a8ce66 Refactoring and cleaning up renderd filed mapping. Created common me… (#134)
• 82a5909 Ensuring that when workitem state is set to done the ClosedBy field is mapped to correct value. (#136)
• 2d7f4d9 Feature/52 links not added to workitem (#131)
• a6aba46 Removing explicit Description mapping and using Generic renderd field… (#132)
• 4eca131 Fixing null reference exception when System.State does not have value set and we try to get string value. (#133)
• 66ee764 Feature/78 state change handling (#130)
• f59b880 fix: correctly map arrays based off value key (#74)

See More

• 369cf4d Updated documentation and sample config with the new MaprRenderd option (#129)
• e6ffe59 Making sure created date it not null, small refactoring to remove duplicate code (#127)
• 7986de9 Fixing Issue #95 when assignee is removed from jira issue then during import we get null reference exception. Added null check and to set string.emtpy to set it to unassigned. (#128)
• 8a56dc4 Updated to allow for custom types and their Rendered versions. (#83)
• da184e9 Updated JiraMapper with target Types for field mapping - including logs and docs (#82)

This list of changes was auto generated.