This page contains:
Report template properties give you control over the content of your report template in a different way. Define fields needed to validate your project, filter the contents of your project, or even change the title of your document.
Quickly edit the Title of your template. The Template file field will always display the original name of the document at the time you uploaded it.
Define the custom document properties in your Word report so that Validate Export can check your document for any missing properties on export.
For the example below, we're going to define the three fields in this simple report template:
These fields are defined within Dradis as
To define these custom document properties:
dradis.enddateas shown below:
Define the fields within your Issues so that Validate Project knows what to look for on export and can warn you about any missing or incorrect fields in your project. And, this allows Dradis to automatically validate each Issue as you save it.
For the example below, we're going to define the Issue fields for this simple template:
Ratingfield. This is especially important if your report template's Issue are being sorted/filtered by specific values. For example, if you're sorting your Issues by
Rating, this setup will flag any values that don't belong (e.g. Critical).
Define the different fields that each instance of Evidence in your project should contain. This lets the Project Validator know what to look for on export and can warn you about any missing or incorrect fields in your project. And, this allows Dradis to automatically validate each piece of Evidence as you save it.
For the example below, we're going to define the Evidence fields for this simple template:
Statusfield. This is especially important if your report template's Evidence content controls are being sorted/filtered by specific values. For example, if you're filtering your Evidence by
Status, this setup will flag any values that don't belong (e.g. Pending).
The Issue and Evidence fields are used to validate your project during the export process. Plus, they automatically check every Issue and instance of Evidence in your project as you save them.
Now when you validate your project on export, you'll know immediately whether your project's Issue and Evidence fields match the fields that your report template is looking for.
When your project is associated to a report template with Issue and Evidence fields defined, Dradis will automatically validate each Issue and each instance of Evidence in your project as you save it.
When you create your project, make sure that it is associated with the correct report template that has the Issue and Evidence fields defined.
Then, every time you update an Issue or piece of Evidence, Dradis will check to make sure that the fields match the expected fields you set in the report template properties.
In this example, Dradis is expecting a
Rating field with a value of High, Medium, or Low within the Issue. We misspelled the field value and entered Hgih so we will see the following error message:
In this next example, we have an instance of Evidence that contains a
Status field but has an invalid value. Dradis is expecting a
Status field value of Open or Closed but this piece of Evidence has the Status set to Pending so we will see the following error message:
Sort the Issues in your project by any of the numeric Issue Fields you've defined. When selected, this property will sort the Issues in your report by this field, highest to lowest, before exporting them.
Next help article: Note templates →