I'm puzzled by something in the Created vs. Resolved report. And it has to do with uncertainty around which specific metric is being represented by "Resolved."
In my specific example, my Created vs. Resolved report shows 18 issues "Resolved." I have 13 with a Status of "Closed" and 5 with a Status of "Resolved." I also have 5 with a Resolution of "Resolved."
Would I be correct in assuming that in the Created vs. Resolved report, the "Resolved" number is the sum of the Status of "Closed" and "Resolved" (13 + 5 = 18), and has nothing to do with the Resolution field?
If that assumption is not correct, then my question becomes: what specific metrics make up the "Resolved" number in the Created vs. Resolved report?
Beaten to it! The middle sentence is the one that really helps people understand how JIRA thinks - status has nothing to do with the resolution (ok, logically, it does, and most JIRA installs will handle it as you expect. But you have to get the workflow right. There's no logic in JIRA code that ties resolution to status. At all. Nothing)
I still want to bin the concept of resolution=resolved, and go with "meta status" (create a group of status in a workflow and enable the admin to say "if it's in that group, it's done"). But heck, I'm still waiting for priority schemes and decent delegation of admin roles.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs