Replying to myself.
I’m using MySQL, but I guess this is not depending on database.
To see last ticket id in DB: (I have only one in this example)
mysql> select id, EffectiveId from Tickets;
| id | EffectiveId |
| 50 | 50 |
1 row in set (0.00 sec)
To update ticket number:
mysql> update Tickets set id=10000, EffectiveId=10000 where id=50;
I don’t know what is difference between ‘id’ and ‘EffectiveId’, but
updating both did not break things. Your milage may vary…
You should add one dummy ticket to system and update it’s id. Otherwise
there might be references to your ticket id somewhere else (like in
Transactions) and you’d break things.
Someone please correct if I’ve done something wrong.
And don’t blaim me if your production database gets screwed up. It’s you
typing the commands, not me.
- ToniOn Thu, 2002-01-24 at 10:39, Toni Willberg wrote:
I have finished testing RT in our environment and it’s time to start
really using it. (It rocks!)
RT test ticket numbers go around #50 at the moment in my test
environment. Our old system however is going near #5000.
I want migration to be as easy as possible for clients so I will have
same kind of format for email subject lines as previous system had.
Because of this I need to set RT so that it starts numbering from #10000
This also helps our support because you can tell if the request is found
from old or new system from the number.
So where does RT keep count which ticket number is next and how to
change it. And is it even safe to change it?
rt-users mailing list
System Specialist, Support
AtBusiness Communications Oyj, Kaapeliaukio 1, FI-00180 HELSINKI
tel. +358 9 2311 6600, fax. +358 9 2311 6601, http://www.atbusiness.com/