trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Atanu Mishra <>
Subject RE: Import of LP bugs into JIRA
Date Thu, 06 Aug 2015 22:33:31 GMT
Hi Suresh,

I signed up to help in getting some order into the imported JIRAs, but have
not gotten to it yet. Please give me a couple of days to make an initial
dent in this, then will go from there. Does this seem reasonable?

Atanu Mishra
Esgyn Corporation
Milpitas, CA
m: +1.408.219.9765      e:

-----Original Message-----
From: Chen, Alice (SeaQuest) []
Sent: Thursday, August 6, 2015 3:23 PM
Subject: RE: Import of LP bugs into JIRA

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 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
and check the "Unresolved by Assignee" section.


-----Original Message-----
From: Suresh Subbiah []
Sent: Thursday, August 06, 2015 2:57 PM
Subject: Import of LP bugs into JIRA


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 corresponds to JIRA-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 ( 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

Thanks for your advice

View raw message