PIRK Components on JIRA

[Ellison Anne Williams <ea...@gmail.com>]

Hi Guys,

As a first step towards starting to organize our JIRA project, I took a
stab at adding some components and adding component specifications to the
open issues. This is just a first pass to get us started -- please feel
free to add/delete/modify.

Thanks!

Ellison Anne

Re: PIRK Components on JIRA

[Tim Ellison <t....@gmail.com>]

On 22/07/16 06:36, Andy LoPresto wrote:
> Component leads are useful if you want to make sure that someone
> (relevant) from the core team sees every issue as it gets reported
> (as long as it is assigned to something) and then triages it. If your
> core team is not necessarily divided by focus that way, component
> leads may not be necessary. You just want to ensure that all incoming
> issues get noticed by someone.

There are also 21 different reasons you can choose from when resolving a
JIRA issue!  I'll admit to choosing a value somewhat randomly, as I
don't see it makes much difference.  So if any one cares please feel
free to educate me on the correct meaning of these, and/or fix up any I
selected incorrectly.

Regards,
Tim

Re: PIRK Components on JIRA

[Andy LoPresto <al...@gmail.com>]

Component leads are useful if you want to make sure that someone (relevant) from the core team sees every issue as it gets reported (as long as it is assigned to something) and then triages it. If your core team is not necessarily divided by focus that way, component leads may not be necessary. You just want to ensure that all incoming issues get noticed by someone. 

Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Jul 21, 2016, at 21:57, Walter Ray-Dulany <ra...@gmail.com> wrote:
> 
> Looks good.
> 
> I'm a JIRA novice, so I did some quick reading on components. It seems like
> this structure works well for us at this younger state. For the same reason
> (our project's youth) I would think it wouldn't make sense to be assigning
> Component Leads just yet? Like I said, I'm new to JIRA, so if someone with
> some actual experience has an opinion on how we're using components, I'd be
> interested in hearing it.
> 
> On Thu, Jul 21, 2016 at 1:56 PM, Ellison Anne Williams <
> eawilliamspirk@gmail.com> wrote:
> 
>> Hi Guys,
>> 
>> As a first step towards starting to organize our JIRA project, I took a
>> stab at adding some components and adding component specifications to the
>> open issues. This is just a first pass to get us started -- please feel
>> free to add/delete/modify.
>> 
>> Thanks!
>> 
>> Ellison Anne
>> 

Re: PIRK Components on JIRA

[Walter Ray-Dulany <ra...@gmail.com>]

Looks good.

I'm a JIRA novice, so I did some quick reading on components. It seems like
this structure works well for us at this younger state. For the same reason
(our project's youth) I would think it wouldn't make sense to be assigning
Component Leads just yet? Like I said, I'm new to JIRA, so if someone with
some actual experience has an opinion on how we're using components, I'd be
interested in hearing it.

On Thu, Jul 21, 2016 at 1:56 PM, Ellison Anne Williams <
eawilliamspirk@gmail.com> wrote:

> Hi Guys,
>
> As a first step towards starting to organize our JIRA project, I took a
> stab at adding some components and adding component specifications to the
> open issues. This is just a first pass to get us started -- please feel
> free to add/delete/modify.
>
> Thanks!
>
> Ellison Anne
>