-
Bug
-
Resolution: Done
-
Major
-
4.3.1.Beta1, 4.4.0.Alpha1
-
None
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:
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
1.
|
add missing m2e mapping; fix dryrun; tweak logging | Closed | Nick Boldt | ||
2.
|
bzira can't handle CLOSED DUPLICATE bugs | Closed | Unassigned |