Allow Admins to close reviews
Bringing back an old thread - I'd like anyone with Admin privileges to be able to move a review to Completed. We've had several instances where someone has left the company, or is on extended leave, and their roles is required to move a review to completed. On solution is to shuffle roles - while that will allow a review to close, it's "not right". If the author of a document is out sick - yes I can assign the author role to someone else - but now you are fudging the review records in order to get the closure. Later when an auditor comes in we have to give a song and dance as to why the roles in the review don't represent the actual roles the staff members have. We shouldn't need to alter the records to move things forward. The review is more than a record of defects - it's a record of who did what, and we shouldn't need to compromise that to get around a technical glitch.
Clone Checklists
Currently Collaborator supports Cloning a review template. A similar feature would be very helpful for Checklists. Often time you want to modify/add/remove some questions from an existing checklist, and you have to copy the checklist manually line by line, making changes where needed. Have a '[clone]' option similar to the one for Review Templates would be helpful.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.
Log all activities of users and admins in Collaborator
In a Large enterprise there will be multiple admins. To track who has done what, Admin should be able to get the log of all users activities. Like, Disabling and Enabling review templates, Disabling and enabling users or adding users etc. In simple terms a log should be generated for every activity happens in Collaborator through all the ways. ex: GUI, API, Collab client, Thirdpart clients, Commands etc.
Ability to have custom field dependencies/relationships based on selection of a dependant field
Ability to have custom field dependencies/relationships based on the "Item" selection of a another custom field. i.e. Custom Field "Phase" --> Item selected = "Requirements" Custom Field "Type of Defect" dependent on the Custom Field "Phase" selection of "Requirements" --> Items available to select "Spelling error", "No Requirements defined", "Does not meet requirements" In the above example, the Custom Field "Type of Defect" would display different Items depending on what was chosen from the "Phase" Custom Field. thanks