This was supposed to go to Jeff, as he seems to be the only person who can create new sprints consistently. Sorry, my script had the wrong assignee.

Everyone but Jeff can ignore this.

#automationIsGreatWhenYouFeedItTheRightVariables

On Fri, Aug 25, 2017 at 12:44 PM, <nboldt@redhat.com> wrote:

As the current sprint 'devex #136 August 2017' draws to a close,
it is time to create the next sprint, 'devex #137 Sept 2017',
so that planning + triage can occur.

Here are the issues that will need to be moved to the next
sprint, a future milestone, or postponed to .x or LATER.

All unresolved issues for 4.5.1.AM1 / 11.1.0.AM1:

https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVersion%20%3D%2011.1.0.AM1%20OR%20project%20in%20(JBIDE)%20AND%20fixVersion%20%3D%204.5.1.AM1)%20AND%20resolution%20%3D%20null

All *YOUR* unresolved issues for 4.5.1.AM1 / 11.1.0.AM1:

https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVersion%20%3D%2011.1.0.AM1%20OR%20project%20in%20(JBIDE)%20AND%20fixVersion%20%3D%204.5.1.AM1)%20AND%20resolution%20%3D%20null%20and%20assignee%20%3D%20currentUser()


_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev



--

Nick Boldt

Senior Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com