Sorry for the dupes. Was scripting calling the jenkins job via bash and forgot to pass in the recipientOverride so that these would go ONLY to me for testing some copy changes. 

I'll stop spamming you now. 

May the triage be with you,

Nick

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

As the current sprint 'devex' draws to a close, it is time
to review your unresolved issues!

Some may be done (or will be done soon), but the JIRA(s) need resolution.

Others may need to be pushed to the next milestone (4.5.1.AM2 + 11.1.0.AM2),
to a future .x release, 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()

Once created, you can also begin scheduling your work for the upcoming
sprint, 'devex #137 Sept 2017'.

Triage tips:

* blocker/critical issues: make these your priority work for the next sprint:
  move to next version & assign to the next sprint

* other issues that WILL be done in the next sprint:
  move to next version & assign to the forthcoming sprint, but lower down

* non-blocker & non-critical issues not for the next sprint:
  move to .x (or LATER)


_______________________________________________
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