[Aardvark Bugs 0000046]: Missing Field for Accept as Marked bugs?

[Austin Group Bug Tracker <noreply@xxxxxxxxxxxxx>]

A NOTE has been added to this issue. 
====================================================================== 
http://austingroupbugs.net/view.php?id=46 
====================================================================== 
Reported By:                Don Cragun
Assigned To:                
====================================================================== 
Project:                    Aardvark Bugs
Issue ID:                   46
Category:                   Aardvark Mk III
Type:                       Omission
Severity:                   Comment
Priority:                   normal
Status:                     Resolution Proposed
Name:                       Don Cragun 
Organization:                
User Reference:              
====================================================================== 
Date Submitted:             2009-06-25 11:49 MST
Last Modified:              2009-06-26 12:14 MST
====================================================================== 
Summary:                    Missing Field for Accept as Marked bugs?
Description: 
Should there be an additional field next to the "Resolution" field on a
bug report that would be set to point to the accepted text when the
Resolution field value is "Accepted As Marked"?

Without this added field, it seems that what has been accepted might not
remain clear if there is an on-going discussion about proposed changes.

It may also be needed if the interpretation process changes text that had
been accepted as submitted.
Desired Action: 
Add a field to bug reports with a label "Accepted Text" with possible
values being "Desired Action", "Note being added by this update", or
"Note XXXXXXX" (where XXXXXXX is the sequence number of an existing note
that contains the approved text).  It should default to "Desired Action"
until another note is designated as the accepted text.

====================================================================== 

---------------------------------------------------------------------- 
 (0000115) msbrown (manager) - 2009-06-26 12:14
 http://austingroupbugs.net/view.php?id=46#c115 
---------------------------------------------------------------------- 
Hmm. My reasoning was that the default value should be the Desired Action -
that way we wouldn't have to change it for "most" cases.

There is a known Mantis defect where filtering Custom Fields breaks when
the selection has spaces, don't know if that is hitting us here. I do see
that selecting "none" for Final Accepted Text acts as if you are seaching
for the default string.