5 ms·
GitHub does all of this very well. "Ticket" => GitHub issue "status" => current column on GitHub project. This includes "is the ticket ready for me", "am I do
by TimTheTinker 6y ago
GitHub does all of this very well.
"Ticket" => GitHub issue
"status" => current column on GitHub project. This includes "is the ticket ready for me", "am I done with a ticket", "is the ticket ready for QA", "did QA reject the ticket", etc. -- each of these is a column in the project board.
"who is working on it" => assignee(s)
- ogre_codes 6y agoI haven't used GitHub for this, so I'll take your word for it. The fact that there are a lot of ways to track these issues well was exactly my point. You need some way of tracking these things. I've used JIRA and it got the job done. I've also used other tools which worked as well. What doesn't scale is not tracking issues.
- threeseed 6y agoIt only does it well if you have extremely basic needs. It doesn't support custom attributes, workflows, approval hierarchies, statuses etc. There is a reason ZenHub had to be invented after all.
- TimTheTinker 6y agoCustom attributes: use labels Workflows: set up one or more project boards and PR merge restrictions Approval hierarchies: where the above is inadequate, use CODEOWNERS files. Statuses: use project columns and labels