We use a single project board as the entire backlog for the team. It's a bit harder to see the whole thing and prioritize than, say, Jira, but the direct link between working issue and backlog is nice.
We've got four columns:
To Do, Doing, Blocked, and Done. Done means merged and shipped.
Labels are for estimations (1-2,3,5,8) and for category of thing (Front-end, Back-end, Pipeline, operational, etc) so we can get a sense of how much of each we've got lined up each sprint. I have milestones set up for major parts of the work but they don't really do me much good because you can't filter your project board by Milestones (yet? - Feature request!).
The automation pieces are not really working that well. Still manually closing issues for the most part.
Easier things: connecting development directly to your project board. Collaboration in issues that is immediately reflected in where you're tracking the work. Collaborating in issues is still better than other platforms and the ability to use Markdown, link to other issues, PRs, etc still makes this a great tool for the team to track in place.
Harder things: a filtered view of a larger more complex backlog that is useful for longer-run planning such as release planning and project planning. For those broader looks you really need to move stories into another format for discussion to keep things clean, or try to filter your Issues view to look at how things lay out (at which point you lose the prioritization piece of the project).
Being able to sort Issues by project priority order would resolve a lot of these issues pretty quickly and make it a more fully-featured, connected tool. I guess I could prioritize by emoji count... Being able to see projects by Milestone or label, and in priority order in a more "consumable" format is really the biggest thing missing.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
We use a single project board as the entire backlog for the team. It's a bit harder to see the whole thing and prioritize than, say, Jira, but the direct link between working issue and backlog is nice.
We've got four columns:
To Do, Doing, Blocked, and Done. Done means merged and shipped.
Labels are for estimations (1-2,3,5,8) and for category of thing (Front-end, Back-end, Pipeline, operational, etc) so we can get a sense of how much of each we've got lined up each sprint. I have milestones set up for major parts of the work but they don't really do me much good because you can't filter your project board by Milestones (yet? - Feature request!).
The automation pieces are not really working that well. Still manually closing issues for the most part.
Easier things: connecting development directly to your project board. Collaboration in issues that is immediately reflected in where you're tracking the work. Collaborating in issues is still better than other platforms and the ability to use Markdown, link to other issues, PRs, etc still makes this a great tool for the team to track in place.
Harder things: a filtered view of a larger more complex backlog that is useful for longer-run planning such as release planning and project planning. For those broader looks you really need to move stories into another format for discussion to keep things clean, or try to filter your Issues view to look at how things lay out (at which point you lose the prioritization piece of the project).
Being able to sort Issues by project priority order would resolve a lot of these issues pretty quickly and make it a more fully-featured, connected tool. I guess I could prioritize by emoji count... Being able to see projects by Milestone or label, and in priority order in a more "consumable" format is really the biggest thing missing.