introducing jira ticketing guideline

Signed-off-by: Navid G <navid.ghazisaidi@verizon.com>
Change-Id: I92c0824f8d2aaec4717434a8fcbb77004d6dadce

diff --git a/docs/contributor-guides/index.rst b/docs/contributor-guides/index.rst
index e28d6913ea191280d2e1882c38f4395952cdf203..6c736bf1844d5b6ae9f6569c4adbda11123fa959 100644 (file)
--- a/docs/contributor-guides/index.rst
+++ b/docs/contributor-guides/index.rst
@@ -9,6 +9,7 @@ Contributor Guides
 
    newcomers-guide
    coding-guidelines/index
+   jira-ticketing-guide
    copyright
 
 * :doc:`LFN Gerrit Guide <lfdocs:gerrit>`

diff --git a/docs/contributor-guides/jira-ticketing-guide.rst b/docs/contributor-guides/jira-ticketing-guide.rst
new file mode 100644 (file)
index 0000000..7920cdd
--- /dev/null
+++ b/docs/contributor-guides/jira-ticketing-guide.rst
@@ -0,0 +1,39 @@
+########################
+Jira Ticketing Guideline
+########################
+
+
+Mandatory Fields
+================
+
+Here is the list of mandatory fields for each jira ticket:
+
+**Project:**
+
+description: the name of related project
+
+values: aaa, bgpcep, controller, etc.
+
+**Priority:**
+
+description: the importance of ticket
+
+values: Highest (reserved for release blocker bugs), High, Medium, Low, Lowest
+
+**Type:**
+
+description: issue type
+
+values: Bug/New Feature/Task/Improvement/Deprecate
+
+**affectedVersion:**
+
+description: the version that the issue was seen (it’s only applicable to bugs)
+
+values: aluminum/silicon/etc.; “None” to be used for anything other than “Bug”
+
+**fixVersion:**
+
+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>`_
+
+values: aluminum/silicon/etc.