Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Introduction

Beginning with the Frankfurt release, we will document requirements in JIRA.

Process

  1. Navigate to  REQ-1 - Getting issue details... STATUS
  2. Select More==>Clone++
  3. Follow the steps in the dialog to clone the issue in the same project (i.e., REQ).  Make sure that the checkbox, "copy issues in epic" is selected.
  4. Modify the "epic name" and "description" fields for your requirement.
  5. Set the "Fix Version" field to the release name for which the use case is intended (e.g., "Frankfurt")
  6. Set the "Assignee" field to the requirement owner.
  7. If the requirement has other requirements or tasks as dependencies, add the requirements in the "Issues in Epic" field.
  8. Add a link to the JIRA issue in the appropriate column of the table on the release requirements page.
  9. Once the TSC has determined the priority for the requirement (0 - 4), set the value in the "TSC Priority" field.
  10. The template includes three sub-tasks for the TSC approvals at MS1, MS3, and MS4.  As these approvals are achieved, add a comment to the sub-task with a link to the approval documentation and mark the task as done.


Requirements Milestones Summary

Unable to render Jira chart macro due to an execution error.


  • No labels