Note: we will no longer be using a Confluence table to track requirements. Instead, we will be documenting requirements in JIRA and using a JIRA dashboard for review. More information here.More information here.
Guilin Use Cases
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 scorecard,m1 approval,m2/3 scorecard,m2/3 approval,m4 scorecard,m4 approval |
---|
maximumIssues | 1000 |
---|
jqlQuery | summary ~ "Guilin - Use Cases" OR description ~ "Guilin - Use Cases" |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
Guilin Requirements
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,assignee,arch review,tsc priority,scope status,t-shirt size,m1 scorecard,m1 approval,m2/3 scorecard,m2/3 approval,m4 scorecard,m4 approval |
---|
maximumIssues | 1000 |
---|
jqlQuery | summary ~ "Guilin - requirements" OR description ~ "Guilin - requirements" |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
Guilin Non-Functional Requirements
Guilin PoC