ONAP Bugs, Epics, Stories, and Tasks are tracked in the JIRA system at https://jira.onap.org/.
Note that you do not need to log into JIRA to view issues; however, your view will be read-only and not all fields described below will be visible.
If you intend to file or update information in JIRA, you will need a Linux Foundation identity to access the ONAP JIRA account. Read this page for instructions.
If you are not familiar with JIRA, you can refer to JIRA User's Guide provided by Atlassian: https://confluence.atlassian.com/JIRA064/JIRA-user-s-guide-720416011.html
ONAP defines a number of different projects for the various subsystems.
To view the current set of JIRA projects, go to the Projects menu, select View All Projects from the pull down menu to see what is currently defined.
Below is the current set of Projects; however, note that additional JIRA projects may be added as needs dictate, so this list is not static
There are many ways to view issues in JIRA. The description here is one way.
Go to Issues menu, select Search for issues
This will bring up the following screen. You will be able to select which Project(s) you want to search, what issue Types (Bug, Epic, Story, Task), what Status and so on. The "More" menu allows you to select additional fields to search on to further narrow down your search.
An alternative to searching, you can use predefined filters provided by JIRA as shown below:
To report a bug against ONAP, select Create (please note that screen display may vary slightly depending from where in JIRA you create the bug)
The following Create Issue screen will be displayed.
New feature or enhancement proposals are submitted via JIRA using the Story issue type.
Before you submit your idea, first check to see if something similar already exists in the backlog. If not, go ahead and create a Story.
Searching for a Story in the backlog works the same way as searching for a Bug (Viewing Issues in JIRA), just select Issue Type Story instead of Bug along with the Project(s) of interest in the Search menu. Alternative, you can go to the Backlog board for a particular project, such as shown below for MSO.
To submit your feature or enhancement proposal, go to the Backlog board of the applicable Project and select Create Issue. In our example, we are using MSO.
This will present the following menu, go to the far right and click on the three dots.
This will bring up the Create Issue screen as show below.
There are generally 5 Jira issue types used within ONAP; the 5th one, Sub-task, can only created from within a Story.
Example of screen shot for creating a JIRA issue via the Create menu option.
5. Sub-task
The ONAP projects have all aligned on the following workflow, which is a slightly modified Atlassian Classic workflow.
From Status | Transition |
| To Status | |
a | Open | Start Progress | → | In Progress |
b | Open | Deliver | → | Delivered |
c | Open | Close | → | Closed |
d | In Progress | Stop Progress | → | Open |
e | In Progress | Submit | → | Submitted |
f | In Progress | Close | → | Closed |
g | Submitted | Deliver | → | Delivered |
h | Submitted | In-Progress | → | In Progress |
i | Delivered | Close | → | Closed |
j | Delivered | Reopen | → | Reopened |
k | Reopened | Close | → | Closed |
l | Reopened | Start Progress | → | In-Progress |
m | Reopened | Deliver | → | Delivered |
n | Closed | Reopen | → | Reopened |
The Resolution field is very important because combined with Status field, it conveys critical information to the community about the general disposition of the Jira issue.
The below list is the set of Resolution options provided as defaults by Jira. Some projects have added to this list, such as Not A Bug, PTLs can request LF to add more Resolution options to their project; however, recommendation is that one set be defined that is used across all projects - this is a work in progress still.
Use this guideline to setup the mandatory "JIRA Priority" field. Note that the PTL has jurisdiction over this criteria and may thus requalifies the priority.
Otherwise, it makes it very difficult: