It looks like when the "dark feature" is enabled in Confluence 6.15.6 the dropdown "Edit with" path to the Companion disappears. If so. this would frustrate those who do successfully use the Companion, i.e. those in our organization lucky enough to have the rights and/or browser able to use it.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
@Brad Taplin Yes, it is either or. The point of this is to bring back the old functionality for those that cannot use the Companion app due to being in a terminal services environment. It sounds like this dark feature will go away once they get the companion app working for terminal services.
I'm on an Air Force network and we cannot install the Atlassian Companion app unless it has been vetted by Air Force Network Integration Center (AFNIC).
I want to submit the Atlassian Companion appto get certified for use on DoD/AFNET but I will need a point of contact (POC) by the developers.
Thomas - because the dark feature and Companion appear to be, effectively, mutually exclusive, insofar as enabling the former makes some of the latter not function, we are foregoing the dark feature. Which of course leaves us at least partly where we were the moment we upgraded: many users just lost functionality. It has been so long they have learned to live without that.
This was not a satisfying outcome, but it is what it is. Having to download, edit, and upload is what folks who cannot use the Companion, due to corporate restrictions on both client apps and proxies, will live with. Our users technically have a way to request the Companion, but it's bureaucractic and most won't.
"in future releases we will look to address" is actually very bad news, we have expected to read "in Confluence 7.0" which would fit with our users expectation. There is much pressure in our company, and I assume in many others with Citrix landscapes as well, towards Office365 with its surrounding services, including Microsoft Teams. Weak points of any existing tool are very welcomed and not being able to edit Office documents inplace is a heavy one for Confluence. Forwarding "in future releases" as Atlassian's answer without a clear and guaranteed time line means Atlassian ignores customer needs.
Our situation: Edit in Office will be replaced by Confluence 7.0; Companion App in Citrix environment not supported; Word and Excel macros in Confluence are using WebDav which is not supported anymore ... dead end for all persons which still need to work with Word / Excel / PPT files.
35 comments