Hi Suresh and Alice, Yes, this task is on my list of things to do. And I haven't gotten to it yet. But it sounds like Suresh is taking care of the issues he's working on :-)
Dave On Thu, Aug 6, 2015 at 3:22 PM, Chen, Alice (SeaQuest) <[email protected]> wrote: > Hello Suresh, > > I thought Dave and/or Steve was coordinating the cleanup of the imported > bugs. Anyways, the LP to JIRA import process did not allow us to import > the conversation history. If you want the conversation history you will > have to copy and paste from LaunchPad. The import process also did not > allow a Status or Resolution to be assigned to the imported issues. You > can look at https://issues.apache.org/jira/browse/TRAFODION-43 to see the > CSV file used for the import process. This file contains the mapping for > Status and Resolution for all the LaunchPad issues. You can use this CSV > file to fix the status for the issues you own. If you just want to see how > many unresolved issues you own you can go to > https://issues.apache.org/jira/browse/TRAFODION/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel > and check the "Unresolved by Assignee" section. > > Cheers, > Alice > > -----Original Message----- > From: Suresh Subbiah [mailto:[email protected]] > Sent: Thursday, August 06, 2015 2:57 PM > To: [email protected] > Subject: Import of LP bugs into JIRA > > Hi, > > I am going through my JIRA issues and noticed two discrepancies. > > 1) For an imported issue in JIRA we do not have the conversation history > that is present in LaunchPad. Please consider this example > https://bugs.launchpad.net/trafodion/+bug/1329361 corresponds to JIRA-375 > https://issues.apache.org/jira/browse/TRAFODION-375 > The extensive conversation history in the LaunchPad bug is not captured in > JIRA. I could find a way to cut and paste for the issues I own, but am > wondering if should attempt a more systematic approach. My apologies if > this problem has already been discussed. > > 2) For imported issues in JIRA, LaunchPad status of FixCommitted or > FixReleased maps to Status = OPEN and Resolution = Unresolved in JIRA > Previous example or https://bugs.launchpad.net/trafodion/+bug/1426605 ( > https://issues.apache.org/jira/browse/TRAFODION-1027) can be used as > instances of this discrepancy. > > The net result is that we have far too many open issues in JIRA than in > reality. I am wondering if we should each take care of the issues assigned > to us and then somehow divide the common pool or if this can be achieved > programmatically or with some kind of script? > > Not being aware of how many actual issues I have assigned to me is > somewhat unsettling. > > Thanks for your advice > Suresh >
