| Issue Type | When or Who Reports the Issue | Managed by | Guidelines for Issue Reporters |
|---|
| Epic | High level Theme is broken down to one or more Epics by the developers of each affected project and linkages are inserted with e.g. <<depends on>> semantics to explicitly link Epics for the same theme between different projects. Either it’s a new feature / improvement we will tag it as Epic to be captured in the requirements document. | Project | | Jira |
|---|
| server | ORAN Jira |
|---|
| serverId | 5ec52304-b77c-3ce7-af6a-112cb13e6008 |
|---|
| key | RSAC-1 |
|---|
|
|
| Story | Each epic is broken to estimated stories by the developers and project proceeds to assignments. If any epic is run across multiple components or modules then will add multiple stories to the epic. Stories can also be broken down into SubTask. | Project |
|
| Task | Only independent supporting requirements will be marked as task. No SubTask will be created under the task. | Project/Developer |
|
| SubTask | To be created only under the Story to split the work between different owners or components. Once all the Subtask are completed then the story will be marked as done. | Project / Developer |
|
