Change History (14)

The version I'm running is available at ​https://github.com/UnwashedMeme/TicketMoverPlugin (0.2.2) which was a fork of the one here on trac-hacks a while back(it didn't work for me at the time). At this point I believe it has diverged significantly, I haven't looked at rjollos code to really compare though.

Both versions of the plugin build up a list of all the trac environments in sibling folders. I've tried to add a bit of caching to this, but that is still in process. If your webserver is creating a new python process for every request (i.e. cgi instead of fcgi) then it would need to redo that work which could cause a slowdown.

The version I'm running is available at ​https://github.com/UnwashedMeme/TicketMoverPlugin (0.2.2) which was a fork of the one here on trac-hacks a while back(it didn't work for me at the time). At this point I believe it has diverged significantly, I haven't looked at rjollos code to really compare though.

It looks like the major difference is that you've implemented an ITicketActionController. I've just tried to kill a few defects with this plugin, and have left it unchanged otherwise. Your implementation looks interesting, and I've added a link to it on the project wiki page, see ​diff.

Both versions of the plugin build up a list of all the trac environments in sibling folders. I've tried to add a bit of caching to this, but that is still in process. If your webserver is creating a new python process for every request (i.e. cgi instead of fcgi) then it would need to redo that work which could cause a slowdown.

I believe this problem is also fixed on the GitHub version. I looked at it a bit more after this came up several weeks ago.

The way I solved it (which works for me, may not for others) is to just presume sibling folders that look like trac folders (have a conf/trac.ini) are valid and don't try to open_environment until someone actually does the move.

Does the one on Github also requires TracSqlHelperScript.
I see the github says this adds "Move to and Delete Ticket". This is actually not what we want. We don't allow tickets to be Deleted (company wide policy" . For us we would prefer:

"Move to and close the ticket"

Does the version on github or the version in track-hacks allows us to move and close (not delete) ticket?

Does the one on Github also requires TracSqlHelperScript.
I see the github says this adds "Move to and Delete Ticket". This is actually not what we want. We don't allow tickets to be Deleted (company wide policy" . For us we would prefer:

"Move to and close the ticket"

Does the version on github or the version in track-hacks allows us to move and close (not delete) ticket?

Hello,
I'm having problem with the git version. Before ticket is moved it is closed as duplicate. Then its moved to a new trac. On the new trac it is also closed, the username was moved but the user doesn't exist in the new trac.

Hello,
I'm having problem with the git version. Before ticket is moved it is closed as duplicate. Then its moved to a new trac. On the new trac it is also closed, the username was moved but the user doesn't exist in the new trac.

I can see the value in that, but I don't have much time to commit to maintaining this plugin. I was just fixing up a few things since some users were running the trac-hacks version; in fact I didn't even know of the GitHub version for quite a while.

Add Comment

This ticket has been modified since you started editing. You should review the
other modifications which have been appended above,
and any conflicts shown in the preview below.
You can nevertheless proceed and submit your changes if you wish so.