Now I'd like to create a similar one for another project, but mostly using the same approach.

Currently I did screenshots of how I configured each panel to be able to re-create it, but it's a real pain.

Something I'd like :

- duplicate shared dashboard (create a new shared dashboard with the same config)

- duplicate "not shared" dashboard

- make a "not shared" copy of a shared dashboard (so that I can copy it, tweak it, and share it with the team once it's ready)

It'd be great if there was more of a distinction between builds and releases. Right not the only way to tell the difference is via the longer indicator that sits underneath releases but not builds:

I love the idea but if I want to share and encourage among my team, I would need to share my settings so we are all monitoring the same builds.

Thanks,

Brian.

The solution so far works great. What can give an improvement is adding folders so you can organize your pipelines. In my case we got multiple pipelines for the same product. By adding folders or take the structure of VSTS you can better organize your pipelines. It make searching for the correct pipeline also easier

Otherwise the view is polluted with information for past builds for branches which were long integrated into mainline and are not existing anymore. One day timeout for short lived is way too long - we create many short lived branches.

It would be really helpful if, when selecting Jenkins builds to monitor in CatLight, the application presented the job list in a similar fashion to Jenkins.  (Broken out by views, with the ability to easily select/deselect all jobs in a view with a single click).

Right now, all jobs are presented in one long, alphabetical list, with no ability to filter or sort.  This makes it really tough to select a specific set of jobs to monitor.