Hacker News new | ask | show | jobs
by donatj 519 days ago
This seems... unneeded bloat? I guess there are some obsessive organizers out there, but a markdown checklist of steps - potentially with links to other tickets seems like all you need.

If you're going to improve something improve code review! Let me comment on and suggest diffs to lines the author did not touch. Like half the time I am reviewing code it is "Hey, you refactored this but you missed a usage in this other file" and right now I have to manually give them file and line number manually and hope for the best.
1 comments
replete 518 days ago
A lot of this will seem trivial if you haven't used Github for an organization's management of issues. This also lets you start off with a markdown checklist, and convert items to sub-issues.
link
paulryanrogers 518 days ago
> This also lets you start off with a markdown checklist, and convert items to sub-issues.

Wasn't that already possible with Tasklists? We did it using "- [ ] description", then clicking the covert-to-issue hover option.

link
donatj 518 days ago
See, but I do. For almost a decade, we have used it as-is for tickets and bug tracking, and it's never been a problem. I just don't see the use case for sub issues.
link