This page contains:
The most common use of tagging is to help visualizing the data in your project.
It doesn't really matter what risk rating your are using (CVSS, DREAD, High/Medium/Low, Impact and Probability scores, etc.) you will almost always want to be able to see a graphical representation of the issues identified so far:
To adjust the tags associated to your issues, head over to All issues on the sidebar. By default you'll land in the Summary of issues screen, where you can review and adjust the tags:
If you open any Issue description, just click Summary of issues to go back again to the table.
To adjust the tags of a given issue, select it with the checkbox in the corresponding row to trigger the actions toolbar:
Open the tags drop-down menu and select the tag to be applied:
You can select multiple rows to apply the same tag to different items.
You can also add tags to issues by using a Tags field when creating (not updating) an Issue.
#[Tags]#
![HEX]_[NAME]
!9467bd_Critical
.#[Tags]#
!9467bd_Critical
Similarly, you can add tags to issues when creating them with the REST API using the #[Tags]#
field.
Want to tag your IssueLibrary entries? Get more details on this other kind of tags in the Tag your IssueLibrary entries of the IssueLibrary guide.
Out of the box, your Dradis projects will be created with the following set of tags:
Tag | Definition |
---|---|
Critical | !9467bd_Critical |
High | !d62728_High |
Medium | !ff7f0e_Medium |
Low | !6baed6_Low |
Info | !2ca02c_Info |
If you want to have different tags (or a different number of them), just create a project template with the definitions for the tags you want.
Head over to the Project templates page in the Administration manual to learn more.
When creating your report template, you can filter issues by tag using the following filter definition:
Tag|<Name>
For example:
Tag|Critical
Learn more about filtering and filter definitions in the Filtering and sorting page of the Custom Word reports manual.
Don't want to manually tag findings? You can use the Rules Engine to create rules so that findings are automatically tagged when you upload plugin output. For more information and examples, check out the Action: Tag findings page.
Next help article: Using methodologies →