[jbosstools-issues] [JBoss JIRA] (JBIDE-18736) create python tooling to create new milestone targets in JBIDE/JBDS
[
https://issues.jboss.org/browse/JBIDE-18736?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-18736:
------------------------------------
Does it matter which way the data flows as long as all the calendar/schedule/meta are in
sync w/o having to manually do the updates? Generating new .tjp content from changes in
JIRA is possible (though the output is ugly), but using the .tjp as the sourcefile from
which to push to JIRA is also possible.
Benefits to flowing from JIRA -> PP: pretty web UI for updating JIRA; many people can
edit this way (and we can script it too)
Benefits to flowing from PP -> JIRA: controlled from a single sourcefile, which is
editable by only PgM
So is it better to have more control, or more flexibilty?
create python tooling to create new milestone targets in JBIDE/JBDS
-------------------------------------------------------------------
Key: JBIDE-18736
URL: https://issues.jboss.org/browse/JBIDE-18736
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Affects Versions: 4.2.0.Final
Reporter: Nick Boldt
When the calendar is updated every two weeks to add a new sprint (or simply to add new
milestones), we want to be able to update product pages .tjp schedule file [1]; commit to
CVS; & run docbot build.
[1]
http://cvs.devel.redhat.com/cgi-bin/cvsweb.cgi/program/jbds/jbds-8-0-0/jb...
As part of that build, we can now
* generate updated Zimbra calendar
* generate new PP [2]
[2] https://pp.engineering.redhat.com/pp/product/jbds/release/jbds-8-0.0/over...
In addition, we would like to be able to update JBIDE/JBDS milestones in JIRA.
This can be done programmatically via JIRA REST api, using a POST to /rest/api/2/version
( https://issues.jboss.org/rest/api/2/version )
Doc: https://docs.atlassian.com/jira/REST/latest/#d2e2421
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)