[jbosstools-issues] [JBoss JIRA] (JBIDE-24674) update the list of nag emails to send on QE stage day

Nick Boldt (JIRA) issues at jboss.org
Fri Jul 21 17:43:00 EDT 2017


    [ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438990#comment-13438990 ] 

Nick Boldt commented on JBIDE-24674:
------------------------------------

First step: creation of a script to automatically move issues from one fixversion/sprint to another:

https://github.com/jbosstools/jbosstools-build-ci/pull/167

https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/checkUnresolvedIssues.py

Sample usage:

{code}
python -W ignore ./checkUnresolvedIssues.py --jira https://issues.stage.jboss.org --jirauser ME --jirapwd SECRET --jbt 4.5.0.AM2 --jbt_NEXT 4.5.0.Final --ds 11.0.0.AM2 --ds_NEXT 11.0.0.GA --sprint "devex #134 Jun 2017" --sprint_NEXT "devex #135 July 2017"{code}

For more output, can use -X for debug, -S to skip validation of the fixversions before proceeding, and -A to make changes non-interactively.

For a future milestone, we can then wrap a Jenkins job around this and have the unresolved JIRAs moved automatically. 

[~jeffmaury] can you review the queries I'm using to find issues to move?



> update the list of nag emails to send on QE stage day
> -----------------------------------------------------
>
>                 Key: JBIDE-24674
>                 URL: https://issues.jboss.org/browse/JBIDE-24674
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.5.0.AM2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.5.0.Final
>
>
> We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them.
> We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint.
> And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list