Different workflow for CI driven changes
At the moment, the UI seems designed to be very manual and interactive, ie, a change happens, and it requires someone to acknowledge the change or deal with it. This is good, and will definitely be useful for some environments.
However, I suggest that there be another workflow added, based around CI driven changes. In this mode, the "acknowledge change" functionality would be hidden, and all changes happen via the integration with a CI tool.
Once a database is built via "SQL CI Build", it is automatically detected as an accepted change, and as it progresses through environments (via "SQL CI Sync" or Octopus Deploy) it is automatically accepted.
This would leave the dashboard as something that is mainly used as an information radiator, rather than an often used interactive tool.
Chad Hattabaugh commented
It would be nice if the same workflow could be used for changes made via SSC. If I check something in from Development, Acknowledge the change as being checked in (maybe Changeset id and user who committed? )
Without an automated workflow around SQLCI, SQLRelease, and SSC this tool just becomes "additional work" as part of a release with little value to the business