github issue tracker
Am I missing the point or is there no "resolved" status in github?
开发者_运维百科having status open/closed means there is no workflow to the bugs - this is a bit of a let down.
or is it there but i'm just not seeing it?
I can emulate the states of an issue by using the labels. Label a issue as "resolved" should everybody inform, why the issue is closed.
You are right, when you say, that there is no workflow defined by github, but using the labels gives you the opportunity to work, like there is the workflow you want, even if this means, that you have to take care about the consistency yourself (e.g. closing a "blocked by other issue" with "resolved" feels wrong as long as the other one is open).
You can add as many labels as you want to an issue, for example "critical" and "bug". If there are dependencies, I suggest to add a link to the corresponding issues in the issue description.
Here's what we use in my projects:
Workflow:
- Anyone can open an issue, and assign to the issue manager.
- Issue manager will see coming issues in 'Assigned to you' list, and review the issue, assign to the right developer with or without comments; or have discussion with issue opener.
- Developer should see coming issues in 'Assigned to you' list, and review the issue, commit the code, deploy the fix on testing site, and assign the issue to issue opener.
- Issue opener should review the issue comments, verify the fix, and close it or reassign it to the developer for further fixing.
Philosophy:
- Open issues are flowing, workflow is implemented by flowing to different people/roles.
- Closed issued are dead, no code fixing or flowing should occur.
- Issue opener will verify the fix and close the issue.
精彩评论