Collaborator Feature Requests

If I write a comment on a review and later want to delete it, I click the Delete button to do so. The message which then appears looks like the image below:     So I have to click Confirm if I want to cancel, and Cancel if I want to cancel the cancellation; i.e. I don't want to cancel the comment. I think.   I think it would be a lot clearer if it used the word "Delete" instead of "Cancel", so could say "Are you sure you want to delete this comment?", and had Yes/No buttons, such that Yes deletes the comment, and No doesn't. ... View more

We would like to copy templates and role configurations instead of having to update all default settings. This would speed up our process of adding new groups when customizations are required.  ... View more

In a large review with many files and multiple participants, if you are not the first or last participant, it is hard to know which column is yours in the list. This makes it difficult to see if you have already accepted a review which causes unnecessary scrolling. A few possible solutions: Always make the logged in participant the first column of the list of participants. May not work well when someone how isn't an participant of the review is looking at the review, but this is rare and they probably aren't looking to see what files they haven't reviewed. Draw the left and right column lines with a heavier weight. For example:     ... View more

see https://community.smartbear.com/t5/Collaborator-Questions/Collaborator-13-12-131200-miss-draws-text-panes-on-Firefox/m-p/236254/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufEw1Sk0wSjU1NVZIUk1afDIzNjI1NHxTVUJTQ1JJUFRJT05TfGhL#M2825 Suggestions: 1. Properly test your systems with all supported browsers. 2. Monitor the community questions and step in when a bug is reported OR 3. Provide a proper bug reporting mechanism so the issues can be raised by users. ... View more

It would be great if this setting in the roles area could include a selection of 'all the participants with this role' we have  a role that is required.  However sometimes we need to have 2 (or more) people with this role participate.  There is no way to configure the tool to say everyone on the review with this role needs to participate.      ... View more

There are some workflows that require file versions to be in the name of the file. Collaborator has no way of recognizing this, causing extra load on our team to rename and track the files. It would be advantageous to allow some method of telling collaborator that file XXXX_01.txt is the next version of XXXX_00.txt.    perhaps this can be a setting per review, or per file, that the revision number is in the name? ... View more

The review tool allows the reviewer to compare two revisions of the document, but it would be good if we could select one of the panes to view the revision of a file that the pin was originally added to. This would allow the reviewer to compare the original issue to the current state. ... View more

During the planning/authoring phase, users can accidentally upload unwanted files. Currently users can only delete the whole change list to start over again. It would be nice to allow users to just delete specific files. ... View more

I have a number of teams developing mobile applications who are complaining about the lack of proper syntax highlighting for those languages: Swift and Kotlin. Reviews are difficult to do which makes Collaborator less useful for them.   Are there plans to add highlighting for these? I don't see previous requests for them here. ... View more

We're human.  We make mistakes.  And some of us are fastidious.  I hate seeing files which were wrongly uploaded or obsolete in my list of files to review.  Also, most of us like to be efficient.  We don't want to have to delete our whole uploaded file list just to clean up a few files.  We should be allowed to delete individual review uploads.  You have a nice tool, but it is frustrating not to be able to do so. ... View more

Could you add multiple selection of Checklist Templates for a Review Template? (Example: In Collaborator, multiple custom fields can be choosen in a review template.) ... View more

In the role template, I encountered some problems. Cases: 1- When choose No to "Allowed to modify review General Information", the role that assigned No, could not change checklist part.  2- When choose Yes to "Allowed to modify review General Information", the role can change Review Template, group, participant.   Could you separate the permissions of General Information as "Allowed to modify Checklists", "Allowed to modify Review Information" and "Allowed to modify Participant"? ... View more

When configuring GitHub or GitLab in Remote System Integration, a branch(es) to track must be entered if "master" isn't the only branch you want to track.  This controls which branches targeted for a merge as part of a pull/merge request will automatically create Collaborator reviews.   In a pretty common git workflow, release branches are created for use as hardening/stable branches in addition to the mainline branch.  If automatic Collaborator reviews based on pull/merge requests against these release/stability branches are also desired, they have to be included in the Remote System Integration list for the repo they're in.   In our use case, we create a branch "rel_v##.##" for our hardening and release candidates as we're getting close to release.  This branch is named and numbered related to the specific release number.  That means we currently need to modify the Remote System Integration for our repositories every time we approach release.   If glob or regex patterns could be specified for the Remote System Integration branches to track (at least for GitHub and GitLab), it would resolve the problem of constantly having to modify the Remote System Integration setting for a number or repos.  As long as a consistent naming convention was used for branches, those branches that should be tracked could be specified once as a pattern and then never need to be updated again. ... View more

Submitted on behalf of Avinash Ravikumar (Wipro Limited). ... View more

User experience would be greatly improved if the reviewer could associate their comment or defect to a range of lines instead of just a single line.   Additionally, if that range could also be inclusive of characters within a single line that would also be appreciated.  When comments or defects are part of a large block of code being able to accurately call out an area of code instead of just a top line of code is helpful. ... View more

Sometimes, you want a different person to look at something, or respond to a comment.  My team would like Collaborator to have a capability to tag another user.  For example, in Jira, you can use "@lastname,firstname" to tag another user.  We would like a similar capability in the comment boxes. ... View more

I guess there is a way to pull it from the API, but that is messy.  We have Participant Custom Fields that we use, and want to get the information filled in those fields (or not) per participant in the reviews.   ... View more

Would be great if the code collaborator was supplied in a Docker container with configuration options to trivialize the spin up of a new instance and the upgrade to a new server version. ... View more

This enhancement applies to Collaborator, version 9.4     In document reviews, the new pushpins are being rendered with opaque background.  The white background is covering the text under the pin. This makes it difficult to read the document when multiple pins are present. Example: => "wi??n"   You can click "Hide Pins", but this hides all of the non-active pins, but not the one you are trying to read at the time.   Please make the white background of the pushpin transparent or allow me to update the pushpin graphic file on the server to include transparent background. ... View more