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).
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:
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs