...
References
Jira Legacy server ONAP System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a4733707d-557c2057-3c0c3a0f-b515ae5e-579789cceedb4fd8aff50176 key CPS-2055 - Mozilla guide to bug writing: https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html
- Link to new CPS Bug Reporting page: Bug Reporting Guidelines for CPS
Assumptions
<optional, assumptions are like decision made up front ie. everyone agrees on the answer but they are important to mention>
...
| Issue | Notes | Decision | |
|---|---|---|---|
| 1 | Acceptance criteria for bug tickets | What should we do if a bug not reproducible? > Reject | CPS team will decide whether to accept bug ticket based on whether enough information has been provided to be able to reproduce/resolve the issue. |
| 2 | Standard Bug Reporting Template | Minimal information useful for all bug tickets | Create a wiki page containing bug report template, as a guideline for writing bug report. Fields are optional, depending on context. Daniel Hanrahan will create this page. |
| 3 | Handling of sensitive information such as logs and heap dumps | Need to protect IPR of commercial contributors | Will provide guidelines for what info can/cannot be shared in open source. For E///, Client-specific internal Jira ticket can be used to share artifacts, where applicable. |
| 4 | Bug reporting guidelines | A wiki page showing how to write a good bug report. Note there are many existing ones such as: https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html | Can be done as part of #2 (bug report template) |
...
- Full description of the issue
- Affected version(s)
- Expected behaviour (what is the requirement?)
- Actual behaviour
- Impact - this is important for setting priority
- Steps to reproduce - ideally a Minimal reproducible example
- (Optional) Attached artifacts: Screenshots, Logs, Test data, etc.
- Environment
- Attached the corresponding IDUN Jira
There has been much confusion about the number of CM-handles the bug reporters are testing with. In many tickets, phrases such as "80k deployment" is used, but in some cases this was 6k CM-handles, and 20k for others!
...
- Environment, including available resources in the deployment (memory and CPU cores, number of application instances)
- What is the load on the system (how many concurrent operations, etc.)?
- Measured CPU and memory consumption
- For Out Of Memory Errors (OOMEs): Attached heap dump - I think this should be a requirement moving forward
...
Client-reported bugs
Links to internal Jira tickets, Jenkins pipelines, should be provided where applicable. Logs etc. could be shared securely herethere.
Acceptance Criteria for Bugs
...