[ https://issues.jboss.org/browse/JBIDE-18736?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18736: ------------------------------- Description: 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 was: When the calendar is updated every two weeks to add a new sprint, we want to be able to update product pages .tjp schedule file; commit to CVS; & run docbot build. As part of that build, we can now * generate updated Zimbra calendar * generate new PP 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)