We improved the way you can map the resolution field of an issue. This fixes the bug BAC-1124 a lot of customers have waited for. The new behavior is now correctly considering the history of resolution changes as well. This means, if an issue gets resolved multiple times, Backbone applies the resolution with each status that is mapped in the workflow mapping and requires a resolution.
The workflow mapping is a complex feature in Backbone due to the power and variety of possible Jira workflow configurations. Please pay special attention in your upgrade testing if your workflow synchronization is running smoothly.
Deprecation of Old Resolution Field Mapping
With this release we're also deprecating the old resolution field mapping. This field mapping is using a global looped transition to apply the resolution on an issue. We're planning to remove this field mapping in a future release - we'll announce the related release version in advance.
Questions?
Do you have questions or something is not working as expected? Please let us know and create a ticket in our support system or write an email to support@k15t.com.
We use cookies to create a secure and effective browsing experience for our website visitors and to understand how you use our site (i.e. Google Analytics). For more information: Click Here
