Issues

Backbone shows the wrong synchronization status in a Data Center environment

Synchronization status is different across Data Center nodes

Mail server credentials fail for certain characters

Change way of setting a mail server password for distributed configurations

Backbone fails to send messages in a distributed configuration on Jira 8.5+

Automatic sync of issues does not work after starting a sync in the cloud

Wrong version check when syncing workflows

Synchronizations don't start automatically after restart

Provide option to always use Basic Authentication

SMTP mail server connection using TLS is failing

Reconnect task for Jira client is not correctly cleaned up

Connection issues between Backbone and Jira cause problems

Issue type can not be found in Backbone's cache

Make it possible to modify threadPool values like maxQueueSize

"Invalid cookie header: expires" warning logged for Jira client

Improve HTTP authentication for Jira client

Run synchronizations only at specific times

Initialization and reconnect logic results in an endless loop

Support Jira 8.4

Outgoing changes fail due to NullPointerException

NullPointerException when synchronizing a field if mapping can not be found

Creating an issue with a field without schema fails

Backbone on Data Center fails with com.atlassian.jira.cache.ehcache.customserialization.CustomSerializedValue is not Serializable

In the Limit Issue dialog allow the user to test and migrate the JQL

Show project size (issues number) in the New Synchronization step

Improve upgrade process of Backbone

Backbone should allow to copy the value of Epic link in the field mapping configuration

Permission check is failing if Jira Service Desk is disabled in cloud

Support moving of issues between two synchronizations

Add multiple comments with a minimum waiting time to avoid missed comments

comments are not synced correct in JSD

License validation failure when disable/enable Backbone on Data center

Backbone creates duplicate attachments

Fallback user can not be set in cloud

Disable of issue type mappings does not work properly

Backbone fails authenticate due the external error: java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_XXXXXXXXXX) has been shut down

Issue updates in the cloud are not synced anymore

Show a detailed sync activity to the Backbone admin

Add option to never sync changes when issue is filtered by a JQL

Backbone fails due the error :{"assignee":"expected Object containing a 'name' property"}}

Backbone may fail resync in distributed environment, if the whole message size exceeds the email servers message size limit

Show user which data is applied when resyncing changes

Backbone on Data Center fails with java.io.NotSerializableException

Backbone does not update correctly the status in a Datacenter node after the single node is restarted

Add possibility to remove the sync relation between two issues

Status sync is wrong if status is changed while sync is pending

Backbone sync is stopped after rebooting a whole Jira data center cluster

Resolution is mapped wrong if multiple workflow transitions are applied

Implement Atlassian API changes regarding user data