Ah. That's confusing. Is there no way we can fix the schema to not do this? I'm assuming you already asked INFRA?
On a side note, is it possible to make the "Shepherd" field mandatory when a task transitions from Accepted --> Assigned? I think this will force users to find shepherds before they start working on an issue. Will also help shepherds guide what issues we want new contributors to focus on. On Wed, Aug 5, 2015 at 11:34 AM, Marco Massenzio <[email protected]> wrote: > Dear all: > > When re-opening an issue (for whatever reason) moving it from its Resolved > state (to either Open or In progress) Jira will *not* update the > "Resolution" field back to "Unresolved". > > This means that (a) you now have a confusing "Open but Resolution: Fixed" > issue and (b) the issue link/display (eg, MESOS-1234) will appear with a > misleading strike-through in Sprint and Kanban Boards. > > The solution is rather simple, albeit fiendishly unintuitive: > > 1) Resolve (again) the issue; > 2) in the resolve dialog that pops up, choose "Unresolved" for its > Resolution field; > 3) move it back to whatever state makes sense (Open, In Progress, etc.) > > Hope this helps! > > *Marco Massenzio* > *Distributed Systems Engineer* >
