Edgewall Software
Modify ↓

Ticket #563 (closed defect: duplicate)

Opened 8 years ago

Last modified 7 years ago

Status field/lifecycle for tickets

Reported by: dobes Owned by: jonas
Priority: normal Milestone:
Component: ticket system Version: 0.7.1
Severity: normal Keywords:
Cc:
Release Notes:
API Changes:

Description

In order to integrate trac better with our workflow, it would be nice if tickets could indicate their position in a life cycle. Currently, it seems like tickets are either new, assigned, or resolved.

I'd like to have additional states:

  • Implemented/fixed (e.g. still needs testing by another party)
  • Passed Tests (customer can be notified, or whatever)
  • Failed Tests (should be reviewed and fixed again)

This way you can make reports that select tickets the need testing, and you can see the status of a ticket.

Attachments

Change History

comment:1 Changed 8 years ago by Jilles <ojilles@…>

Looks a bit like #301... But more general.

comment:2 Changed 7 years ago by cmlenz

  • Resolution set to duplicate
  • Status changed from new to closed

Superseded by #869. Go there for further comments.

View ↑

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
to The owner will be changed from jonas. Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

Attachments ↑
 
Note: See TracTickets for help on using tickets.