Open fwenzel opened 11 years ago
Yeah. The idea is that the "full backlog" is uncurated straight from bugzilla. Project manager types would then curate the bugs that are ready to sprint on into the sprint-ready list for their project. Then when the team is ready to create a new sprint, all the bugs from those ready lists for all the projects in the team would be there for creating the sprint.
It's not really an advertized feature, but you can move a bug directly into the ready backlog, or a sprint using the "s=<sprint_slug>"
tag in the whiteboard. If sprint_slug
exists as a sprint on the project, the bug will be added to said sprint, if the sprint doesn't exist it'll be in the ready backlog.
For many teams the full backlog is HUGE, and having it on the page when creating a sprint was so unwieldy as to be worthless. So it was decided that having some separation and a level of abstraction was preferable.
The workflow was though to be something like the following:
If you need more flexibility I'm sure we can work something out.
Thank you, the s=...
works very well for my purposes. We can either WONTFIX this bug, or keep it as a feature request for the "full backlog" page, up to you.
I do think it'd be worth it to find a way to add a bug directly to a sprint from the full backlog page as a shortcut. Like you found, you could easily be looking at that page and want to just move a bug into the current sprint. I think we should keep this as a feature request for that.
When adding a new bug to a sprint, I first need to find the "full backlog" page, add it to the sprint ready list there, then find the bugs list for the sprint in question and add it to the actual sprint, there.
I think we can cut one step out of this, perhaps by allowing to switch from "ready backlog" to "full backlog" on the sprint bugs edit page (http://scrumbu.gs/t/deveco/2012.2/bugs/).