# Tool import issue

**URL:** <https://discuss.dradis.com/t/tool-import-issue/45>\
**Category:** uncategorized\
**Created:** [August 3, 2014, 2:18am UTC](https://discuss.dradis.com/t/tool-import-issue/45 "2014-08-03T02:18:15Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![rachkor](https://yyz1.discourse-cdn.com/flex035/user_avatar/discuss.dradis.com/rachkor/32/51_2.png) [@rachkor](https://discuss.dradis.com/u/rachkor)\
**Post date:** [April 17, 2017, 7:55pm UTC](https://discuss.dradis.com/t/tool-import-issue/45/12 "2017-04-17T19:55:18Z")

</div>

Hi @Kalaratri, responding to your update thread separately here: [Upgrading Dradis-CE 3.1.0rc2 to latest via git pull](https://discuss.dradis.com/t/upgrading-dradis-ce-3-1-0rc2-to-latest-via-git-pull/449)

> [@Kalaratri](#):
>
> Re item 5. It would be great to be able to delete all issues that aren’t referenced in any node’s evidence, but this would have to wait until the end of the pen test process for all hosts. I’d much prefer a workflow that allows mass vulnerability scanning of all hosts, then work through the hosts one by one, deleting evidence that doesn’t lead to the penetration, whilst deleting the master issue if it’s not referenced by another node. This way the pentester can use the summary page to iteratively work through the most critical issues first. However there may be a more elegant workflow that I haven’t considered? How would you envisage the workflow?

You can delete the Issue from the All Issues/Summary page. In your case, Issues aren’t referenced by any Hosts (e.g. don’t have any Evidence associated with them) would have a `0` in the Affected column. As far as the overall workflow, that’s going to depend on you and your team. If a sticking point is automatically deleting Issues that are no longer referenced by any Hosts (e.g. don’t have any Evidence associated with them), you could look at scripting this instead?

---

_[View the full topic](https://discuss.dradis.com/t/tool-import-issue/45)._