Overview
You can use the Requirements and Ideation schema to divide larger pieces of work into smaller pieces of work. This is especially helpful if multiple team members are working on a larger feature. Everybody will be able to manage their own work while still contributing to a larger, trackable body of work.
The Requirements and Ideation schema is tailored toward product managers and release train engineers. The schema allows users to create Projects, Releases, Work Items, and Ideas for product teams.
There are four record types in the Requirements Management schema.
- Project
- Within the Project record type, the following fields are available: Name, Description, TypeList, ReleaseType, Owner, Release.
- Release
- Within the Release record type, the following fields are available: Name, Description, StartDate, EndDate, ReleaseType, RecordType, Project, and Status. Subfields for Status include Ready to Ship, Under Consideration, and In Development.
- Work Item
- There are three types of work items: Epic, Feature, and Requirement. Requirements nest under Features which nest under Epics.
Within the Work Item record type, the following fields are available: State, Description, CloseBy, PlannedForRelease, Project, RecordType, ModifyBy, Owner, Tags, CloseDate, Priority, Title, ModifyDate, History, EndDate, and StartDate.
- Idea
- Ideation is the part of the Requirements schema that is used to capture user enhancement requests. Users can submit an Idea that may be converted to a Requirement. Converting an Idea into a Requirement is a great way to include small requests that fit under a planned feature.
- Within the Idea record type, the following fields are available: Title, Description, State, Category, Resolution, Owner, Tags, History, Project, and CreatedDate.