Contributions
Reviews 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.307Views0likes0CommentsDisabled users should be accessible when generating reports
When running reports, the user lists show only those users that are active/enabled. In order to run a report based on a disabled user, one must re-activate the user. This introduces a security risk just to run a report. Users get disabled for many reasons (incorrect credentials, folks leave the company, etc.) and managers/supervisors still need to be able to run reports against those users. User lists in the report screens need to show ALL users, not just active users.2.1KViews2likes0CommentsTrack ANY change to a review
Currently, there seems to be no history captured for various changes to a review (Reviewers changed to Observers, template changed, links added, etc.). We would like to see an Activity Log (similar to what Jira does) that captures any change to a review (who did it and when). We use reports from SbC against our CMMI dev process to measure performance in reviews. Some reviews appear to languish for many many days and then resolve, most likely because the Reviewers/Observers have been changed. We need to be able to capture this information when reviewing the metrics of our Code and Doc Reviews.2KViews0likes1Comment