Default requirements and documents workflows

The requirements and requirement documents workflows define the path requirements and documents take from initial draft to implementation. Items are assigned to users who review them and indicate if changes are needed. When the work is complete, the user enters an event to move the item to the next state in the workflow. The item Status field indicates the current state and assignment.

You can use the default requirements and documents workflows out of the box or customize them to support your process. The default workflows include the following events.

Event	Use to:
Assign	Assign items to users. For example, you may want to assign a draft requirement or document to a user who can estimate the time it will take to implement.
Estimate	Estimate the time needed to work on an item. For example, you may want to enter the estimated effort to implement a requirement or complete development of the functionality described in a document.
Enter Work	Enter work you complete on an item to keep others informed about your progress.
Ready for Review	Submit an item for review after you complete a draft or make changes. For example, you may want a stakeholder to review a requirement or document to make sure it is accurate and complete.
No Changes Needed	Indicate no changes are needed after you review and accept an item.
Review Note	Add review notes to provide specific feedback. See Adding requirement and document review notes.
Ready for Approval	Submit an item for final approval when it is complete.
Approve	Approve items to indicate they are complete and ready for the next step in the process. For example, you may want to approve a requirement to indicate it will addressed in an upcoming release or approve a document to indicate it is ready for implementation.
Reject	Reject items if they are not complete or approved. For example, you may reject a requirement or document that does not include requested changes.
Needs Change	Request changes after you review an item.
Mark Suspects	Indicate related items may need to be reviewed when a requirement changes. For example, if a requirement changes, other items linked to it may also need to be updated. See Marking all dependent items as suspect. Only available in the requirements workflow.
Implemented	Close items after they are implemented.
Obsolete	Close an obsolete item if it is no longer needed. For example, you may need to mark a document obsolete if it was dropped from a release.
Re-Open	Reopen obsolete items to use them again.
Comment	Add comments to items to clarify information or add notes for other users.