Issue 100034 - Skip issues that collide with the internal Sun bugtracker
Summary: Skip issues that collide with the internal Sun bugtracker
Status: CONFIRMED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Bugzilla (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-09 07:43 UTC by kendy
Modified: 2013-02-07 22:34 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description kendy 2009-03-09 07:43:18 UTC 
In the source code, the issues starting with 100000 mean the issues filed into 
the internal Sun bugtracking system.  In the source code it then looks like:

// #103597# prevent export of form controls which are embedded in
// mute sections

Please, can we skip to eg. 200000, or something else high enough in IssueZilla 
so that we do not have conflicts?  And please, can we do that as soon as 
possible? - we are already past the issue number 100000, so I guess there 
already are some conflicts...
Comment 1 mst.ooo 2009-03-10 11:18:14 UTC 
hi kendy,

afaik, what you say is not correct.
actually, the sun internal issues don't start at 100000; those are merely the
more recent ones :)
if you look at code that is old enough, you will find reference to sun-internal
issues <100000.

the way these are distinguished from OOo izilla issues is that the sun-internal
issues are plain numbers, while the izilla issues have the letter "i" prefixed.

(there are also issues from _another_ sun-internal bug tracker that have a
prefix letter "b"; so far i have never used that bug tracker myself)
Comment 2 stx123 2011-03-23 16:20:39 UTC 
Reset QA Contact to new default