Per-Reviewer Independent Checklist Mechanism
Each assigned reviewer shall be able to fill an individual checklist instance associated with the same review record. The filled checklist responses shall be independently stored, uniquely identifiable to the respective reviewer and preserved as objective evidence supporting compliance with DO-178C review objectives.Have ability to add closed reviews to projects
We've been using Collaborator for many years and have reviews that closed well before the project feature was added. I would be very useful to be able to add these retrospectively to projects without having to re-open the review. This is because to then re-close the review you have to get all the Reviewers to send it to completed and, apart from the hassle, in many cases the reviewers no longer work for the company.107Views0likes1CommentPreviously Accepted Comment
Since comment acceptance clears on file upload, it would be helpful to know which comments were previously accepted. So you would have 3 icons, unaccepted, previously accepted and accepted. This way it makes accepting a comment useful and not just cleared on a new upload. This way if you didn't change anything related to that comment you know you don't have to go back and look at it or get someone to reaccept.40Views0likes0CommentsReviews of a submodule change need to show file change in review
When using a git submodule with a pull request / merge request mechanism enforced (i.e., Bitbucket), when the developer changes the submodule and there is no other change in the parent repository other than pointing to the new merge commit, Collaborator shows no files in the review. Commits are properly listed, but there are no changes to actually review, which is incorrect. Bitbucket, for example, lists the "pointer file" that holds the submodule commit reference. It would be extremely helpful to have Collaborator show this difference as well.346Views0likes0CommentsAdd a "Ready for Approval" state to defects
It would be helpful if there was a third state to indicate that a defect has been resolved, but still needs to be "approved" (marked Fixed) by the author of the defect. Currently a defect only appears as "Open" or "Fixed" in the Defect Log. It is difficult to tell which defects have been resolved without looking through the comments, or having someone tell you to look at a specific defect. When there are a lot of defects in the Defect Log, a third state to filter on would make it easy to identify those defects that need to be marked Fixed. Maybe this could also be shown with a different color bug, instead of red or green.1KViews0likes2CommentsAdd multiple pull requests to "Remote System Links"
Currently a pull request from Bitbucket can only be added to the Remote System Links section automatically when the pull request is created, and there isn't a way to add a link to a pull request manually. Is it possible to make an update that allows linking of more than one pull request in a single review? In the case of making small related changes across multiple repositories, it would be very beneficial to be able to include more than one pull request in a single review, to allow those changes to be reviewed as a set.1.6KViews0likes4Comments"Confirm to cancel comment" dialog wording is awkward and unclear.
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.2KViews1like2Comments