References
CPS-2055
-
Getting issue details...
STATUS
<optional other relevant references, Jiras, Confluence pages, external links>
Assumptions<optional>
<optional, assumptions are like decision made up front ie. everyone agrees on the answer but they are important to mention>
| # | Assumption | Notes |
|---|---|---|
| 1 | Decisions will be agreed with stakeholders |
Issues & Decisions
| # | Issue | Notes | Decision |
|---|---|---|---|
| Standard bug reporting template | Minimal information needed for all bug tickets | ||
| Bug reporting guidelines | A wiki page showing how to write a good bug report | ||
| Acceptance criteria for bug tickets | |||
| NCMP-specific information | |||
| Handling of sensitive information such as sharing of artifacts such as logs | Need to protect IPR of commercial contributors | ||
| 2 | Do we need a analysis template? | is convention for (new) developers to guide them | Luke Gleeson (Unlicensed) and Toine Siebelink agreed we do to have consistent study pages |
| 3 | This is a very important (blocking issue) |
<Note. use green for closed issues, yellow for important ones if needed>
Any Other Header
< we do not want to dictate the remainder of an analysis it will depend on the type of user story at hand>