We've chatted a touch on slack about this but haven't gotten resolution. How are we flagging tickets as being 4.1 blockers?
Option 1: FixVersion 4.1.0, unresolved Cons: confusing overload of FixVersion and breaks our "fixversion only set on close" paradigm Option 2: FixVersion 4.1.x, unresolved, priority BLOCKER Cons: We can't edit priority on open tickets (bug in JIRA cloud edition); non-starter Option 3: FixVersion 4.x, unresolved, severity Critical Cons: Kind of confusing; only even enumerating because we can't change priority Option 4: FixVersion 4.x, unresolved, add label "4.1_blocker" Cons: brittle, doesn't use existing "JIRA state change" logic So I see us competing between Option 1 (4.1.0, unresolved == blocker) and Option 4 (add 4.1_blocker label). I advocate for Option 1 as it's a pretty clear logical model: if a ticket has a FixVersion of some version N, the work in that ticket must be in N. If resolved, that means it's committed. If unresolved, that means it's a blocker. Any other opinions or ideas out there? Would like to tidy our tickets up as build lead and scope out remaining work for 4.1. Thanks! ~Josh
