> -----Original Message-----
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: Monday, April 08, 2013 2:05 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Don't assign tickets to people when triaging
>
>
>
> On 4/8/13 1:32 PM, "Animesh Chaturvedi" <animesh.chaturv...@citrix.com>
> wrote:
>
> >
> >>
> >> I also wanted to find out how do other projects get through resolving
> >>blocker bugs sooner?
> >>
> >> [1]
> >>
> >>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Current+Maintai
> >>ner
> >> s+Per+Component
> >>
> >[Animesh>] Folks I wanted to get your opinion on auto-assignment based
> >on the component maintainers list. We can also create shared issues
> >filters based on components. Folks can subscribe to the filters of
> >interest and receive daily email notification.
>
> Although the wiki and Jira are useful repositories of information, the ML is
> where things are supposed to get decided. How about a daily report posted to
> the ML (could be auto posted from Jira?) that lists
> - defects that have aged > 1 week without an owner
> - defects newly assigned to somebody
> - new defects without any owners
> - defects assigned but no progress > 1 week
>
> Yes, anybody could run the same report on Jira, but this brings it out in the
> open?
[Animesh>] That is certainly doable. As per Jira documentation it supports
subscription emails to be sent to groups and supports scheduling, but looks
like I don't have sufficient privilege to check on this feature in Apache
CloudStack JIRA. Chip/David can you confirm whether this can be done in Apache
JIRA
