4 ms·
Author here. We have actually managed to use the same task tracking tool for the three years our project has been running: Linear. We don't do pull requests, an
by hmeh 3y ago
Author here. We have actually managed to use the same task tracking tool for the three years our project has been running: Linear. We don't do pull requests, and we don't put our work item number in our commit messages.
I can count on zero fingers the number of times I have ever wished I had this.
We do, however, keep daily work logs (each person submits them) so we have a log of everything that everyone worked on. We have Slack history, which is sometimes referred to.
I'm curious what folks find this useful for. What are the scenarios where one has to refer back to an issue from a commit?
By the way, I also have the experience of inheriting a code base where the commit messages were mostly (or just) issue numbers. Guess what I didn't inherit? The issue tracker. The commit messages were useless to me.
- pseudalopex 3y agohttps://news.ycombinator.com/item?id=38832525 https://news.ycombinator.com/item?id=38832525 https://news.ycombinator.com/item?id=38836183 https://news.ycombinator.com/item?id=38836183
- hmeh 3y agoGot it, thank you for the links. As I suspected, we just don't have these problems. Rather, we have other things that cover these needs when they arise that we have full ownership of (i.e., it won't matter if our issue tracker is replaced). Specifically those are work logs (individual daily logs), project logs (logs for larger projects which may consist of a work cell of a few people and several work items), material logs (logs for specific equipment, virtual or otherwise), work in progress notes (notes for ongoing initiatives, including checklists, etc.), etc. They are all text files contained in git repositories that are always available for reference. We can also refer to Slack conversations, but most of our conversations are done live so as to avoid hand-offs, so we must rely on recording of decisions by folks on the team. We use our work tracking system just to track work -- placeholders for conversation. My colleague wrote in more detail about what goes into our work and why issue numbers don't even enter our airspace: https://news.ycombinator.com/item?id=38836919 https://news.ycombinator.com/item?id=38836919
- AceyMan 3y agoRelying on Slack history is living dangerously. Viz., your org gets swallowed (or, is already a cog in a bigger enterprise) and Infosec/CISO starts to truncate all histories past NN days.
- hmeh 3y agoOh, we’d be fine without it. It just augments.