-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
7
-
Severity 3 - Minor
-
0
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Summary
- Edit the document using Atlassian Companion is not working on terminal server with multiple desktop session
Steps to reproduce
- The first user tries to edit the document and receives a prompt to download and install the Atlassian Companion app which then gets installed into their user profile. And they can open the document correctly.
- The second user logged on to the same Terminal Server tries to open a different document using Atlassian Companion (the second user will not be prompted to install the Atlassian Companion – instead the document will open on the first user’s desktop)
- If the first user shuts down the Atlassian Companion by clicking Quit in its tray menu, the second user will now be prompted to download and install the Companion app and the second user able to open documents on their second user desktop.
- If another user tries to edit a document using Atlassian Companion it will open on the second user’s desktop.
Environment
- Operating System: Windows Server 2012 R2.
- Microsoft Office version: Microsoft Office 2013.
Expected Result
- Edit the document using Atlassian Companion will show on the same desktop session.
Actual Result
- Edit the document using Atlassian Companion will show on the previous desktop session that using Atlassian Companion before.
Workaround
- If the user already done using the Atlassian Companion to close the Atlassian Companion.
Notes: I can't reproduce-able the issue as we don't have the infrastructure to test.
- relates to
-
-
- Closed
-
![[Confluence] Page](/images/icons/generic_link_16.png "[Confluence] Page"){kind=icon}
[CONFCLOUD-56557] Edit the document using Atlassian Companion is not working on terminal server with multiple desktop session
In the Confluence Server version we had no problems with the Companion App under CITRIX. After we migrated to the cloud in September 2021, we have these problems with the Companion App in the CITRIX environment, which have already been described here several times. We are now hoping for a solution soon, especially as this BUG has been in development here since 2017 with status in progress.
Many thanks in advance
we will evaluate GoEdit as a workarround.
Thank you for the comment !
Upfront disclaimer: I am biased since we are the vendor of GoEdit
We offer GoEdit for Confluence and Jira as an upgrade of Edit in, which has a terminal server integration since 3 years.
We have a demo online http://goedit.io so you can test it without any strings attached.
If you rely on a terminal integration, maybe this is a solution for an upgrade/enrichment to the build in Edit in if Confluence functionality.
Please see this comment as "If you are seriously blocked by this issue and need an alternative by any means, GoEdit can be a payed solution to this problem"
Has anyone found a working workarround?
I am still searching
Hello from Germany,
we have a terminalserver too. Please fix this issue as soon as possible.
with best regards, Kai
This is a step closer modern IT-infrastructure. Please resolve this as soon as possible.
Thank you,
We detect the same issue on our Citrix XenApp 7.15 environment (Session-based virtual desktops). It's a must have to run this feature from a Citrix/Terminal server environment, for better user experience and adoption of Jira within our organization.
We have the same problem. It is not possible to get the Companion App in our Citrix/Terminalserver Environment running normaly. We are on 6.11 and upgraded to get the "edit in" feature for firefox quantum. It would be nice to get a fix asap.
Companion App integration has been removed from Confluence Cloud. Therefore this ticket is closed as "won't fix".
See the community post for details