But, this killed all SQL based reports. How to fix that? This shouldn't
happen in first place of course...
--
Jani Tiainen
"Tein sein mihin näillä lahjoilla pystyin.
Tein sen, en yhtään enempää." - Martti Servo & Napander
So, how I could recover my missing 700 tickets...
One resolution that I would like to use is to push mass update to all
tickets that don't have entry in my "priority" field to use default
value "normal" with attached text "Automatic update due new priority
classes" (or something like that) but how I can run such a mass update?
I suppose you haven't actually lost your tickets, have you? At least on
my test install, if I set e.g. a priority to a value not present in the
defined priorities, the ticket still appears on the custom query page.
You can't set a filter on the priority for "invalid" values, though, as
the drop-down is populated only with defined priorities.
You were mentioning SQL-based reports. If those give you trouble, you'll
have no choice but to fix the SQL so that it works with the new values.
-- Remy
You're right.
> You were mentioning SQL-based reports. If those give you trouble, you'll
> have no choice but to fix the SQL so that it works with the new values.
I would rather fix all my (open) tickets to have some sensible value.
Many people still uses SQL reports .
Of course I would be more than happy to have SQL reports disabled and
forward people always to query page from sql reports.
Ah, I wasn't suggesting dropping SQL reports altogether. You would have
to edit the SQL for the reports that stopped working and fix it so that
it works with the new values.
Unfortunately, batch ticket editing is not yet integrated into Trac,
although there has been some work on that (there's an experimental
branch in the sandbox, but I have no idea of its status).
-- Remy