Timeline for Using bug-tracking / issue-tracking software to discuss design questions, new tools etc
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 9, 2011 at 15:57 | vote | accept | Ozan | ||
| Dec 5, 2011 at 6:54 | comment | added | mattnz | It has a slightly different workflow, but is essentailly the same as any other item - Issues are raised, triaged, fixed, tested and finally accepted. From memory a Risk does not go through the QA cycle like a software change does. | |
| Dec 5, 2011 at 6:03 | comment | added | Ozan | Interesting, classifying it as risk seems to counter the possibility that a "decision" issue is just left open. Is the workflow of such a risk category issue straightforward or is there any aspect in particular one should consider? | |
| Dec 4, 2011 at 22:38 | history | answered | mattnz | CC BY-SA 3.0 |