Process of using JIRA vs dev list?

[Eric Owhadi <er...@esgyn.com>]

I thought that using JIRA was a great way to collaborate on a topic, and
keep the history of conversation searchable and well formatted.

However, I think only watchers on a JIRA will see email notification on
comments, (not sure about that). If nobody is watching, then it is
pointless.

There is a way to add watchers to a JIRA, but it looks like one need to
have specific privilege to do so. I got error message trying that.

Dave do you know how one could force sending stuff to dev list from a JIRA
comment?

Eric

Re: Process of using JIRA vs dev list?

[Dave Birdsall <da...@esgyn.com>]

Hi,

JIRA is a better place to keep discussion, as it also serves as an
historical record on the topic. If it is discussed instead on a dlist, it
will tend to get lost among 1000's of other e-mails on different topics.

Dave

On Mon, Jul 27, 2015 at 5:20 PM, Hans Zeller <ha...@esgyn.com> wrote:

> Agree, we should try to opt for a pull rather than push model where
> possible. An initial message on the dev list is probably ok, but the
> exchange of many more detailed emails is better done on the JIRA.
>
> If the message includes a link to the JIRA, adding ourselves as a watcher
> is just a few clicks.
>
> I used to get an email for every JIRA that got created (yes, that includes
> the 1400 or so created by Alice). Did that get turned off? I couldn't find
> a profile setting in JIRA to turn it back on.
>
> Thanks,
>
> Hans
>
> On Mon, Jul 27, 2015 at 4:49 PM, Steve Varnau <st...@esgyn.com>
> wrote:
>
> > Folks that want to see what is happening in JIRA can subscribe to
> > issues@trafodion.incubator.apache.org. Why use dev list for the same
> > thing?
> >
> > --Steve
> >
> > -----Original Message-----
> > From: Eric Owhadi [mailto:eric.owhadi@esgyn.com]
> > Sent: Monday, July 27, 2015 4:10 PM
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: Process of using JIRA vs dev list?
> >
> > My 2 cts is that this is not scalable. I'd rather send to dev list, and
> > copy
> > back to JIRA.
> > Don't know what others think?
> > Eric
> >
> >
> > -----Original Message-----
> > From: Dave Birdsall [mailto:dave.birdsall@esgyn.com]
> > Sent: Monday, July 27, 2015 5:39 PM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Re: Process of using JIRA vs dev list?
> >
> > Hi,
> >
> > Looks like with the current permissions set-up for Trafodion JIRAs,
> anyone
> > can view the list of watchers for a given JIRA. Committers, PMC members
> > (including our mentors) and JIRA administrators can manage the watcher
> > list.
> > So, if you wish, I can add watchers for a given JIRA for you. Of course,
> > everyone can add themselves as a watcher or remove themselves.
> >
> > Dave
> >
> > On Mon, Jul 27, 2015 at 3:27 PM, Dave Birdsall <da...@esgyn.com>
> > wrote:
> >
> > > Hi Eric,
> > >
> > > Hmmmm... let me look into adding watchers in JIRA. Maybe we can change
> > > the permissions policy.
> > >
> > > Another way to proceed is when you create a new JIRA, you can e-mail
> > > the dev list (or specific people you think would be interested
> > > instead) about your JIRA, including a URL pointing to the JIRA, and
> > > invite them to add themselves as watchers and/or comment there.
> > >
> > > Dave
> > >
> > > On Mon, Jul 27, 2015 at 3:19 PM, Eric Owhadi <er...@esgyn.com>
> > > wrote:
> > >
> > >> I thought that using JIRA was a great way to collaborate on a topic,
> > >> and keep the history of conversation searchable and well formatted.
> > >>
> > >> However, I think only watchers on a JIRA will see email notification
> > >> on comments, (not sure about that). If nobody is watching, then it is
> > >> pointless.
> > >>
> > >> There is a way to add watchers to a JIRA, but it looks like one need
> > >> to have specific privilege to do so. I got error message trying that.
> > >>
> > >> Dave do you know how one could force sending stuff to dev list from a
> > >> JIRA comment?
> > >>
> > >> Eric
> > >>
> > >
> > >
> >
>

Re: Process of using JIRA vs dev list?

[Hans Zeller <ha...@esgyn.com>]

Agree, we should try to opt for a pull rather than push model where
possible. An initial message on the dev list is probably ok, but the
exchange of many more detailed emails is better done on the JIRA.

If the message includes a link to the JIRA, adding ourselves as a watcher
is just a few clicks.

I used to get an email for every JIRA that got created (yes, that includes
the 1400 or so created by Alice). Did that get turned off? I couldn't find
a profile setting in JIRA to turn it back on.

Thanks,

Hans

On Mon, Jul 27, 2015 at 4:49 PM, Steve Varnau <st...@esgyn.com>
wrote:

> Folks that want to see what is happening in JIRA can subscribe to
> issues@trafodion.incubator.apache.org. Why use dev list for the same
> thing?
>
> --Steve
>
> -----Original Message-----
> From: Eric Owhadi [mailto:eric.owhadi@esgyn.com]
> Sent: Monday, July 27, 2015 4:10 PM
> To: dev@trafodion.incubator.apache.org
> Subject: RE: Process of using JIRA vs dev list?
>
> My 2 cts is that this is not scalable. I'd rather send to dev list, and
> copy
> back to JIRA.
> Don't know what others think?
> Eric
>
>
> -----Original Message-----
> From: Dave Birdsall [mailto:dave.birdsall@esgyn.com]
> Sent: Monday, July 27, 2015 5:39 PM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Process of using JIRA vs dev list?
>
> Hi,
>
> Looks like with the current permissions set-up for Trafodion JIRAs, anyone
> can view the list of watchers for a given JIRA. Committers, PMC members
> (including our mentors) and JIRA administrators can manage the watcher
> list.
> So, if you wish, I can add watchers for a given JIRA for you. Of course,
> everyone can add themselves as a watcher or remove themselves.
>
> Dave
>
> On Mon, Jul 27, 2015 at 3:27 PM, Dave Birdsall <da...@esgyn.com>
> wrote:
>
> > Hi Eric,
> >
> > Hmmmm... let me look into adding watchers in JIRA. Maybe we can change
> > the permissions policy.
> >
> > Another way to proceed is when you create a new JIRA, you can e-mail
> > the dev list (or specific people you think would be interested
> > instead) about your JIRA, including a URL pointing to the JIRA, and
> > invite them to add themselves as watchers and/or comment there.
> >
> > Dave
> >
> > On Mon, Jul 27, 2015 at 3:19 PM, Eric Owhadi <er...@esgyn.com>
> > wrote:
> >
> >> I thought that using JIRA was a great way to collaborate on a topic,
> >> and keep the history of conversation searchable and well formatted.
> >>
> >> However, I think only watchers on a JIRA will see email notification
> >> on comments, (not sure about that). If nobody is watching, then it is
> >> pointless.
> >>
> >> There is a way to add watchers to a JIRA, but it looks like one need
> >> to have specific privilege to do so. I got error message trying that.
> >>
> >> Dave do you know how one could force sending stuff to dev list from a
> >> JIRA comment?
> >>
> >> Eric
> >>
> >
> >
>

RE: Process of using JIRA vs dev list?

[Steve Varnau <st...@esgyn.com>]

Folks that want to see what is happening in JIRA can subscribe to
issues@trafodion.incubator.apache.org. Why use dev list for the same thing?

--Steve

-----Original Message-----
From: Eric Owhadi [mailto:eric.owhadi@esgyn.com]
Sent: Monday, July 27, 2015 4:10 PM
To: dev@trafodion.incubator.apache.org
Subject: RE: Process of using JIRA vs dev list?

My 2 cts is that this is not scalable. I'd rather send to dev list, and copy
back to JIRA.
Don't know what others think?
Eric


-----Original Message-----
From: Dave Birdsall [mailto:dave.birdsall@esgyn.com]
Sent: Monday, July 27, 2015 5:39 PM
To: dev@trafodion.incubator.apache.org
Subject: Re: Process of using JIRA vs dev list?

Hi,

Looks like with the current permissions set-up for Trafodion JIRAs, anyone
can view the list of watchers for a given JIRA. Committers, PMC members
(including our mentors) and JIRA administrators can manage the watcher list.
So, if you wish, I can add watchers for a given JIRA for you. Of course,
everyone can add themselves as a watcher or remove themselves.

Dave

On Mon, Jul 27, 2015 at 3:27 PM, Dave Birdsall <da...@esgyn.com>
wrote:

> Hi Eric,
>
> Hmmmm... let me look into adding watchers in JIRA. Maybe we can change
> the permissions policy.
>
> Another way to proceed is when you create a new JIRA, you can e-mail
> the dev list (or specific people you think would be interested
> instead) about your JIRA, including a URL pointing to the JIRA, and
> invite them to add themselves as watchers and/or comment there.
>
> Dave
>
> On Mon, Jul 27, 2015 at 3:19 PM, Eric Owhadi <er...@esgyn.com>
> wrote:
>
>> I thought that using JIRA was a great way to collaborate on a topic,
>> and keep the history of conversation searchable and well formatted.
>>
>> However, I think only watchers on a JIRA will see email notification
>> on comments, (not sure about that). If nobody is watching, then it is
>> pointless.
>>
>> There is a way to add watchers to a JIRA, but it looks like one need
>> to have specific privilege to do so. I got error message trying that.
>>
>> Dave do you know how one could force sending stuff to dev list from a
>> JIRA comment?
>>
>> Eric
>>
>
>

RE: Process of using JIRA vs dev list?

[Eric Owhadi <er...@esgyn.com>]

My 2 cts is that this is not scalable. I'd rather send to dev list, and copy
back to JIRA.
Don't know what others think?
Eric


-----Original Message-----
From: Dave Birdsall [mailto:dave.birdsall@esgyn.com]
Sent: Monday, July 27, 2015 5:39 PM
To: dev@trafodion.incubator.apache.org
Subject: Re: Process of using JIRA vs dev list?

Hi,

Looks like with the current permissions set-up for Trafodion JIRAs, anyone
can view the list of watchers for a given JIRA. Committers, PMC members
(including our mentors) and JIRA administrators can manage the watcher list.
So, if you wish, I can add watchers for a given JIRA for you. Of course,
everyone can add themselves as a watcher or remove themselves.

Dave

On Mon, Jul 27, 2015 at 3:27 PM, Dave Birdsall <da...@esgyn.com>
wrote:

> Hi Eric,
>
> Hmmmm... let me look into adding watchers in JIRA. Maybe we can change
> the permissions policy.
>
> Another way to proceed is when you create a new JIRA, you can e-mail
> the dev list (or specific people you think would be interested
> instead) about your JIRA, including a URL pointing to the JIRA, and
> invite them to add themselves as watchers and/or comment there.
>
> Dave
>
> On Mon, Jul 27, 2015 at 3:19 PM, Eric Owhadi <er...@esgyn.com>
> wrote:
>
>> I thought that using JIRA was a great way to collaborate on a topic,
>> and keep the history of conversation searchable and well formatted.
>>
>> However, I think only watchers on a JIRA will see email notification
>> on comments, (not sure about that). If nobody is watching, then it is
>> pointless.
>>
>> There is a way to add watchers to a JIRA, but it looks like one need
>> to have specific privilege to do so. I got error message trying that.
>>
>> Dave do you know how one could force sending stuff to dev list from a
>> JIRA comment?
>>
>> Eric
>>
>
>

Re: Process of using JIRA vs dev list?

[Dave Birdsall <da...@esgyn.com>]

Hi,

Looks like with the current permissions set-up for Trafodion JIRAs, anyone
can view the list of watchers for a given JIRA. Committers, PMC members
(including our mentors) and JIRA administrators can manage the watcher
list. So, if you wish, I can add watchers for a given JIRA for you. Of
course, everyone can add themselves as a watcher or remove themselves.

Dave

On Mon, Jul 27, 2015 at 3:27 PM, Dave Birdsall <da...@esgyn.com>
wrote:

> Hi Eric,
>
> Hmmmm... let me look into adding watchers in JIRA. Maybe we can change the
> permissions policy.
>
> Another way to proceed is when you create a new JIRA, you can e-mail the
> dev list (or specific people you think would be interested instead) about
> your JIRA, including a URL pointing to the JIRA, and invite them to add
> themselves as watchers and/or comment there.
>
> Dave
>
> On Mon, Jul 27, 2015 at 3:19 PM, Eric Owhadi <er...@esgyn.com>
> wrote:
>
>> I thought that using JIRA was a great way to collaborate on a topic, and
>> keep the history of conversation searchable and well formatted.
>>
>> However, I think only watchers on a JIRA will see email notification on
>> comments, (not sure about that). If nobody is watching, then it is
>> pointless.
>>
>> There is a way to add watchers to a JIRA, but it looks like one need to
>> have specific privilege to do so. I got error message trying that.
>>
>> Dave do you know how one could force sending stuff to dev list from a JIRA
>> comment?
>>
>> Eric
>>
>
>

Re: Process of using JIRA vs dev list?

[Dave Birdsall <da...@esgyn.com>]

Hi Eric,

Hmmmm... let me look into adding watchers in JIRA. Maybe we can change the
permissions policy.

Another way to proceed is when you create a new JIRA, you can e-mail the
dev list (or specific people you think would be interested instead) about
your JIRA, including a URL pointing to the JIRA, and invite them to add
themselves as watchers and/or comment there.

Dave

On Mon, Jul 27, 2015 at 3:19 PM, Eric Owhadi <er...@esgyn.com> wrote:

> I thought that using JIRA was a great way to collaborate on a topic, and
> keep the history of conversation searchable and well formatted.
>
> However, I think only watchers on a JIRA will see email notification on
> comments, (not sure about that). If nobody is watching, then it is
> pointless.
>
> There is a way to add watchers to a JIRA, but it looks like one need to
> have specific privilege to do so. I got error message trying that.
>
> Dave do you know how one could force sending stuff to dev list from a JIRA
> comment?
>
> Eric
>