title: Bugzilla to JIRA migration: definitive approach for mapping entire bugzilla db->product->component hierachy to JIRA?
body: <p>Our organisation is now using JIRA and I'm looking to migrate a bugzilla database of about 1500 entries into it.</p>
  
  <p>I'm aware that JIRA has projects but not of divisions within this.</p>
  
  <p>My firm preference is to have one JIRA project for this bugzilla database and the bugzilla products then components all contained within this. This keeps the database self contained and doesn't expose (and therefore overcrowd) the top level project list in JIRA with my department specific bugzilla products.</p>
  
  <p>Given that there is not a straight one-to-one mapping of the hierachy in bugzilla with that in JIRA, I would consider custom fields to implement the bugzilla product and component levels in JIRA and build a custom JIRA webpage with a form that would auto-present the correct components once a product is selected (much as is the case in the bugzilla). I'm aware that JIRA is highly customisable with APIs but I don't know the detail yet - this is where I would need advice.</p>
  
  <p>I've attempted some research but this is inconclusive: <a href="http://forums.atlassian.com/message.jspa?messageID=257299050" rel="nofollow">http://forums.atlassian.com/message.jspa?messageID=257299050</a></p>
  
  <p>So in summary:</p>
  
  <ol>
  <li>Is custom fields the
  definitive/accepted way to represent
  bugzilla products and their
  components in JIRA. Any disadvantages?</li>
  <li>If so, are there examples, suggest as to how to implement this - and
  the form that auto-suggests the
  components, once a product is
  selected. </li>
  <li>If not, then what would be the alternative to using custom fields?</li>
  </ol>