Jani Tiainen wrote:
> I would rather fix all my (open) tickets to have some sensible value.
> Many people still uses 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
Remy Blank kirjoitti:
> Jani Tiainen wrote:
>> So, how I could recover my missing 700 tickets...
>
> 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
Jani Tiainen wrote:
> So, how I could recover my missing 700 tickets...
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 s
Jani Tiainen kirjoitti:
> I had very old trac db that contained priorities and severities. I
> decided to upgrade it a bit newer version, removed all severities and
> made priorities more sane.
So, how I could recover my missing 700 tickets...
One resolution that I would like to use is to push
