Minor doc edits
overview/contributing/jira_tickets.rst
--------------------------------------
o Fixed a typo
o Added an example for jira tracking and sub-ticket creation.
Change-Id: I5def3fedb5cfdbbcf0a914dd69626e968136ff44
diff --git a/overview/contributing/jira_tickets.rst b/overview/contributing/jira_tickets.rst
index d7fd3d9..ef97b75 100644
--- a/overview/contributing/jira_tickets.rst
+++ b/overview/contributing/jira_tickets.rst
@@ -5,7 +5,16 @@
- For large or multi-part features create a containing ticket with several
sub-tickets tracking individual features or problems.
-- Descripton - include relevant information
+
+ - Primary tracking ticket.
+ - VOL-5125 - Tracking ticket for bbsim failures in jenkins vip job view.
+
+ - Sub-ticket(s)
+ - VOL-5024 - bbsim unit test job reporting status=UNSTABLE
+ - VOL-5157 - verify_bbsim_unit-test failures in history
+ - VOL-5154 - Triage test failure in periodic-voltha-unitag-subscriber-tt-test-bbsim
+
+- Description - include relevant information
- Error messages
- Reproduction step(s) for problems
@@ -14,10 +23,13 @@
- Note: Jenkins job logs will age out and disappear over time.
- To prevent this view the job history panel in jenkins UI
- - Two links are available in history, colored icon on the left and #job on the right.
+ - `View a jenkins job page <https://jenkins.opencord.org/view/vip/job/verify_bbsim_unit-test>`_
+ - Two links are available in history (lower left corner), colored icon on the left and #job on the right.
- Click the #job link to view job.
- Top right corner will contain a clickable button "Keep this build forever".
- - Just remember to clear this attribute after the jira ticket is closed.
+ - At some point in the future after a ticket has been resolved
+ remember to revisit the job log and unfreeze it (click button:
+ Do not keep this build forever)
- Assign field ``Fix Version/s:`` VOLTHA-X.Y