[Trac-tickets] [The Trac Project] #3408: Why does 'Resolving Ticket' change the status to 'Close'?

[The Trac Project]

#3408: Why does 'Resolving Ticket' change the status to 'Close'?
---------------------------+------------------------------------------------
 Reporter:  anonymous      |       Owner:  jonas
     Type:  enhancement    |      Status:  new  
 Priority:  normal         |   Milestone:       
Component:  ticket system  |     Version:  0.9.6
 Severity:  normal         |    Keywords:       
---------------------------+------------------------------------------------
 Hello,

 I'm a new user to Trac so please bear with me if this question has been
 asked and answered in the past.

 When a developer gets to the point of resolving the ticket as fixed or
 whatever option, this changes the status of the ticket to close.  This
 makes it difficult to do regression testing as the tester doesn't know if
 a ticket was retested and closed, or is closed due to the developer's fix
 and needs to be regression tested.  There doesn't seem to be a
 distinction.  The tester seems to be left with trying to figure out which
 tickets they should go back and test.

 In Bugzilla, the ticket is closed by the tester, so they know it is truly
 closed.  I believe that changing the 'resolved' state should not change
 the status to closed, and that someone should actually go in to manually
 change the status to 'closed'.  Is there some configuration in Trac for us
 to do this by ourselves, or some other convention people use to to make
 this distinction?

-- 
Ticket URL: <http://trac.edgewall.org/ticket/3408>
The Trac Project <http://trac.edgewall.com/>