Collaborator WebUI looks different for different people
Hey everyone I have two Collaborator users who have behavior that the rest of us do not - one user is not getting document differences highlighting - Another user has the 'chat window' doing weird thing after he adds a comment (the window collapses, then the comment windows get big enough to occlude the function buttons) I'll submit tickets for some of these, but I'm curious if other have had Collaborator WebGUI act different for some people, even while they use the same browser and have the same settings as everyone else.
Collaborator and Outlook
Hey Community I personally started getting an issue. When I click on the envelope next to a review participants name, I get the error shown below. When I select 'email all', that works fine. This is a new error, and seems to affect my only - others are not getting the issue. The outlook app is indeed at the path shown in the error box. Outlook is still a local app (not 365 yet) so that's not an issue. Wanted to get the community's thoughts first, as when I go to IT they will just blame SB. 🙂 Thoughts?Issue with hung client when adding comments.
Several users are seeing issues where the client gets hung when adding a comment or marking a comment as read. (spinner keeps spinning and the comment is not seen/refreshed). A screen refresh (F5) fixes the issues and does show the new comment, but this is annoying... This is seen in Firefox, and has been observed for several Collaborator versions (we are now on 13.8) Is anyone else seeing this? Any pointers? I tried cleaning the cache but the issue comes back. Marc
Inability to delete an Upload to Review Materials due to comments
I have searched all the documentation and conversations and understand that an upload to the Review Materials can not be deleted if there is a comment or defect in any one of the files, so I have no question about that. But I do have a comment about that. That is the most short-sighted and ridiculous rule. The idea that a responsible Administrator can not correct a Review is extremely frustrating. What has happened is in a Review with about 10 changed files, the author in attempting to correct an error in his code erroneously uploaded a branch with hundreds of changed files. Now we are stuck with this huge set of changes - NOT because someone has commented on this new upload, but because someone had previously commented on one of the files in that upload, which collaborator so conveniently carries over to the new upload. Of course we uploaded the correct set of files afterword, BUT have had to put up an overall comment, which we can only HOPE that our Reviewers will see, to tell everyone to ignore uploads before a certain date. If they don't notice this message then they'll spend hours reviewing incorrect code changes. So we need to go to an outside method to email everyone to be careful about this review because Collaborator wont allow us to logically control our own review. The idea that "Smartbear" doesn't think we are smart enough for an Administrator to surgically edit a Review to correct errors feels like being managed by a helicopter parent. This along with several other issues like not being able to control the placement of User Defined Fields (making our Review forms haphazard and confusing), an inability to create Reports in our own format, and even the fact that Notes for a file are displayed in a Center Justified column (so that short notes can't be seen at all because they are sitting out in the middle of someone else's 3 sentence notes). That such basic functions are out of our control becomes very annoying. Despite the time and effort we have spent converting to and learning Code Collaborator many people are starting to recognize that there are other options out there that might be more flexible.
