[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21363:
---------------------------------------------
Here is how to get the content via python:
{code}
import bugzilla
import pprint
pp = pprint.PrettyPrinter()
bz = bugzilla.Bugzilla(url="https://bugs.eclipse.org/bugs/xmlrpc.cgi")
query = bz.url_to_query("https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT")
issues = bz.query(query)
for bug in issues:
print '%s - %s [%s, %s, [%s]] -> %s' % (bug.id, bug.summary, bug.product, bug.component, bug.target_milestone, bug.weburl)
{code}
gives:
{code}
310411 - Toggling of breakpoints should not happen on the UI thread [WTP Source Editing, wst.sse, [Future]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=310411
443097 - Ignore undefined HTML attributes, elements validation with extension point [WTP Source Editing, wst.html, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=443097
459732 - Bower IDE contribution [JSDT, General, [Future]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=459732
464535 - Support for Smart Import mechanism [m2e, ui, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535
470328 - Extension point to delegate JSDoc "Generate Element Comment" [JSDT, General, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=470328
471820 - [contribution] Eclipse WTP JSON Editor [WTP Source Editing, wst.sse, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=471820
472614 - Migrate Smart Project Importer to Eclipse Platform UI [Platform, UI, [4.6]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=472614
473559 - [language support] Add support for ECMAScript 2015 [JSDT, Web, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=473559
477030 - [ES6] Support for ECMAScript 6 syntax coloration [JSDT, General, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=477030
477031 - [ES6] Support for ECMAScript 6 validation [JSDT, General, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=477031
479466 - Support node.js debugging [JSDT, Debug, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=479466
481344 - JSDT should support the use of sourcevalidation extension point [JSDT, General, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=481344
481706 - Update or replace JSDT parser to support ES6 [JSDT, General, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=481706
481828 - Node.js-based JavaScript Dependency Management Tools: bower, npm [JSDT, General, [3.8]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=481828
482054 - Support for Unit testing similar to JDT Junit [JSDT, General, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=482054
482841 - JSDT to utilize org.eclipse.wst.validation.validatorV2 extension point [JSDT, General, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=482841
483398 - JavaScript Task Runner: grunt [JSDT, General, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=483398
483399 - Need to add JavaScript Build System: gulp [JSDT, General, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=483399
484068 - Contribution of Smart Import extension for Java EE development [WTP Incubator, incubator, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=484068
484418 - Need to improve js tools (npm / bower) launch [JSDT, General, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=484418
484597 - Launch configuration for node.js applications [JSDT, Debug, [---]] -> https://bugs.eclipse.org/bugs/show_bug.cgi?id=484597
{code}
This uses `python-bugzilla` you can install via `pip install python-bugzilla`
> 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)
> * [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)
10 years, 3 months
[JBoss JIRA] (JBTIS-539) missing dependency org.kie.eclipse when building JBDS IS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-539?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-539:
----------------------------------
Verified, your new approach works.
Here's a PR to update the READMEs in case you want the above documented for other users:
https://github.com/jbosstools/jbosstools-integration-stack/pull/475
> missing dependency org.kie.eclipse when building JBDS IS
> --------------------------------------------------------
>
> Key: JBTIS-539
> URL: https://issues.jboss.org/browse/JBTIS-539
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Fix For: 9.0.0.Beta1
>
>
> When I try to build the JBDS IS site, I get a missing dependency. What am I doing wrong?
> 1. check out sources from master branch
> 2. cd target-platform; mvn clean install -Pmirror
> (works)
> 3. cd ../jbosstools; mvn clean install -Pstable -Pearlyaccess
> (works)
> 4. cd ../devstudio; mvn clean install -Pstable -Pearlyaccess
> Fails:
> {code}
> [INFO] Resolving dependencies of MavenProject: com.jboss.jbds.integration-stack:site-ea:9.0.0-SNAPSHOT @ /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-integration-stack/devstudio/site-ea/pom.xml
> [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: site-ea raw:9.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):9.0.0-SNAPSHOT
> [ERROR] Missing requirement: site-ea raw:9.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):9.0.0-SNAPSHOT requires 'org.kie.eclipse.feature.feature.group 0.0.0' but it could not be found{code}
> From where should I be resolving org.kie.eclipse.feature? It's in the JBTIS site, but JBDSIS can't find it. :(
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21357) Missing dialog messages for publishing via server adapter on OpenShift 2 applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21357?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21357:
-------------------------------------
Fix Version/s: 4.3.1.Beta2
> Missing dialog messages for publishing via server adapter on OpenShift 2 applications
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-21357
> URL: https://issues.jboss.org/browse/JBIDE-21357
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Fix For: 4.3.1.Beta2
>
> Attachments: publish_msg.png, publish_msg_no_changes.png
>
>
> When I am trying to publish code to OpenShift 2 application via server adapter, there are dialogs which contains missing msg info instead of message. First one is in case of publishing no changes, another one is when I create a new OpenShift 2 application from local eclipse project via deploying to OpenShift in context menu of the eclipse project and then select Publish in context menu of server adapter. See attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21357) Missing dialog messages for publishing via server adapter on OpenShift 2 applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21357?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21357:
----------------------------------------
Assignee: Andre Dietisheim
> Missing dialog messages for publishing via server adapter on OpenShift 2 applications
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-21357
> URL: https://issues.jboss.org/browse/JBIDE-21357
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta2
>
> Attachments: publish_msg.png, publish_msg_no_changes.png
>
>
> When I am trying to publish code to OpenShift 2 application via server adapter, there are dialogs which contains missing msg info instead of message. First one is in case of publishing no changes, another one is when I create a new OpenShift 2 application from local eclipse project via deploying to OpenShift in context menu of the eclipse project and then select Publish in context menu of server adapter. See attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-16970) create mechanism to verify that nightly build is different from previous milestone
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16970 at 12/17/15 5:33 PM:
--------------------------------------------------------------
Above change applied in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... AFTER build 11317. Will need to let this grind for a few iterations to see if it works as expected.
...
Can't filter on BUILD_NUMBER because the p2diff report includes TWO versions, not just the current one.
Thus, applied in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... >=11321:
{code}
egrep -v "(<|>) (Alpha[0-9]+|Beta[0-9]+|CR[0-9]+|Final|GA).+-B[0-9]+\."
{code}
DONE: applied change to other stream & other jobs
was (Author: nickboldt):
Above change applied in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... AFTER build 11317. Will need to let this grind for a few iterations to see if it works as expected.
TODO: check logs for similar changes (or better, actual ones)
TODO: apply change to other stream & other jobs
> create mechanism to verify that nightly build is different from previous milestone
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-16970
> URL: https://issues.jboss.org/browse/JBIDE-16970
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.x
>
>
> After the discovery site build job is done, we should:
> * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case)
> * for respins, use *job param* label = "respin-a" or "respin-b" in jira query
> * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings
> * install Eclipse from *job param* eclipseBundleVersion = luna.M6
> * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet...
> * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder)
> * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/
> * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal...
> * run p2diff on the two repos - see https://github.com/irbull/p2diff
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-16970) create mechanism to verify that nightly build is different from previous milestone
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16970 at 12/17/15 5:33 PM:
--------------------------------------------------------------
TODO: check logs for similar changes (or better, actual ones)
was (Author: nickboldt):
Can't filter on BUILD_NUMBER because the p2diff report includes TWO versions, not just the current one.
Thus, applied in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... >=11321:
{code}
egrep -v "(<|>) (Alpha[0-9]+|Beta[0-9]+|CR[0-9]+|Final|GA).+-B[0-9]+\."
{code}
> create mechanism to verify that nightly build is different from previous milestone
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-16970
> URL: https://issues.jboss.org/browse/JBIDE-16970
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.x
>
>
> After the discovery site build job is done, we should:
> * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case)
> * for respins, use *job param* label = "respin-a" or "respin-b" in jira query
> * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings
> * install Eclipse from *job param* eclipseBundleVersion = luna.M6
> * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet...
> * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder)
> * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/
> * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal...
> * run p2diff on the two repos - see https://github.com/irbull/p2diff
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21363:
-------------------------------
Description:
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}
was:
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}
title: 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
> 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)
> * [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)
10 years, 3 months
[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21363:
-------------------------------
Description:
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}
title: 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
was:
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
> 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}
> title: 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)
10 years, 3 months