Re-opening an issue (aka - Un-Resolving it)

[Marco Massenzio <ma...@mesosphere.io>]

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*

Re: Re-opening an issue (aka - Un-Resolving it)

[Marco Massenzio <ma...@mesosphere.io>]

Progress!

Gavin fixed this for us and I've verified that it works - so, now
re-opening a Resolved issue, will put it back into a "valid" Resolution:
Unresolved, and it will correctly show up in the "My Open Issues" query.

*Marco Massenzio*
*Distributed Systems Engineer*

On Thu, Aug 6, 2015 at 2:06 PM, Marco Massenzio <ma...@mesosphere.io> wrote:

> https://issues.apache.org/jira/browse/INFRA-10086
> (apparently, I'm not allowed to add Watchers on an INFRA ticket... weird!)
>
> *Marco Massenzio*
> *Distributed Systems Engineer*
>
> On Thu, Aug 6, 2015 at 2:00 PM, Marco Massenzio <ma...@mesosphere.io>
> wrote:
>
>>
>> On Wed, Aug 5, 2015 at 11:55 AM, Vinod Kone <vi...@gmail.com> wrote:
>>
>>> Ah. That's confusing.
>>
>> It gets even more confusing....
>>
>> ... even doing this, the outcome is "unsatisfactory" - apparently Jira
>> has two "classes" of "Unresolved" Resolution - the one where the issue
>> never was Resolved, and the one which is attained when following my
>> suggested "hack."
>> So, if you hit the "My Open Issues"[0] query, you *still* don't get those
>> issues, and they still show up struck through.
>>
>> If you use a hand-crafted query[1] you can see, if you add the Resolution
>> column, that they all show "Unresolved" but the genuine ones have it in
>> italic, the others in plain text: so I'm assuming Jira behind the scenes
>> uses a different metadata set than it appears externally.
>>
>> [0] JQL: `assignee = currentUser() AND resolution = Unresolved ORDER BY
>> updatedDate DESC`
>> [1] JQL: `assignee = currentUser() AND status in (Accepted, Reviewable,
>> Open, "In Progress")`
>>
>>
>>> Is there no way we can fix the schema to not do this?
>>> I'm assuming you already asked INFRA?
>>>
>>> I haven't and I don't know.  I don't really think it has anything to do
>> with our schema: this happened to me before at other places, both with
>> on-prem and on-demand Jira.
>> I'll file a ticket and see what they say, though.
>>
>> 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.
>>>
>>
>> I would suggest filing a ticket with INFRA (I don't know and don't have
>> the necessary perms to try it out, unfortunately); we must be very clear
>> that this should only apply to a *transition* (and I presume, you meant:
>> Accepted --> In Progress) otherwise our "backlog grooming" (Open to
>> Accepted) becomes too laborious.
>>
>>
>>>
>>> On Wed, Aug 5, 2015 at 11:34 AM, Marco Massenzio <ma...@mesosphere.io>
>>> 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*
>>> >
>>>
>>
>>
>

Re: Re-opening an issue (aka - Un-Resolving it)

[Marco Massenzio <ma...@mesosphere.io>]

https://issues.apache.org/jira/browse/INFRA-10086
(apparently, I'm not allowed to add Watchers on an INFRA ticket... weird!)

*Marco Massenzio*
*Distributed Systems Engineer*

On Thu, Aug 6, 2015 at 2:00 PM, Marco Massenzio <ma...@mesosphere.io> wrote:

>
> On Wed, Aug 5, 2015 at 11:55 AM, Vinod Kone <vi...@gmail.com> wrote:
>
>> Ah. That's confusing.
>
> It gets even more confusing....
>
> ... even doing this, the outcome is "unsatisfactory" - apparently Jira has
> two "classes" of "Unresolved" Resolution - the one where the issue never
> was Resolved, and the one which is attained when following my suggested
> "hack."
> So, if you hit the "My Open Issues"[0] query, you *still* don't get those
> issues, and they still show up struck through.
>
> If you use a hand-crafted query[1] you can see, if you add the Resolution
> column, that they all show "Unresolved" but the genuine ones have it in
> italic, the others in plain text: so I'm assuming Jira behind the scenes
> uses a different metadata set than it appears externally.
>
> [0] JQL: `assignee = currentUser() AND resolution = Unresolved ORDER BY
> updatedDate DESC`
> [1] JQL: `assignee = currentUser() AND status in (Accepted, Reviewable,
> Open, "In Progress")`
>
>
>> Is there no way we can fix the schema to not do this?
>> I'm assuming you already asked INFRA?
>>
>> I haven't and I don't know.  I don't really think it has anything to do
> with our schema: this happened to me before at other places, both with
> on-prem and on-demand Jira.
> I'll file a ticket and see what they say, though.
>
> 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.
>>
>
> I would suggest filing a ticket with INFRA (I don't know and don't have
> the necessary perms to try it out, unfortunately); we must be very clear
> that this should only apply to a *transition* (and I presume, you meant:
> Accepted --> In Progress) otherwise our "backlog grooming" (Open to
> Accepted) becomes too laborious.
>
>
>>
>> On Wed, Aug 5, 2015 at 11:34 AM, Marco Massenzio <ma...@mesosphere.io>
>> 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*
>> >
>>
>
>

Re: Re-opening an issue (aka - Un-Resolving it)

[Marco Massenzio <ma...@mesosphere.io>]

On Wed, Aug 5, 2015 at 11:55 AM, Vinod Kone <vi...@gmail.com> wrote:

> Ah. That's confusing.

It gets even more confusing....

... even doing this, the outcome is "unsatisfactory" - apparently Jira has
two "classes" of "Unresolved" Resolution - the one where the issue never
was Resolved, and the one which is attained when following my suggested
"hack."
So, if you hit the "My Open Issues"[0] query, you *still* don't get those
issues, and they still show up struck through.

If you use a hand-crafted query[1] you can see, if you add the Resolution
column, that they all show "Unresolved" but the genuine ones have it in
italic, the others in plain text: so I'm assuming Jira behind the scenes
uses a different metadata set than it appears externally.

[0] JQL: `assignee = currentUser() AND resolution = Unresolved ORDER BY
updatedDate DESC`
[1] JQL: `assignee = currentUser() AND status in (Accepted, Reviewable,
Open, "In Progress")`


> Is there no way we can fix the schema to not do this?
> I'm assuming you already asked INFRA?
>
> I haven't and I don't know.  I don't really think it has anything to do
with our schema: this happened to me before at other places, both with
on-prem and on-demand Jira.
I'll file a ticket and see what they say, though.

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.
>

I would suggest filing a ticket with INFRA (I don't know and don't have the
necessary perms to try it out, unfortunately); we must be very clear that
this should only apply to a *transition* (and I presume, you meant:
Accepted --> In Progress) otherwise our "backlog grooming" (Open to
Accepted) becomes too laborious.


>
> On Wed, Aug 5, 2015 at 11:34 AM, Marco Massenzio <ma...@mesosphere.io>
> 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*
> >
>

Re: Re-opening an issue (aka - Un-Resolving it)

[Vinod Kone <vi...@gmail.com>]

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 <ma...@mesosphere.io>
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*
>