On Wed, Nov 07, 2007 at 12:59:05PM -0500, James Henstridge wrote:

Hi Bryce,

I've completed the demo import of Inkscape bug reports. You can view the results here:

https://bugs.demo.launchpad.net/inkscape/

Hi James,

We've had some time to review the demo site and poke around a bit. In general it looks really good, however some people spotted a few things that look incorrect.

Thanks, Bryce

Bugs appear reported in future ------------------------------ On this bug (and possibly others), the dates associated with buliabyak-users are in the future (2011, 2012).

E.g. https://bugs.demo.launchpad.net/inkscape/+bug/157587

Category mapped to milestones ----------------------------- For Inkscape, we used the SF Category to tag bugs by type. These appear to have been mapped to milestones by the converter, however. Instead, can you have the Categories just mapped into LP tags?

Missing Attachments ------------------- In a number of cases the bug attachments didn't come through correctly. Here is one example:

SF.net http://sourceforge.net/tracker/index.php?func=detail&aid=1816893&gro... Launchpad https://bugs.demo.launchpad.net/inkscape/+bug/159964

Fix Committed State ------------------- It appears that the 'Pending' state in SF was mapped to 'Fix Committed' in launchpad. We never really understood what 'Pending' meant, but what we used it for in Inkscape is more like the "Incomplete" state, so it should be mapped to that.

Inconsistant Bug Stats ---------------------- The bug numbers in Launchpad show:

Open 1144 Critical 43 New 809 Unassigned 826 All bugs ever reported 5536

while on sf we have:

# Bugs : (801 open / 3,727 total) # Patches : (27 open / 828 total) # Feature Requests : (1,022 open / 2,183 total)

We're curious how the numbers are arrived at, and what causes the stats discrepancies?

(I'm guessing it's just due to terminology differences between SF and LP status, but am uncertain how they get mapped through.)

Map priority 5 bugs to New/Undecided status ------------------------------------------- By default, SourceForge sets the priority of newly reported bugs to 5. We found this irritating since it interferes with triaging the priorities of bugs. So as a hack-around we decided that priority 5 actually means "unprioritized".

Can you set the script to map priority-5 bugs to be New/Undecided?