Hi Mark,
I posted a similar question recently here
http://groups.google.com/group/trac-users/browse_thread/thread/389a0a9040dcbae3#
Since I did not receive any response, I developed a solution myself.
As I do not have very much in-debt knowledge about TRAC, I started
using ticket_clone.py (http:/
Hi Mark,
My suggestion is to find the latest ticket id from the new trac
environment. And update the old database wherever the ticket id is
stored with "old_ticket_id"+"latest_ticket_id" from new environment.
This shouldn't be hard and maybe less than hundred line of SQL will do it.
mark ardi
Hi,
It would be great if someone could help me transfer tickets from a previous
trac environment to another trac environment.
My problem is the ticket id wouldn't be unique anymore and reference to it
would be broken once it tickets are transferred.
Thanks,
Mark
--
You received this messag
Yes, that will have to be a plugin. You could set something up as an
ITicketListener easily enough (depends on how smart you want it to be re:
"reassigning" from one port to another).
--Noah
> -Original Message-
> From: trac-users@googlegroups.com [mailto:trac-us...@googlegroups.com]
> On
Hi Olemis,
On Apr 27, 2010, at 6:32 PM, Olemis Lang wrote:
>> Well, but what if you have to issue some external command to extract the
>> email addresses to be inserted into the CC-field?
>
> If we are talking about maintainer e-mail : Why would you use a script ?
Well, the maintainer is actua
On Apr 26, 10:57 am, Remy Blank wrote:
> I can confirm this behavior on current trunk. Permissions must be
> all-uppercase and groups all-lowercase. The code checks for either
> .isupper() or .islower() to be true for all arguments to "permission add".
>
> The admin panel only checks that neither
