www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marco Massenzio (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-10086) Unresolving issues does not clear the Resolution field
Date Thu, 06 Aug 2015 21:06:04 GMT
Marco Massenzio created INFRA-10086:
---------------------------------------

             Summary: Unresolving issues does not clear the Resolution field
                 Key: INFRA-10086
                 URL: https://issues.apache.org/jira/browse/INFRA-10086
             Project: Infrastructure
          Issue Type: Bug
            Reporter: Marco Massenzio


We assume this is a Jira bug, but is it possible that there is some configuration / workaround
for the problem?

{quote}
> 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.)
>
{quote}


Unfortunately,  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")`




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message