DependencyTrack
Export functionality to download metrics from components and vulnerabilities
Current Behavior
The data we have in Dependency Track is used to share component, vulnerability and other information to our stakeholders. Since we need a way to transfer this information to other users we have the use case for us to be able to download some of this information in a readable way and share it with our colleagues.
Proposed Behavior
If we were able to implement a way to download information to a spreadsheet from certain UIs in the application that would satisfy our use case. I personally implemented a feature like this and am hopeful to include it into dependency track itself, pending input from the team. Please see an image of how it looks below and note the download button above the table in the UI.
Checklist
- [X] I have read and understand the contributing guidelines
- [X] I have checked the existing issues for whether this enhancement was already requested
Thanks for the suggestion. I would prefer to use the Export plugin in Bootstrap Table. It would save screen real estate and supports multiple formats.
Demo: https://examples.bootstrap-table.com/#extensions/export.html API Docs: https://bootstrap-table.com/docs/extensions/export/
Hey @stevespringett , thank you for your comment, my apologies for taking this long to get back with you but I've been working on implementing the export plugin into my local instance of dependency track. I wanted to get back with some of my findings and have a dialogue with you on what features this enhancement would need to be included into the application.
One of the first things I've found with the export plugin is that it only exports the data that is shown on the table. For example, if you are looking at component with 100 items and have the table view amount set to 50, the export plugin only downloads the 50 items that are shown on the table. We were hoping that we'd be able to pull all of the data for a given component instead of just what we can see in the table.
Secondly, how the plugin is shown in the Dependency Track UI is causing some issues that I've opened a ticket against the repo that maintains the plugin. l'm not sure if this is something on my end that just needs configuration or if it's something the export plugin will need to handle. I'm waiting for their response now.
Please let me know if there's any clarifications that I can make, thanks.
Thanks @nvcastelli
One of the first things I've found with the export plugin is that it only exports the data that is shown on the table.
True, that is the default behavior which can be changed. I believe if the exportDataType is set to all, then the plugin should paginate through all results. https://bootstrap-table.com/docs/extensions/export/#exportdatatype
Thank you, Steve. I was able to implement that functionality.
As it stands, using bootstrap-table-export, I am able to download files from the table. However I am still working through my second point I mentioned above where I am seeing issues in the UI. I am hoping to receive a response from the plugin team but am looking into it on my end as well. I hope to be able to contribute this to the project soon pending approval.
Thanks for the suggestion. I would prefer to use the Export plugin in Bootstrap Table. It would save screen real estate and supports multiple formats.
Demo: https://examples.bootstrap-table.com/#extensions/export.html API Docs: https://bootstrap-table.com/docs/extensions/export/
Hey @stevespringett are you completely married to the bootstrap plugin you referenced? We are having a slow response times, so not sure if we can try an alternative package? Also, this could be a candidate for the "experimental" process we talked about-- iron out the kinks and document accordingly for the rest of the folks.
@melba-lopez I would like the plugin architecture to be used which would simply make the export part of bootstrap table, however, if we want to create a custom plugin to do this, thats fine with me.