101

Closed

No nice way to track bug resolution reasoning

description

Most bug tracking tools let you resolve bugs "postponed", "won't fix", "by design", etc.. CodePlex's interface only lets bugs be "Active" and "Closed", so there's no clean way to do a search for "postponed" bugs without establishing some convention for bug comments and hoping everyone abides by it.
Closed Jun 6, 2013 at 5:35 PM by TomCornelius
A few months back we added Resolved state, as well as a Reason Closed field. This is a customizable field so you can add your own reasons. Take a look here:

http://blogs.msdn.com/b/codeplex/archive/2013/04/05/reason-closed-in-the-issue-tracker.aspx

comments

wrote Jul 13, 2006 at 3:23 AM

There's also not a "Resolved" state which really breaks the dev resolves the bug & test closes the bug lifecycle difficult.

But I think the broader problem here is that there's very little control offered over work item modification. There should be the ability to add fields of various sorts (free text, controlled text, drop down options only, drop down w/ user allowed extensibility, restricted to other things such as Releases, etc...). Presumably TFS supports this stuff so it's just a matter of doing the Web UI for it too :).

davedev wrote Sep 13, 2007 at 3:25 PM

I like to mark things as "Fixed" until the release and then "Closed" afterwards, given the limited set of choices now. But this presents a semantic issue for non-bug "issues" (i.e., features and tasks). The only option other than "Closed" is "Fixed", and that just doesn't make sense for features and tasks. "Complete" would be more appropriate, IMO.

This work item presents a problem for that nifty status legend on the releases page, however. So maybe it would be better for users to just be able to create their own list of statuses and choose the associated colors themselves? Then the legend could be auto-generated and will be succinct, on a per-project basis.

Pon_the_Pony wrote Oct 9, 2007 at 4:41 AM

This is because of the process template that CodePlex uses; it's a simplified Agile template.

ChrisRickard wrote Oct 20, 2009 at 5:09 AM

This is because of the process template that CodePlex uses; it's a simplified Agile template
So it's... By design? Let's mark this issue as su-
(divide by zero)

toddmcdermid wrote Apr 13, 2011 at 8:53 PM

I'd like to see (at least) three things related to this:
  • Allow work items to identify a "release they apply to" (as in "which release was this bug found in")
  • Allow work items to identify the "release that addresses them" (as in "this bug is fixed in this release", or "this feature added in this release")
  • work items that are attached to releases be shown automatically on the release page with current status.

neugrek wrote May 14, 2012 at 9:31 AM

I would also like to be able to set different states for an issue such as :

"later", "won't fix", "invalid", "by design", "duplicate", "bug" ....