Open thisandagain opened 9 years ago
Yes, if you need a good laugh, here is my current workflow for assigning designers. Can't imagine what @simonwex's process looks like!
Step 1: Figure out and visually group which ticktes are p1 vs p2 Step 2: Remember who was assigned to previous tickets that are being carried through to this sprint Step 3: Assign p1s Step 4: Assign p2s Step 5: Remember which ones I'm 'quality' on Step 6: Bang my head on the table =)
we now have the code in a place where we could implement a thing, if we had a design to go from.
For resourcing and even for understanding what an individual is attached to, it would be great to have a people-centric view of planning issues for a specific sprint (milestone).
For example, I currently don't have a simple way to see all issues in a sprint that @cassiemc is attached to (both P1 and P2). We could do this by parsing the RACI section, or even more simply, by extracting all
@mentions
from each issuebody
.