Backbone Issue Sync 3.0.82-AC

May 2022

We're happy to announce the release of Backbone Issue Sync 3.0.82-AC!

This release comes with feature upgrades that will help you automatically synchronize versions across your paired Jira projects. This includes synchronization of not only the version names but also your project version attributes such as the status and release date, irrespective of whether they on the same cloud instance or on different cloud instances.

Here's a short guide on what the new update brings, along with instructions on different configurations and their usage.

Automatically Sync Jira Project Versions

In addition to syncing issues, now you can also rely on Backbone to synchronize your project versions and keep track of any version changes across different projects.

Here’s what’s new:

• You can use Backbone for simultaneous synchronization of all versions in a Jira project, irrespective of whether the version is currently being used in an issue or not.

• When you rename a Jira project version, Backbone will automatically sync the new version name to the corresponding synchronized project, so don’t have to manually change or delete the old version.

• Similarly, any changes you make in the attributes of a version on one Jira project will automatically be synced by Backbone to the corresponding Jira projects' version attributes. You can keep the following attributes in sync:

  • Name

  • Description

  • Status

  • Start date

  • Release date

What You Might Need To Change in Your Versions Settings

• Scenario 1: You were syncing the Version fields without creating any new versions
  → No action required. The first option in the project tab, i.e. “Disabled”, will be automatically applied.
  
  

• Scenario 2: You were syncing the Version fields for all of your projects and selected the “create missing versions” option for all synchronizations
  → No action required. The second in the project tab, i.e. “Field Mapping”, will automatically be applied.
  
  

• Scenario 3: You were syncing the Version fields and selected the “create missing versions” option for some synchronizations, but not all of them
  → The first option in the project tab, i.e. “Disabled”, will automatically be applied. No project versions will be synced nor any missing versions will be created until you manually select a different option.

Learn how to start synchronizing versions across your Jira projects in our detailed  help documentation →

JQL Editor Just Got Smarter

The integrated JQL editor is used to limit the issues that are being synced by assigning them particular labels. Another feature update in this release improves your JQL editor experience by introducing the auto-fill feature, after which the editor will automatically suggest and fill out the commands, making it easier, more time-efficient, and less prone to errors.

You can watch the new JQL editor in action below:

Questions?

Do you have questions or is something not working as expected? Don’t fret, we are here to help!🙂 

Please create a ticket in our support system or write an email to help@k15t.com!

All updates and fixes in this release