You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Justin Mclean <ju...@classsoftware.com> on 2012/06/17 03:18:10 UTC

Duplicate JIRA issues

Hi,

Just taking a look at the JIRA import and it looks like we have some duplicates:

An example (and there are others):
https://issues.apache.org/jira/browse/FLEX-11749
https://issues.apache.org/jira/browse/FLEX-12223

However the total number of issues seems roughly right, so it doesn't look like all issue have been imported twice. Is it possible that some have been doubled up and we are missing other issues?

For comparison:

Apache Flex:

	Open	3244	
   10%
	In Progress	2	
 
	Reopened	1	
 
	Resolved	695	
   2%
	Closed	29181	
   88%


Adobe Flex:
	Open	642	
   2%
	In Progress	4	
 
	Reopened	59	
 
	Resolved	105	
 
	Closed	26074	
   88%
	Community	2264	
   8%
	New	61	
 
	Internal Review	35	
 
	Under Investigation	8	
 
	Waiting on Info	77	
 
	Committed	2	
 
	Deferred	158	
   1%
	Patch Submitted	8	
 
	Patch Submission Review	2	
 
	Rejected	126	
 



Thanks,
Justin


Re: Duplicate JIRA issues

Posted by Carol Frampton <cf...@adobe.com>.

On 6/17/12 1 :45AM, "Alex Harui" <ah...@adobe.com> wrote:

>I think if we missed migration of something important we'll find out
>shortly
>and can manually re-enter in Apache Flex JIRA.  We need to ask folks to
>re-enter any Adobe bug created after Jan 30 2012, which is when I made the
>dump file.

I never bothered to turn off my daily summary email of new Adobe Flex so I
know there are some bugs that should be brought over.  There are typical 1
to 3 new bugs per day.

Carol


Re: Duplicate JIRA issues

Posted by Alex Harui <ah...@adobe.com>.


On 6/16/12 10:32 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

> Hi,
> 
>> Definitely possible that there are duplicates and some missing.
> I don't think it a huge issue as long as we have most of them (and I believe
> we do) it's all good.
> 
>>  Plus, it was a custom migration tool I wrote and it crapped out a few times
>> and had to be restarted.
> Do we have list of what issues were in the import or what issue were not
> included (which would be the shorter list I assume)? Is there as easy way to
> check what has and hasn't been copied across?
I didn't build a list of what was not allowed to be migrated.  I don't know
of any easy way of verifying other than writing a SOAP app to walk both
databases.  It is not a priority for me at this time.
> 
> I assume at this point it good use the Apache JIRA and mostly ignore the old
> Adobe bug base.
I think if we missed migration of something important we'll find out shortly
and can manually re-enter in Apache Flex JIRA.  We need to ask folks to
re-enter any Adobe bug created after Jan 30 2012, which is when I made the
dump file.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Re: Duplicate JIRA issues

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> Definitely possible that there are duplicates and some missing.  
I don't think it a huge issue as long as we have most of them (and I believe we do) it's all good.

>  Plus, it was a custom migration tool I wrote and it crapped out a few times and had to be restarted.
Do we have list of what issues were in the import or what issue were not included (which would be the shorter list I assume)? Is there as easy way to check what has and hasn't been copied across?

I assume at this point it good use the Apache JIRA and mostly ignore the old Adobe bug base.

Thanks,
Justin

Re: Duplicate JIRA issues

Posted by Alex Harui <ah...@adobe.com>.


On 6/16/12 6:18 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

Hi,

Just taking a look at the JIRA import and it looks like we have some duplicates:

An example (and there are others):
https://issues.apache.org/jira/browse/FLEX-11749
https://issues.apache.org/jira/browse/FLEX-12223


Definitely possible that there are duplicates and some missing.  For sure, there were some bugs that couldn’t be migrated for certain legal or content reasons.  Plus, it was a custom migration tool I wrote and it crapped out a few times and had to be restarted.

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui