1 ########################
2 Jira Ticketing Guideline
3 ########################
9 Here is the list of mandatory fields for each jira ticket:
13 description: the name of related project
15 values: aaa, bgpcep, controller, etc.
19 description: the importance of ticket
21 values: Highest (reserved for release blocker bugs), High, Medium, Low, Lowest
25 description: issue type
27 values: Bug/New Feature/Task/Improvement/Deprecate
31 description: the version that the issue was seen (it’s only applicable to bugs)
33 values: aluminum/silicon/etc.; “None” to be used for anything other than “Bug”
37 description: the version targeted for the bug fix, new feature, behavior/feature change (improvement), or deprecated feature (the first time that the feature is being disappeared), the release schedule can be found `here <https://docs.opendaylight.org/en/latest/release-process/release-schedule.html>`_
39 values: aluminum/silicon/etc.