[jbosstools-issues] [JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151333#comment-13151333 ] 

Nick Boldt commented on JBIDE-21363:
------------------------------------

PR updated again today. Max says:

{quote}
for me the thing we need before going live is:
1) actually implement the version mapping lambdas for the products we know
2) figure out what to do with bz's we don't have mapped - i.e. have the build fail with a report with enough info so someone can go and add the mapping - but without stopping doing imports of those that does work
3) at least know we can within decent time implement a way to update fields if version mappings changes
4) check that we can avoid having to query all bugzillas and jiras at every run (i.e. have the script only query things that changed since last run)
{quote}

> create bugzilla importer for JIRA
> ---------------------------------
>
>                 Key: JBIDE-21363
>                 URL: https://issues.jboss.org/browse/JBIDE-21363
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> Looking to create some kind of jiralint-like scraper tool to facilitate JIRA-like scrum/dashboard tracking of upstream projects, not located in JBoss JIRA.
> This scraper would:
> * [REQ1] find all bugzillas associated with a particular query, such as  https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT (18 issues)
> * [REQ2] generate a JIRA for each one found (no dupes should be created)
> * [REQ3] scrape several fields: product, component, version, target milestone, comment #0, summary, bug #
> * [REQ4] need a mapping table for Eclipse-prod:proj:component:fixversion-or-target-milestone to Neon milestone so we can set default values for affectsversion/fixversion/targetrelease in created JIRAs. 
> * [REQ5] need a mapping table for Eclipse-prod:proj:component to ERT:component, eg., WTP:JSDT -> javascript
> * [REQ6] created test issues here: https://issues.stage.jboss.org/browse/ERT
> * [REQ7] run as a Jenkins job every 3 hours
> Generated JIRA example:
> {code}
> title: (scraped from summary) Support for smart Import Mechanism [Eclipse BZ 464535] 
> issue link: (scraped from BZ ID#) https://bugs.eclipse.org/464535
> description: (scraped from BZ comment #0)
> affectsversion: (scraped from BZ version 1.6.0)
> fixversion: (scraped from BZ target milestone ---)
> component: (scraped from product:component = m2e:ui)
> labels: RHT, ERT
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)