[jbosstools-issues] [JBoss JIRA] (JBIDE-24674) automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-24674:
-------------------------------
    Description: 
1. 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.
* *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-releng-push-to-staging-00-sprint-creation-and-jira-triage-request-emails/
2. 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.
* *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-releng-push-to-staging-00-sprint-creation-and-jira-triage-request-emails/

3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version.

*TODO*: 
* filter out those issues with labels = releasework


  was:
1. 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.
* *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-releng-push-to-staging-00-sprint-creation-and-jira-triage-request-emails/
2. 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.
* *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-releng-push-to-staging-00-sprint-creation-and-jira-triage-request-emails/

3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version.

*TODO*: 
* filter out those issues with labels = releasework
* if yesno is null, assume Y




> automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation
> ---------------------------------------------------------------------------------------------------------
>
>                 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
>              Labels: releasework
>             Fix For: 4.5.1.AM1
>
>
> 1. 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.
> * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-releng-push-to-staging-00-sprint-creation-and-jira-triage-request-emails/
> 2. 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.
> * *NEW*: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-releng-push-to-staging-00-sprint-creation-and-jira-triage-request-emails/
> 3. And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version.
> *TODO*: 
> * filter out those issues with labels = releasework



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