Opened 19 years ago
Closed 13 years ago
#1199 closed enhancement (worksforme)
Ability to unaccept tickets
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.11.7 |
| Severity: | normal | Keywords: | |
| Cc: | mmitar@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
It would be nice if accepted tickets could be "unaccepted".
Also, if an previously accepted ticket is assigned to a different user, the ticket system should no longer mark that ticket as accepted.
Attachments (0)
Change History (5)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
| Owner: | removed |
|---|
You can do that by using the action reassign to: and clear that field.
(doing it now…)
comment:3 by , 19 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
The status reverted to new.
So I guess this ticket can be closed
(if what was initially requested was an explicit unaccepted status, I think that this should be done in a custom workflow, once that's supported, not in the default workflow)
comment:4 by , 13 years ago
| Cc: | added |
|---|---|
| Resolution: | worksforme |
| Status: | closed → reopened |
| Version: | 0.7.1 → 0.11.7 |
Does not work if restrict_owner is set to true. You cannot clear the field in that case.
comment:5 by , 13 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | reopened → closed |
Please don't reoppen 5-year old tickets, and open a new one instead. In this case, I'm not sure it's warranted, as this can be achieved easily with a custom workflow. So "worksforme" is definitely appropriate.
I second the motion.