...
Use Case Title | Title of the Use Case |
Actors (and System Components) | The list of Actors and System Components that participate in the Use Case |
Description | Short overview of the Use Case |
Points of Contact | Authors and maintainers of the Use Case. Use Case Lead, Key Use Case members and code contributors. |
Preconditions | A list of conditions that are assumed to be true before the Use Case is invoked Includes description of Information Consumed |
Triggers / Begins when | Describes the trigger for beginning the Use Case |
Steps / Flows (success) | Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes) Interaction diagrams may be included or referenced |
Post-conditions | The expected results of the execution of the Use Case Includes description of Information Produced |
Alternate / Exception Paths | Description of any exceptions or special process that could occur during Use Case |
Related Use Cases | List of the Use Cases referenced by this Use Case |
Assumptions | Describes any assumptions that are made for this use case |
Tools / References / Artifacts | List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability. List of any associated diagrams or modelling artifacts associated with the Use Case |
...
Epic Status
1000 Jira Legacy server System Jira columns key,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 approval,m2 approval,m3 approval,m4 approval,rc0 approval,status maximumIssues
OR 20 jqlQuery key = REQ-446 serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Test Status
Jira Legacy server System Jira columns key,summary,assignee,creator,integration test plan status,integration test time to complete,integration test status maximumIssues 1000 jqlQuery "Epic Link" = REQ-446 and project = REQ serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...