[jbosstools-issues] [JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla
Max Rydahl Andersen (JIRA)
issues at jboss.org
Wed Aug 10 03:51:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277118#comment-13277118 ]
Max Rydahl Andersen commented on JBIDE-22966:
---------------------------------------------
[~rgrunber] I Agree that would be nice and i'm all for it - but just to let you know why I didn't bother implementing it initially was the following:
A) often when an upstream eclipse issue is resolved/closed it does not mean we are actually done with it on our side - so not changing the state was the simplest.
B) in many cases jira workflows might prevent setting the state - we could of course just fail silently in that case, but it was this issue + A that made me skip it.
If someone does implement then awesome - but I think it might want to be a setting based on products whether you really want the eclipse issue to disappear from view/boards in jira. It might be we learned we do all the work anyway and thus not worth the complexity. In any case - just explaning the reasons why it was not there initially.
> create bzira fork that supports scraping RH bugzilla
> ----------------------------------------------------
>
> Key: JBIDE-22966
> URL: https://issues.jboss.org/browse/JBIDE-22966
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> Sample issue to scrape:
> https://bugzilla.redhat.com/show_bug.cgi?id=1363849
> More issues:
> https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=5630620&product=Red%20Hat%20Software%20Collections
> Target method:
> * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does)
> Mappings:
> * BZ Product = Red Hat Software Collections --> RH-ECLIPSE jira
> * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically)
> * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA
> * Target Milestone --> label in JIRA
> * Target Release -> label in JIRA
> [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list