Consider CI Dashboard integration to SMELT
http://dashboard.qam.suse.de/blocked contains information about tests status for individual updates.
That requires a lot of cross-checking between smelt and dashboard which impacts usability.
For example the dashboard doesn't contain information about priority and deadlines. Having them included in he dashboard would effectively duplicate items from SMELT.
Perhaps it would be worth considering integrating the dashboard to the SMELT directly and decommission http://dashboard.qam.suse.de.
Updated by okurz about 2 years ago
- Priority changed from Normal to Low
- Target version set to future
ok, nice idea. For now on the back burner in "future" to collect thoughts and to refine.
Do you or someone else know what was the original motivation to develop the dashboard outside the context of smelt? If it was just done as a proof-of-concept then I would say that succeeded and we can consider the integration into smelt. But maybe there are other good additional reasons why it made sense or still makes sense to keep it separated.