blob: d7fd3d916f0f9e228236533c70d11fc2fb87bc3b [file] [log] [blame]
Joey Armstrong3980d702023-08-23 10:57:18 -04001Jira tickets for code changes
2=============================
3
4Please open a `jira ticket <https://jira.opencord.org/projects/VOL>`_ describing the issue/feature.
5
6- For large or multi-part features create a containing ticket with several
7 sub-tickets tracking individual features or problems.
8- Descripton - include relevant information
9
10 - Error messages
11 - Reproduction step(s) for problems
12 - Web URLs, links to jenkins job logs are very helpful.
13
14 - Note: Jenkins job logs will age out and disappear over time.
15 - To prevent this view the job history panel in jenkins UI
16
17 - Two links are available in history, colored icon on the left and #job on the right.
18 - Click the #job link to view job.
19 - Top right corner will contain a clickable button "Keep this build forever".
20 - Just remember to clear this attribute after the jira ticket is closed.
21
22- Assign field ``Fix Version/s:`` VOLTHA-X.Y
23
24 - This will enables searching for feature by release.
25 - Leveraged during release to document fixes and enhancements in release notes.
26- While viewing a jira ticket, the 'More' navigation pulldown menu at the top
27 is useful for creating sub tickets or creating links to external resources.
28
29See Also
30--------
31
32- https://jira.opencord.org
33- `jira :: VOLTHA <https://jira.opencord.org/projects/VOL/issues/VOL-4470?filter=allopenissuse>`_