Hi everyone, it’s Samuel with another poll! 
This one is something I’m curious about from the perspective of the sprint planning manager role.
Regarding the “Ready to pull in” and “Not ready to pull in” labels (implemented as release versions in Jira):
- Yes
- No
If you find them useful, I’m curious why.
Personally as sprint planning manager I do not find them useful: the semantics are not clear, they’re a weak signal of ticket readiness anyway, they get outdated very quickly, and they’re ignored (if we want a ticket in the sprint, we put a ticket in the sprint, regardless of a little planning label).
Also, in looking for the source again, I only find this reference: “Ensure tickets ready to be pulled into a sprint are properly marked and ranked higher in the backlog.” in the handbook. And this is a hard thing to do; probably better to simply leave all this up to the relevant epic owners, who know better the budgets, ticket scopes, scheduling, etc.
I’d propose deleting these “Not ready to pull in” and “Ready to pull in” labels if no-one finds them useful.
Ticket: BB-3149