Working on this in the background. The latest broker version has some improvements to the UI already.

I'm replacing tags with explicit branches, and the ability to nominate which is the "main development branch" for each pacticipant. The index page will then be able to show the pact/result for the main branches.

This makes sense to me.

I've been considering allowing the configuration of "important tags" to allow the UI to show the tags that are most relevant to the user. eg. you might want to see the verifications for "master" and "prod". This sounds like a good use case for it.

Something that one of our Pactflow customers did is create their own dashboard using the "matrix" Pact build badges, that allow you to specify the consumer tag and the provider tag, and see the status of the pact verification between them. That might be a useful intermediate state.

Here's the link to the badge docs. https://docs.pact.io/pact_broker/advanced_topics/provider_verification_badges#with-consumer-and-provider-tags

Something that's also on the back burner (there's an issue in canny for it) is to duplicate the tags functionality with "branches" and "environments". This would make it easier for the UI to know which verifications were important to show.

This would be a huge improvement for us.

We're just rolling Pact out across teams in our company, and this isn't something they all understand right away. Since all of our development happens in feature branches, 95% of the time, the "dashboard" view is just showing verification results for a feature branch.

Because of this, it's almost meaningless to us