Issues
- Backbone fails to restart all synchronizations on Jira restartBAC-1436Resolved issue: BAC-1436
- Backbone shows the wrong synchronization status in a Data Center environmentBAC-1435Resolved issue: BAC-1435
- Synchronization status is different across Data Center nodesBAC-1431Resolved issue: BAC-1431
- Async task with id not found on Backbone CloudBAC-1423Resolved issue: BAC-1423
- Connection errors when running Jira on Java 11 ( > 8)BAC-1408Resolved issue: BAC-1408
- Support Jira 8.4BAC-1345Resolved issue: BAC-1345
- Sprints are duplicated when multiple issues are moved to a new sprintBAC-1332Resolved issue: BAC-1332
- The public API example can not be build without access to Backbone's parent pomBAC-1308Resolved issue: BAC-1308
- Improve UI performance through cachingBAC-1197Resolved issue: BAC-1197
- Jira 7.12.1 compatibilityBAC-1168Resolved issue: BAC-1168
- Jira 7.12 compatibilityBAC-1163Resolved issue: BAC-1163
- Allow synchronizations to be automatically stopped when Backbone is restarted/re-enabled/re-installedBAC-1156Resolved issue: BAC-1156
- Add option to use a separate log file instead of atlassian-jira.logBAC-1152Resolved issue: BAC-1152
- Make Backbone more robust against network problemsBAC-1126Resolved issue: BAC-1126
- Check Jira 7.9.x compatibilityBAC-1085Resolved issue: BAC-1085
- Comments in Jira Cloud are not syncedBAC-1055Resolved issue: BAC-1055
- Backbone does not start after Tomcat updateBAC-1034Resolved issue: BAC-1034
17 of 17
