Spira currently limits the statuses available for the requirement artifact due to the support the requirement status level automation. One request, despite infrequent, is to address how to accommodate excluding requirements at a release level or reporting on requirements in this 'required but currently unavailable' requirement status. This article addresses this requirement.
A customer recently asked for assistance requirement documentation on the Inflectra website about help on the various fields available when creating requirements in Spira.
Specifically, the columns such as Type (List of values = Design element, Epic, Feature, Need, Quality, Use Case, User Story). They needed to understand what was the intended use of each of these fields. and also the meaning of list of values under the status fields (Planned, Requested, developed etc). They wanted to see if we could provide a more detailed explanation or guide what each list of values means? They did not want to make any incorrect assumptions.