You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Musayev, Ilya" <im...@webmd.net> on 2013/10/03 00:14:57 UTC
[DISCUSS] Components in JIRA and bug assignment
I would like to separate this thread on tickets assignments in JIRA.
Previously it was mentioned that we can add additional components into JIRA CLOUDSTACK project and have ticket default to maintainer of the component - who can then assign it to a proper developer.
What do you think?
Any other suggestions?
If agreed, who has the karma in JIRA to do this?
What components we need to add or remove to lower the confusion?
Last but not least, if someone can explain how bug reporter would identify the proper component, we can then post it on WIKI and minimize the error rate caused by improper bug filling.
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Musayev, Ilya [mailto:imusayev@webmd.net]
> Sent: Friday, October 04, 2013 12:10 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [DISCUSS] Components in JIRA and bug assignment
>
> Response in line:
>
> > -----Original Message-----
> > From: Santhosh Edukulla [mailto:santhosh.edukulla@citrix.com]
> > Sent: Friday, October 04, 2013 2:02 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: [DISCUSS] Components in JIRA and bug assignment
> >
> > Not Sure, if it falls under similar lines\requires a separate thread.
> > I am trying to see if there is a way we can add a component field,
> > primary owner fields for component available to be assigned for a
> > given review under Http://reviews.apache.org.
>
> While we want to extend JIRA and add various components to address
> current limitations, I'm not certain if this is in the same scope. I
> also have to admit, that I only use JIRA as basic user, so I don't know
> if what you are asking is doable. Perhaps someone else can?
>
[Animesh>] Reviews are managed in separate tool called ReviewBoard
>
> >
> > This way i will select component as "Automation", branch as "4.1" and
> > so etc , save that query on my dashboard and everytime i login, i can
> > see reviews based upon my query saved.
>
> We can create a separate component Automation, so you can create filters
> as described.
>
[Animesh>] JIRA already has a component for Automation. Santhosh you should open a separate thread for review board enhancements
> >
> > If this facility is already there, then i will search more to find it
> out.
> >
> > Regards,
> > Santhosh
> > ________________________________________
> > From: Chip Childers [chip.childers@sungard.com]
> > Sent: Friday, October 04, 2013 1:45 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [DISCUSS] Components in JIRA and bug assignment
> >
> > On Fri, Oct 04, 2013 at 05:40:06PM +0000, Animesh Chaturvedi wrote:
> > >
> > > [Animesh>] Chip does that mean you are open to folks assigning
> > > tickets to others? Should this be posted in the original thread
> > > http://markmail.org/thread/btovj6t6opqxge5q. because the threads
> > where
> > > Ilya reopened the discussion has received few responses from Alex,
> > > Sheng, Alena, Sudha, RamG
> > >
> >
> > No, that just means that I was explaining the technical capabilities
> of Jira.
> >
> > I'm -0, so move forward if everyone else continues to agree. I still
> > don't think it's the right way to operate, but I'm not interested in
> > blocking it if everyone else wants to do it this way.
> >
> > I won't reiterate my previous reasoning, since you pointed to that
> thread.
> >
> > Cheers!
> >
> > -chip
>
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by "Musayev, Ilya" <im...@webmd.net>.
Response in line:
> -----Original Message-----
> From: Santhosh Edukulla [mailto:santhosh.edukulla@citrix.com]
> Sent: Friday, October 04, 2013 2:02 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [DISCUSS] Components in JIRA and bug assignment
>
> Not Sure, if it falls under similar lines\requires a separate thread. I am trying
> to see if there is a way we can add a component field, primary owner fields
> for component available to be assigned for a given review under
> Http://reviews.apache.org.
While we want to extend JIRA and add various components to address current limitations, I'm not certain if this is in the same scope. I also have to admit, that I only use JIRA as basic user, so I don't know if what you are asking is doable. Perhaps someone else can?
>
> This way i will select component as "Automation", branch as "4.1" and so etc ,
> save that query on my dashboard and everytime i login, i can see reviews
> based upon my query saved.
We can create a separate component Automation, so you can create filters as described.
>
> If this facility is already there, then i will search more to find it out.
>
> Regards,
> Santhosh
> ________________________________________
> From: Chip Childers [chip.childers@sungard.com]
> Sent: Friday, October 04, 2013 1:45 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Components in JIRA and bug assignment
>
> On Fri, Oct 04, 2013 at 05:40:06PM +0000, Animesh Chaturvedi wrote:
> >
> > [Animesh>] Chip does that mean you are open to folks assigning tickets
> > to others? Should this be posted in the original thread
> > http://markmail.org/thread/btovj6t6opqxge5q. because the threads
> where
> > Ilya reopened the discussion has received few responses from Alex,
> > Sheng, Alena, Sudha, RamG
> >
>
> No, that just means that I was explaining the technical capabilities of Jira.
>
> I'm -0, so move forward if everyone else continues to agree. I still don't think
> it's the right way to operate, but I'm not interested in blocking it if everyone
> else wants to do it this way.
>
> I won't reiterate my previous reasoning, since you pointed to that thread.
>
> Cheers!
>
> -chip
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by Santhosh Edukulla <sa...@citrix.com>.
Not Sure, if it falls under similar lines\requires a separate thread. I am trying to see if there is a way we can add a component field, primary owner fields for component available to be assigned for a given review under Http://reviews.apache.org.
This way i will select component as "Automation", branch as "4.1" and so etc , save that query on my dashboard and everytime i login, i can see reviews based upon my query saved.
If this facility is already there, then i will search more to find it out.
Regards,
Santhosh
________________________________________
From: Chip Childers [chip.childers@sungard.com]
Sent: Friday, October 04, 2013 1:45 PM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Components in JIRA and bug assignment
On Fri, Oct 04, 2013 at 05:40:06PM +0000, Animesh Chaturvedi wrote:
>
> [Animesh>] Chip does that mean you are open to folks assigning tickets to others? Should this be posted in the original thread http://markmail.org/thread/btovj6t6opqxge5q. because the threads where Ilya reopened the discussion has received few responses from Alex, Sheng, Alena, Sudha, RamG
>
No, that just means that I was explaining the technical capabilities of
Jira.
I'm -0, so move forward if everyone else continues to agree. I still
don't think it's the right way to operate, but I'm not interested in
blocking it if everyone else wants to do it this way.
I won't reiterate my previous reasoning, since you pointed to that
thread.
Cheers!
-chip
Re: [DISCUSS] Components in JIRA and bug assignment
Posted by Chip Childers <ch...@sungard.com>.
On Fri, Oct 04, 2013 at 05:55:58PM +0000, Animesh Chaturvedi wrote:
> [Animesh>] Chip I get the principle behind the reasoning in thread[2] which should be maintained but at the same time not being able to assign the issues is a big hindrance in running a release. I am not sure if you saw my response in this thread [1] started by Ilya which was based on my experience as RM for 4.2.0
>
I did see it. I'm agreeing to disagree but not be a hindrance to
progress. ;-)
If everyone else agrees with the approach, then rock on with it!
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Friday, October 04, 2013 10:45 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Components in JIRA and bug assignment
>
> On Fri, Oct 04, 2013 at 05:40:06PM +0000, Animesh Chaturvedi wrote:
> >
> > [Animesh>] Chip does that mean you are open to folks assigning tickets
> > to others? Should this be posted in the original thread
> > http://markmail.org/thread/btovj6t6opqxge5q. because the threads where
> > Ilya reopened the discussion has received few responses from Alex,
> > Sheng, Alena, Sudha, RamG
> >
>
> No, that just means that I was explaining the technical capabilities of
> Jira.
>
> I'm -0, so move forward if everyone else continues to agree. I still
> don't think it's the right way to operate, but I'm not interested in
> blocking it if everyone else wants to do it this way.
>
> I won't reiterate my previous reasoning, since you pointed to that
> thread.
>
> Cheers!
>
> -chip
[Animesh>] Chip I get the principle behind the reasoning in thread[2] which should be maintained but at the same time not being able to assign the issues is a big hindrance in running a release. I am not sure if you saw my response in this thread [1] started by Ilya which was based on my experience as RM for 4.2.0
I am +1 on the proposal
[1] http://markmail.org/thread/cwxxxjnkor6trq4s
[2] http://markmail.org/thread/btovj6t6opqxge5q
Re: [DISCUSS] Components in JIRA and bug assignment
Posted by Chip Childers <ch...@sungard.com>.
On Fri, Oct 04, 2013 at 05:40:06PM +0000, Animesh Chaturvedi wrote:
>
> [Animesh>] Chip does that mean you are open to folks assigning tickets to others? Should this be posted in the original thread http://markmail.org/thread/btovj6t6opqxge5q. because the threads where Ilya reopened the discussion has received few responses from Alex, Sheng, Alena, Sudha, RamG
>
No, that just means that I was explaining the technical capabilities of
Jira.
I'm -0, so move forward if everyone else continues to agree. I still
don't think it's the right way to operate, but I'm not interested in
blocking it if everyone else wants to do it this way.
I won't reiterate my previous reasoning, since you pointed to that
thread.
Cheers!
-chip
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Friday, October 04, 2013 10:28 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] Components in JIRA and bug assignment
>
> 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
[Animesh>] Chip does that mean you are open to folks assigning tickets to others? Should this be posted in the original thread http://markmail.org/thread/btovj6t6opqxge5q. because the threads where Ilya reopened the discussion has received few responses from Alex, Sheng, Alena, Sudha, RamG
Re: [DISCUSS] Components in JIRA and bug assignment
Posted by Daan Hoogland <da...@gmail.com>.
On Mon, Oct 7, 2013 at 10:50 PM, Sheng Yang <sh...@yasker.org> wrote:
> One basic rule for component maintainer to assign the ticket, can be: Fix
> your own code.
>
I agree with Sheng. And with Ilya on the point that I think we will have to
revisit this procedure soon. What I am thinking of is the expectation of a
reporter that on entering a feature request/bug follow up will happen.
I still don't like the approach but have no better alternative so I have to:
+1
regards,
Daan
Re: [DISCUSS] Components in JIRA and bug assignment
Posted by Sheng Yang <sh...@yasker.org>.
+1 to the approach.
One basic rule for component maintainer to assign the ticket, can be: Fix
your own code. If the bug is introduced by a certain commit(etc, using 'git
blame'), it would go to the committer to fix or revert it, unless someone
else volunteer to fix it. Of course sometime it wouldn't be easy to tell
which commit introduce the bug, and people made mistakes on deciding
troublesome commit, but least it should help on the majority of the issues..
--Sheng
On Mon, Oct 7, 2013 at 8:15 AM, Musayev, Ilya <im...@webmd.net> wrote:
> Daan,
>
> As comparison, take a look at where we are now. We have a great deal of
> unassigned tickets, mostly because we lack structure on JIRA side and its
> too general.
>
> I also don’t believe there should be an issue of monopoly, there is more
> work than we can possibly handle and it should only affect tickets in
> unassigned queue.
>
> This is a community effort, if someone feels they can help resolve the
> ticket, they can ask for it to be assigned to them or they can assign
> ticket to _self.
>
> At the very least, we should have less unassigned tickets, because it was
> misfiled or missed.
>
> Last point I would like to make, if we feel like this structure is not
> working in our favor in the future, we can always discuss and alter as
> necessary, but leaving as-is, does not seem to be very productive.
>
> Regards
> ilya
>
> > -----Original Message-----
> > From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> > Sent: Monday, October 07, 2013 12:33 AM
> > To: dev@cloudstack.apache.org
> > Cc: Musayev, Ilya
> > Subject: RE: [DISCUSS] Components in JIRA and bug assignment
> >
> >
> >
> > > -----Original Message-----
> > > From: Daan Hoogland [mailto:daan.hoogland@gmail.com]
> > > Sent: Sunday, October 06, 2013 12:16 PM
> > > To: dev
> > > Cc: Musayev, Ilya
> > > Subject: Re: [DISCUSS] Components in JIRA and bug assignment
> > >
> > > 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?
> > [Animesh>] There is no monopoly or hierarchy, everyone is equal. When
> > someone asks another person to pick up an issue it is a request not an
> > assignment. They can always say they can't and unassign with comments
> > > . 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?
> > >
> > [Animesh>] That's reasonable for a ticket created by a QA member of the
> > community but for tickets coming from users they may not know who should
> > those be assigned and we would like to lower the barrier of entry for
> users
> > reporting the defects.
> >
> > > 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
> > > <ra...@citrix.com>wrote:
> > >
> > > > +1 for the proposal.
> > > >
> > > > -----Original Message-----
> > > > From: Alena Prokharchyk [mailto:Alena.Prokharchyk@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" <im...@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.
> > > >
> > > >
>
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by "Musayev, Ilya" <im...@webmd.net>.
Daan,
As comparison, take a look at where we are now. We have a great deal of unassigned tickets, mostly because we lack structure on JIRA side and its too general.
I also don’t believe there should be an issue of monopoly, there is more work than we can possibly handle and it should only affect tickets in unassigned queue.
This is a community effort, if someone feels they can help resolve the ticket, they can ask for it to be assigned to them or they can assign ticket to _self.
At the very least, we should have less unassigned tickets, because it was misfiled or missed.
Last point I would like to make, if we feel like this structure is not working in our favor in the future, we can always discuss and alter as necessary, but leaving as-is, does not seem to be very productive.
Regards
ilya
> -----Original Message-----
> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> Sent: Monday, October 07, 2013 12:33 AM
> To: dev@cloudstack.apache.org
> Cc: Musayev, Ilya
> Subject: RE: [DISCUSS] Components in JIRA and bug assignment
>
>
>
> > -----Original Message-----
> > From: Daan Hoogland [mailto:daan.hoogland@gmail.com]
> > Sent: Sunday, October 06, 2013 12:16 PM
> > To: dev
> > Cc: Musayev, Ilya
> > Subject: Re: [DISCUSS] Components in JIRA and bug assignment
> >
> > 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?
> [Animesh>] There is no monopoly or hierarchy, everyone is equal. When
> someone asks another person to pick up an issue it is a request not an
> assignment. They can always say they can't and unassign with comments
> > . 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?
> >
> [Animesh>] That's reasonable for a ticket created by a QA member of the
> community but for tickets coming from users they may not know who should
> those be assigned and we would like to lower the barrier of entry for users
> reporting the defects.
>
> > 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
> > <ra...@citrix.com>wrote:
> >
> > > +1 for the proposal.
> > >
> > > -----Original Message-----
> > > From: Alena Prokharchyk [mailto:Alena.Prokharchyk@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" <im...@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.
> > >
> > >
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Daan Hoogland [mailto:daan.hoogland@gmail.com]
> Sent: Sunday, October 06, 2013 12:16 PM
> To: dev
> Cc: Musayev, Ilya
> Subject: Re: [DISCUSS] Components in JIRA and bug assignment
>
> 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?
[Animesh>] There is no monopoly or hierarchy, everyone is equal. When someone asks another person to pick up an issue it is a request not an assignment. They can always say they can't and unassign with comments
> . 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?
>
[Animesh>] That's reasonable for a ticket created by a QA member of the community but for tickets coming from users they may not know who should those be assigned and we would like to lower the barrier of entry for users reporting the defects.
> 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
> <ra...@citrix.com>wrote:
>
> > +1 for the proposal.
> >
> > -----Original Message-----
> > From: Alena Prokharchyk [mailto:Alena.Prokharchyk@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" <im...@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.
> >
> >
Re: [DISCUSS] Components in JIRA and bug assignment
Posted by Daan Hoogland <da...@gmail.com>.
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 <ra...@citrix.com>wrote:
> +1 for the proposal.
>
> -----Original Message-----
> From: Alena Prokharchyk [mailto:Alena.Prokharchyk@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" <im...@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.
>
>
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by Rajesh Battala <ra...@citrix.com>.
+1 for the proposal.
-----Original Message-----
From: Alena Prokharchyk [mailto:Alena.Prokharchyk@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" <im...@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.
Re: [DISCUSS] Components in JIRA and bug assignment
Posted by Travis Graham <tg...@tgraham.us>.
I don't think we need to add another tool for this. I'm sure Jira is fully capable of doing what's needed, it's just finding the right configuration and the person who knows how to get things setup to work.
Travis
On Oct 8, 2013, at 9:15 AM, Frankie Onuonga <fr...@angani.co> wrote:
> +1 I think we need another tool to do this .
> Maybe set up trac or RT.
>
>
> Sent from my Windows Phone
> ________________________________
> From: Alena Prokharchyk<ma...@citrix.com>
> Sent: 10/4/2013 10:12 PM
> To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>; Musayev, Ilya<ma...@webmd.net>
> Subject: Re: [DISCUSS] Components in JIRA and bug assignment
>
> On 10/4/13 10:37 AM, "Musayev, Ilya" <im...@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.
>
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by Frankie Onuonga <fr...@angani.co>.
+1 I think we need another tool to do this .
Maybe set up trac or RT.
Sent from my Windows Phone
________________________________
From: Alena Prokharchyk<ma...@citrix.com>
Sent: 10/4/2013 10:12 PM
To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>; Musayev, Ilya<ma...@webmd.net>
Subject: Re: [DISCUSS] Components in JIRA and bug assignment
On 10/4/13 10:37 AM, "Musayev, Ilya" <im...@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.
Re: [DISCUSS] Components in JIRA and bug assignment
Posted by Alena Prokharchyk <Al...@citrix.com>.
On 10/4/13 10:37 AM, "Musayev, Ilya" <im...@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.
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by "Musayev, Ilya" <im...@webmd.net>.
> 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
Re: [DISCUSS] Components in JIRA and bug assignment
Posted by Chip Childers <ch...@sungard.com>.
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
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by "Musayev, Ilya" <im...@webmd.net>.
As per thread below with Animesh, we would like to resurrect the issue.
As per my conversation with Chip, the issue for not letting component maintainers - get assignments by default - was because we wanted to maintain a balance of "getting things done" vs "letting community grow"
Question to JIRA experienced admins, we can preserve "assign to me" option, and if unassigned goto "component" maintainer?
> -----Original Message-----
> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> Sent: Wednesday, October 02, 2013 6:48 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [DISCUSS] Components in JIRA and bug assignment
>
>
>
> > -----Original Message-----
> > From: Musayev, Ilya [mailto:imusayev@webmd.net]
> > Sent: Wednesday, October 02, 2013 3:15 PM
> > To: dev@cloudstack.apache.org
> > Subject: [DISCUSS] Components in JIRA and bug assignment
> >
> > I would like to separate this thread on tickets assignments in JIRA.
> >
> > Previously it was mentioned that we can add additional components into
> > JIRA CLOUDSTACK project and have ticket default to maintainer of the
> > component - who can then assign it to a proper developer.
> >
> [Animesh>] Yes JIRA allows adding a component lead. I can add components
> and the primary lead if the community agrees to it. This will be based on our
> maintainers list [1]
>
> > What do you think?
> [Animesh>]+1, I had brought up the same idea in the thread [2] and that
> time it was not approved by the community. With my experience from 4.2.0 I
> would like it to be reconsidered.
>
> >
> > Any other suggestions?
> >
> [Animesh>] In the thread [3] I had also called out the email subscriptions for
> each of the components based on JIRA filter, but at that time I did not get
> much response.
>
> > If agreed, who has the karma in JIRA to do this?
> [Animesh>] There are few folks that have Admin access to JIRA including me.
> Alex, David, Chip are ofcourse administrators.
> >
> > What components we need to add or remove to lower the confusion?
> [Animesh>] We should review the current component list and refine them.
> Some of them are over used like "management Server" as Sheng mentioned
> in the other thread.
> >
> > Last but not least, if someone can explain how bug reporter would
> > identify the proper component, we can then post it on WIKI and
> > minimize the error rate caused by improper bug filling.
> [Animesh>] We can add a description column in [1] to provide description for
> the components.
>
> [1]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Current+Maintai
> ners+Per+Component
> [2] http://markmail.org/thread/btovj6t6opqxge5q
> [3] http://markmail.org/thread/2gm4lq3lgfdzeo53
>
RE: [DISCUSS] Components in JIRA and bug assignment
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Musayev, Ilya [mailto:imusayev@webmd.net]
> Sent: Wednesday, October 02, 2013 3:15 PM
> To: dev@cloudstack.apache.org
> Subject: [DISCUSS] Components in JIRA and bug assignment
>
> I would like to separate this thread on tickets assignments in JIRA.
>
> Previously it was mentioned that we can add additional components into
> JIRA CLOUDSTACK project and have ticket default to maintainer of the
> component - who can then assign it to a proper developer.
>
[Animesh>] Yes JIRA allows adding a component lead. I can add components and the primary lead if the community agrees to it. This will be based on our maintainers list [1]
> What do you think?
[Animesh>]+1, I had brought up the same idea in the thread [2] and that time it was not approved by the community. With my experience from 4.2.0 I would like it to be reconsidered.
>
> Any other suggestions?
>
[Animesh>] In the thread [3] I had also called out the email subscriptions for each of the components based on JIRA filter, but at that time I did not get much response.
> If agreed, who has the karma in JIRA to do this?
[Animesh>] There are few folks that have Admin access to JIRA including me. Alex, David, Chip are ofcourse administrators.
>
> What components we need to add or remove to lower the confusion?
[Animesh>] We should review the current component list and refine them. Some of them are over used like "management Server" as Sheng mentioned in the other thread.
>
> Last but not least, if someone can explain how bug reporter would
> identify the proper component, we can then post it on WIKI and minimize
> the error rate caused by improper bug filling.
[Animesh>] We can add a description column in [1] to provide description for the components.
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Current+Maintainers+Per+Component
[2] http://markmail.org/thread/btovj6t6opqxge5q
[3] http://markmail.org/thread/2gm4lq3lgfdzeo53