http://dev.ortro.net is now running the launchpad trac plugin

Excellent! Thank you very much for installing the plugin.

At the moment there are no bug watches against http://dev.ortro.net in Launchpad (https://edge.launchpad.net/bugs/bugtrackers/ortro-bugs). If you know of any Launchpad bugs that need to be linked to the Ortro bug tracker, please link them so that Launchpad can start syncing with them.

I've linked the ortro project (https://bugs.launchpad.net/ortro) with http://dev.ortro.net bug tracker.
Please let me know if I've missed something.

Sorry, perhaps I should have been clearer.

At the moment, Launchpad can't just automatically import bugs from the remote bug tracker. This is functionality that we've been working on but we won't enable it until we're sure that everything else is working first (the plugins are in beta at the moment after all).

In order for Launchpad to be able to synchronise bug statuses and comments with the Ortro bug tracker, some Launchpad bugs needs to be linked to bugs on that bug tracker. See https://help.launchpad.net/Bugs/MultiProjectBugs#Bugs%20in%20external%20trackers for details on how to create these links.

Ah ok, thanks.
BTW there are some Launchpad tests bugs I may link since I'm not able to create a test bugs in the Ortro Launchpad project?
Thanks for your help and patience ;-)

There aren't any test bugs in Launchpad that you can use, however, you can create test bugs and bug watches at https://staging.launchpad.net. This is a testing environment whose database gets reset every day, so we can use it to make sure that Launchpad plays nice with the Ortro Trac.

If you create some test bugs and bug watches on https://staging.launchpad.net please let us know so that we can run the bug watch updater on the staging server.

Hi,
it seems to work correctly in staging I've created the projects test-ortro and test-ortro-2.
https://bugs.staging.launchpad.net/test-ortro-2/+bug/290100

BTW I made a mistake and I've created the test-ortro-2 also on launchpad :-(, may you delete it or do I need to open another issue ?

Thanks for help and sorry again for the mistake.

Another question, just curiosity this step is needed only for check if the plugin works correctly, is it right?
Successively in the Ortro project I may see all bugs (such an import), excuse me for the question but from the online docs seems that the only way to import trac bugs in launchpad is to use this plugin.
Thanks again :-)
Luca

Hi all,
here I am with my definitive questions ;-).
In these days I'd take a look in depth at malone and I'm looking at migrating permanently from Trac into it. Is possible to import all Trac bugs in to Malone? Is it made using the plugin?
By the way if you need further tests on the plugin does not hesitate to let me know :-D.

Thanks in advance for your help, patience and the great tool :-)

Regards,
Luca

gmb is the expert, but I'm pretty sure it's not possible to automatically migrate bugs from Trac into Launchpad. The plugin would handle this but it's not ready yet. All you can do right now is link Launchpad bugs to Trac bugs so that their statuses, etc. stay in sync.

Hi Luca, Leonard,

Sorry for not responding sooner; this was on my radar but I've been playing catch up after the Launchpad team sprint over the last two weeks. Anyway...

> Is possible to import all Trac bugs in to Malone?

Yes, and we've done it before (for Ekiga, IIRC). As Leonard says, the plugin doesn't handle this (though it will do bug imports eventually), but we have a specific bug import format that you can convert the Trac tickets into so that we can do the import on our servers. If you're interested in doing this please let me know and I'll contact you directly about it.

Hi Leonard, Graham,
yes I'm interested in import bugs into launchpad :-), please let me know the export format you need.

BTW, if in the meanwhile I may help you to test some functionalities on the plugin, does not hesitate to let me know ;-).

Thanks again for you help.

Hi Luca. Please contact me at my default address (see http://launchpad.net/~gmb) so that we can discuss the import further (you don't list a contact address so I can't contact you directly).

Cheers,

Graham