Flyover Reports for Crucible Question

Tini Good
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 3, 2015

Is there a way to configure Flyover Reports for Crucible so that it doesn't use the same (erroneous in our case) assumption as Atlassian that the goal is 100% reviews of every changeset? 

We'd go nuts trying to peer review every changeset (using Subversion).  Our goal is peer review of a diff of the first changeset against the final changeset of a branch before merge to trunk. 

Alternatively, only require review of every changeset made against the trunk, (as that would include any branch merges).

1 answer

1 accepted

0 votes
Answer accepted
Alexander Taler
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 3, 2015

Your suggested alternative of trunk review would work well with Flyover Reports. You could create a report which just covers the trunk, but you would have to create reviews for all merge commits, and only after merge has been committed.

You can add multiple changesets to a single review in Crucible, and could theoretically add all the commits from one branch. This works fairly well for Crucible, but unfortunately there's one issue which is highlighed by Flyover Reports:

https://jira.atlassian.com/browse/CRUC-6363

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events