I have doubts about this thought it would seem productive. It constructs a small assignment hierarchy in the community which feels fine for any company project I have worked on in the past.
It feels out of place. . Are those component maintainers going to have monopoly on assigning tickets pertaining to 'their' component? . as a featurist: a ticket will usually pertain to several components. it can be for instance UI - API - orchestration - provisioning - network - storage. I would think the person entering the ticket has the responsibility of finding devs/assigning the work. (dis)agree? I actually prefer unassigned tickets and a irc meeting like discussion on them once in a while. just €0,02 Daan On Sun, Oct 6, 2013 at 6:08 AM, Rajesh Battala <rajesh.batt...@citrix.com>wrote: > +1 for the proposal. > > -----Original Message----- > From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com] > Sent: Saturday, October 5, 2013 12:42 AM > To: dev@cloudstack.apache.org; Musayev, Ilya > Subject: Re: [DISCUSS] Components in JIRA and bug assignment > Importance: High > > On 10/4/13 10:37 AM, "Musayev, Ilya" <imusa...@webmd.net> wrote: > > >> On Fri, Oct 04, 2013 at 05:11:32PM +0000, Musayev, Ilya wrote: > >> > Question to JIRA experienced admins, we can preserve "assign to me" > >> option, and if unassigned goto "component" maintainer? > >> > >> Absolutely. Initial assignment does not equal the actual assignee. > >> Component-based assignment is just a way to skip the unassigned > >> phase, but people can reassign to themselves or others. > >> > >> -chip > > > >Chip, thanks for the answer. > > > >So far, I've yet to see someone speaking negatively on this proposal. > >We do need better structure - that will also help us being productive. > > > >Please kindly respond with +1, 0 or -1 > > > >If -1, please explain why. > > > >Thanks > >ilya > > > > > > > +1 > > -Alena. > >
