Modify ↓
Opened 15 years ago
Last modified 7 months ago
#7786 new defect
Removing existing ticket priorities makes tickets unrenderable in queries
| Reported by: | jtiai | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-stable-1.6.x |
| Component: | admin/web | Version: | 0.11-stable |
| Severity: | major | Keywords: | verify |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
If you remove all priorities that exist in tickets and add new ones (with different name) you can't query existing tickets anymore since many pieces of code relies on existing "priority" values in enum table.
There should be warning that operation causes bad side-effects, preferably there should be option to automatically upgrade tickets to new values.
Attachments (0)
Change History (7)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Plus the web admin also allows you to Modify Priority when you click on a priority value.
comment:3 by , 15 years ago
| Keywords: | verify added |
|---|---|
| Milestone: | → 0.11.4 |
No feedback - still worth trying to reproduce.
comment:4 by , 9 years ago
| Milestone: | next-minor-0.12.x → next-stable-1.0.x |
|---|
comment:5 by , 7 years ago
| Milestone: | next-stable-1.0.x → next-stable-1.2.x |
|---|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.
comment:6 by , 4 years ago
| Milestone: | next-stable-1.2.x → next-stable-1.4.x |
|---|
Note:
See TracTickets
for help on using tickets.
Did you consider using the following TracAdmin command, instead of removing/adding?
That should have taken care of the update of tickets.
Also, can you be a bit more specific about: