Modify ↓
Opened 20 years ago
Closed 20 years ago
#3110 closed enhancement (wontfix)
New option for resolve as - postponed
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.9.5 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
It would be very handy to be able to resolve tickets as postponed. Sometimes a ticket needs to be entered into the system, but either depends on another ticket (would be a nice feature, I guess like an auto-postponed) or just can't be done yet, and it would be handy to filter out these tickets in the reports on open tickets.
Attachments (0)
Change History (2)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
While you could freely add new resolutions using the WorkFlow branch (scheduled for inclusion in Trac milestone:0.11), why not use the milestone field for this?
You could either clear the milestone value in order to "post-pone", or use a specific "Post-poned" or the mythical "1.0" milestone for that :)
Note:
See TracTickets
for help on using tickets.
Just to be clear, I have added the postponed value to the enum table for my system, my suggestion is that this be included by default for new Trac installations.