Testtrack RM Requirement Fields

TestTrack RM Requirement Fields

Use these worksheets as a guide for customizing fields on the Add/Edit/View Requirement windows and requirement workflow event fields in TestTrack RM.

Requirement types

TestTrack RM includes the following requirement types by default:

• Business Requirement
• Functional Requirement
• Non-Functional Requirement

To add or change the requirement types, choose Tools > Administration > Requirement Types.

Add/Edit Requirement window

General fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Summary / Yes
Date Entered / <not set>
current date> / <current date>
Entered By / Yes / <not set>
<current user>
(all users) / <current user>
Importance / <not set>
Must
Should
May / <not set>
Description

Notes:

• To rename fields, choose Tools > Administration > Rename Field Labels and select Requirements as the Type.
• To change required fields and default values, choose Tools > Administration > Required Fields & Default Values and select Requirements as the Type. Select General Fields from the field list. By default, all requirement types use the same setting, but you can configure different settings for each type.
• To add or change the Type field values, choose Tools > Configure List Values > Requirement Importance Values.
• To add field relationships for pop-up menu fields, choose Tools > Administration > Field Relationships. Select Requirements as the Type.

Detail tab fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Owners* / <not set>
<current user>
(all users) / <not set>
Origin* / <not set>
Feature Request
Defect
Competitive Analysis / <not set>
Source* / <not set>
<current user>
(all users) / <not set>
Risk* / <not set>
High
Medium
Low / <not set>
Difficulty* / <not set>
High
Medium
Low / <not set>
Product* / <not set> / <not set>
Release* / <not set>
Current
Next
Future / <not set>

Notes:

• Custom fields are marked with an asterisk (*). To add or change custom fields and values, choose Tools > Administration > Custom Fields and select Requirements as the Type. The Product field values are shared with the requirement document Product field and TestTrack Pro defect Product field. The Release field values are shared with the requirement document Release field.
• To change required fields and default values, choose Tools > Administration > Required Fields & Default Values and select Requirements as the Type. Select Custom Fieldsfrom the field list. By default, all requirement types use the same setting, but you can configure different settings for each requirement type.
• To add field relationships for pop-up menu fields, choose Tools > Administration > Field Relationships. Select Requirements as the Type.

Workflow event fields

• To rename event fields, choose Tools > Administration > Workflow and select Requirements as the Type. Click the Events tab, select the event that contains the fields you want to rename, and click Edit.
• Custom fields are marked with an asterisk (*). To add or change custom fields, choose Tools > Administration > Custom Fields and select Requirements as the Type. Click the Events tab, select the event, and click Edit. To rename an existing field, click the Fields tab. To add or remove fields, click the Custom tab and click Custom Fields.
• To change required fields and default values, choose Tools > Administration > Required Fields & Default Values and selectRequirements as the Type. Select <event> Fieldsfrom the field list. For example, select Assign Fields to change settings for the Assign event.
• To add field relationships for pop-up menu fields, choose Tools > Administration > Field Relationships and select Requirements as the Type.
• Files can be attached to events. To add or remove an Attachments tab, choose Tools > Administration > Workflow and select Requirements as the Type. Click the Events tab, select an event, and click Edit. Select or clear the Files can be attached to this event option.

Assign event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Assign By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes
Assign To / <not set>
<current user>
(all users) / <not set>
Due Date* / <not set>
<current date> / <not set>

Estimate event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Estimate By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes
Estimated Time
Completion Date* / <not set>
<current date> / <not set>

Note: The Estimated Time field is displayed because time tracking is enabled for the event. To change time tracking options, choose Tools > Administration > Workflow and select Requirements as the Type. Select the Estimate event and click Edit. Time tracking options are available on the Details tab.

Enter Work event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Enter Work By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes
Actual Effort
Remaining Time* / Yes

Note: The Actual Effort field is displayed because time tracking is enabled for the event. To change time tracking options, choose Tools > Administration > Workflow and select Requirements as the Type. Select the Enter Work event and click Edit. Time tracking options are available on the Details tab.

Ready for Review event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Ready for Review By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes
Due Date* / <not set>
<current date> / <not set>

No Changes Needed event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
No Changes Needed By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes

Review Note event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Review Note By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes
Note Type* / <not set>
No Comments
Change Suggested
Approve
Reject
Question
General Note / <not set>

Note: To change the Note Type field values, choose Tools > Configure List Values > Requirement Custom Event Values > Note Type.These values are shared with the Note Type field in the requirement document Review Note event.

Ready for Approval event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Ready for Approval By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes
Due Date* / <not set>
<current date> / <not set>

Approve event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Approve By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes

Reject event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Rejected By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes

Needs Change event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Needs Change By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes

Mark Suspects event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Marked By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes
Mark dependent items as suspect / <checked>
<unchecked> / <checked>

Note:TheMark dependent items as suspect option is displayed because Include option to mark dependent items as suspect is selected for the event. To change this option, choose Tools > Administration > Workflow and select Requirements as the Type. Select the Mark Suspects event, click Edit, and click the Detailtab.

Implemented event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Implemented By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes

Obsolete event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Obsolete By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes
Reason* / <not set>
Design Changed
Feature Dropped
Invalid
Other / <not set>

Note: To change the list values for the Reason field, choose Tools > Configure List Values > Requirement Custom Event Values > Obsolete Reason.These values are sharedwith the Reason field in the requirement document Obsolete event.

Re-Open event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Re-Open By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes

Comment event fields

Field / Rename / Required / Values / Additional Values / Default Value / Related Field / Relationship (Parent or Child)
Comment By / Yes / <not set>
<current user>
(all users) / <current user>
Date / Yes / <not set>
<current date/time> / <current date/time>
Notes

TestTrack RMRequirement Fields1