3 ms·
My point is that the overhead of writing up a ticket description becomes a significant fraction of the total work involved. Write a commit message if you want
by bpodgursky 7y ago
My point is that the overhead of writing up a ticket description becomes a significant fraction of the total work involved. Write a commit message if you want it documented.
There's no need for a ticket for small tasks, unless you are being evaluated on number of tickets closed (which is a separate problem)
- greenyoda 7y agoOn the other hand, being forced to write something up gives you extra time to think about what you're about to do. I've had many experiences when I was about to commit what I thought was a trivial change to the code, but then suddenly realized that it was going to break something.
- ropman76 7y agoLike all things in life it depends on the team and workflow. I have my PM’s make tickets because many times I am in the middle of a different feature or bug and don’t want to have to have the mental load of remembering what the issue was. Secondly I work with very solid PM’s who document the ticket very well and it saves me time having to reproducing the issue. My team does have a lot of tickets but we make it work for us and our process flow.