| Table of Contents |
|---|
References
Jira Legacy server
...
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
...
4733707d-
...
2057-
...
3a0f-
...
ae5e-
...
4fd8aff50176 key CPS-2055
...
- Mozilla guide to bug writing: https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html
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? | |
| 2 | Standard Bug Reporting Template | The minimal information needed for all bug tickets | |
| 3 | NCMP Bug Reports | There is specific information needed for reproducing NCMP bugs, e.g. number of CM-handles | |
| 4 | Performance Bug Reports | Performance issues are much more difficult to reproduce than functional issues | |
| 5 | Handling of sensitive information such as logs and heap dumps | Need to protect IPR of commercial contributors | |
| 6 | 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 |
<Note. use green for closed issues, yellow for important ones if needed>
...