Timeline for Is there any good reason for not using the issue tracker 'properly'?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 17, 2018 at 14:06 | vote | accept | Bruce Adams | ||
| Nov 27, 2018 at 16:35 | answer | added | nvoigt | timeline score: 0 | |
| Nov 27, 2018 at 13:00 | review | Close votes | |||
| Dec 13, 2018 at 3:05 | |||||
| Nov 27, 2018 at 12:56 | comment | added | Bruce Adams | So far only occasionally as people are sticking to their own parts of the system. It feels like a time-bomb. I can't ask does this solution to this story meet or original intent or the business requirement if it isn't expressed. Compared to other issues such as the quality of their code perhaps its not a big deal. But if its a YAGNI why use the tracker at all? Just check stuff in. While I'm in rant mode why bother with comments in code while your at it or tests outside the golden path? | |
| Nov 27, 2018 at 12:43 | comment | added | Ben Cottrell | Is this process you describe actually causing any problems for you in terms of being able to get on with your job? or are you only worried about the fact that you may need to refer back to the information in future? If it's the latter it may be that the team considers this kind of documentation to be a case of 'YAGNI' | |
| Nov 27, 2018 at 12:30 | review | First posts | |||
| Nov 27, 2018 at 13:14 | |||||
| Nov 27, 2018 at 12:28 | history | asked | Bruce Adams | CC BY-SA 4.0 |