DCM Dashboards
DCM Dashboards help you get an overview of all open issues (from the lint rules and code quality checks) and metric violations across all your projects, and how those numbers change over time.
Getting Started
To learn how to integrate DCM Dashboards into your workflow, check out this guide.
It covers all necessary steps from creating your first project to uploading your metadata to DCM Dashboards.
Managing Access
By default, only the account owner has access to the DCM Teams Console and, therefore, to the account's Dashboards.
To invite developers to view Dashboards, refer to this page. And to invite non-developer users to view Dashboards or manage other users' access, refer to this page.
Privacy
When uploading data to DCM Dashboards, only the issues metadata (by default, the rule/metric names and the number of issues/violations) will be uploaded, meaning that tool does not upload your source code, file names or projects structure.
We understand that this might make the experience a bit worse, but you will still have an opportunity to run all DCM commands locally and the goal for the Dashboards is to provide you with an overview (and for that, collecting your code is not necessary).
When using the --with-details flag, the tool starts to include additional metadata (e.g. the issue description, severity, estimated effort, etc.) and if an issue's description references, for example, a variable or class name in your code, that information will be uploaded to the Dashboards.
If you consider this information too sensitive to upload, do not pass the --with-details flag. Additionally, you can always preview the collected metadata before uploading it by passing the --preview-upload flag.