Edgewall Software

Opened 14 years ago

Closed 14 years ago

#7713 closed enhancement (invalid)

Ticket life cycle should include a Resolved status between new/assigned and closed

Reported by: amit.tendulkar@… Owned by:
Priority: normal Milestone:
Component: ticket system Version:
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:


I am using Trac version 0.11.1. This enhancement request is related to the status field of the enhancement. Currently a ticket can have new —> assigned —> closed —> reopened (and back to assigned) as a status work flow. Whenever a tester files a defect he adds a ticket with the status as new. The developer gets this defect assigned to himself and works on it. Whenever the fixing is done he directly closes the defect (marks the status as closed). In practice the tester should get a chance to verify the fix before the defect reaches a logical closure. So I propose to have an additional status as Resolved. The developer will change the status to resolved whenever (s)he has actually fixed the defect. The tester can then easily get the list of to-be-verified defects based on the 'Resolved' status and can close them out after verification (by marking the status as closed).

Attachments (0)

Change History (1)

comment:1 by Noah Kantrowitz, 14 years ago

Keywords: ticket status resolved removed
Resolution: invalid
Status: newclosed
Version: 0.11.1

Read TracWorkflow.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.