Introduction
Beginning with the Frankfurt release, we will follow these practices:
- All release requirements must be associated with a use case
- All use cases and requirements will be documented in the Release Requirements JIRA project
Why are we doing this? Attaching release requirements to use cases helps the TSC to ensure that all work on the release is aligned with ONAP objectives, and tracking the use cases and requirements in JIRA enables managers and the community to quickly see the status of each use case, as well as the requirements associated with each use case.
Process
Use Case
- Navigate to REQ-1 - Getting issue details... STATUS
- Select More==>Clone++
- Follow the steps to clone the issue. Make sure that "copy issues in epic" is selected.
- Modify the "epic name" and "description" fields for your use case.
- Set the "Fix Version" field to the release name for which the use case is intended (e.g., "Frankfurt")
- Add associated requirements (see below) if they're known (this can be done later).
- Save
- Add a link to the use case JIRA issue in the appropriate column of the use case table on the release requirements page.
Requirements
New
- Locate the Use Case epic with which the new requirement is associated in the Release Requirements JIRA project.
- Find the "Issues in Epic" field and click the '+' sign. This will pop up a new issue form.
- Set the "issue type" for the requirement as "new feature".
- Set the "Fix Version" field to the release name for which the use case is intended (e.g., "Frankfurt")
- Save the issue.
- Repeat until all associated requirements have been added.