-
Suggestion
-
Resolution: Fixed
Companion should have a config or install option to disable backwards compatible code paths. In particular, if users are using Confluence 7.3 + then they do not require Companion to start a local websocket server.
[CONFSERVER-60273] Companion should have an option to disable running local websocket server
Workflow | Original: JAC Suggestion Workflow 4 [ 3978120 ] | New: JAC Suggestion Workflow 3 [ 4338703 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
QA Demo Status | Original: Not Done [ 14330 ] | New: Not Needed [ 14332 ] |
Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
Story Points | New: 3 |
Fix Version/s | New: Companion-1.2.7 [ 96391 ] |
Sprint | New: Greater Glider [ 6509 ] | |
Labels | New: samurai |
Remote Link |
New:
This issue links to "Companion › Companion CI (Electron 2 NVM) › issue- |
Remote Link |
New:
This issue links to "Companion › Companion CI (Electron 8 NVM) › issue- |
A fix for this issue is available in Companion 1.3.0. View the Release Notes to see what other issues are resolved.
If Companion is installed via the MSI, then it will need to be manually updated to the new version.