[jbosstools-issues] [JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA
Nick Boldt (JIRA)
issues at jboss.org
Thu Dec 17 16:01:00 EST 2015
[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt reassigned JBIDE-21363:
----------------------------------
Assignee: Nick Boldt
> create bugzilla importer for JIRA
> ---------------------------------
>
> Key: JBIDE-21363
> URL: https://issues.jboss.org/browse/JBIDE-21363
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> 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)
> Example:
> {code}
> Support for smart Import Mechanism [EBZ#464535]"
> issue link: https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535
> {code}
> * [REQ3] Data to be scraped from bugzilla includes:
> * comment #0 -> description
> * fixversion, target milestone
> * product, project, component
> * [REQ4] Will also 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.
> Issues should be created (for testing purposes) here:
> https://issues.stage.jboss.org/browse/ERT
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list