You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Benedict Elliott Smith <be...@apache.org> on 2019/04/08 12:55:42 UTC
Jira: Author Field
A couple of people have recently raised the possibility of an Author field in JIRA, that permits multiple authors (much like we now support multiple reviewers).
Unfortunately this can never be quite as clean as Reviewers, as Assignee is a core Jira field and cannot be replaced entirely by Authors. However, when we (hopefully later) get the ScriptRunner add-on, we might be able to manage it transparently.
In the meantime, I don’t see any harm in introducing an Author field anyway. Does anyone have any objections?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Jira: Author Field
Posted by Benedict Elliott Smith <be...@apache.org>.
I think it’s just for people to know who is responsible for the work, much the same as for Reviewers. This can be useful to know before commit, and also to have a more easily queried source of the knowledge than in Git. It also permits searching in Jira for tickets by a particular person, and producing reports on said data (say).
FWIW, I’ve also got no strong pre-conceived position on this, I’m just bringing forward a request I’ve had made a couple of times off the back of the Jira changes. But, multi-author tickets seem to becoming a bit more common, and are something we should perhaps be encouraging. It’s also easiest to do now, while we’re in flux.
> On 8 Apr 2019, at 14:01, Joshua McKenzie <jm...@apache.org> wrote:
>
> What problem are we trying to solve w/this proposed change?
>
> Is the thinking for live querying of things in progress, or is the thinking
> for after-the-fact research to determine who wrote a thing to reach out to
> them for context? If the latter, does a change in JIRA metadata give us
> more context than good git commit message hygiene (i.e. list all authors on
> commit msg)?
>
> fwiw, no religion on the topic here. Just curious.
>
>
> On Mon, Apr 8, 2019 at 8:55 AM Benedict Elliott Smith <be...@apache.org>
> wrote:
>
>> A couple of people have recently raised the possibility of an Author field
>> in JIRA, that permits multiple authors (much like we now support multiple
>> reviewers).
>>
>> Unfortunately this can never be quite as clean as Reviewers, as Assignee
>> is a core Jira field and cannot be replaced entirely by Authors. However,
>> when we (hopefully later) get the ScriptRunner add-on, we might be able to
>> manage it transparently.
>>
>> In the meantime, I don’t see any harm in introducing an Author field
>> anyway. Does anyone have any objections?
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Jira: Author Field
Posted by Benedict Elliott Smith <be...@apache.org>.
Ok, there’s now an ‘Authors' field
> On 8 Apr 2019, at 15:03, Joshua McKenzie <jm...@apache.org> wrote:
>
>>
>> It also permits searching in Jira for tickets by a particular person
>
> That makes sense from an attribution perspective. Certainly easier than
> git grepping (low bar on usability, that).
>
> Having a multi-user Authors field, in addition to the multi-user Reviewers
>> field that we already have, allows to more accurately reflect on the ticket
>> who contributed in what capacity.
>
> Also gives us symmetry / consistency, which scratches my OCD itch.
>
> +1 from me.
>
> On Mon, Apr 8, 2019 at 9:18 AM Aleksey Yeshchenko <al...@apple.com.invalid>
> wrote:
>
>> Some of it is just for clear attribution.
>>
>> Occasionally, you do get an extensive review that borders on
>> authoring/coauthoring.
>>
>> Sometimes you get a large body of work co-created by several people in
>> author capacity.
>>
>> Having a multi-user Authors field, in addition to the multi-user Reviewers
>> field that we already have, allows to more accurately reflect on the ticket
>> who contributed in what capacity.
>>
>>> On 8 Apr 2019, at 14:01, Joshua McKenzie <jm...@apache.org> wrote:
>>>
>>> What problem are we trying to solve w/this proposed change?
>>>
>>> Is the thinking for live querying of things in progress, or is the
>> thinking
>>> for after-the-fact research to determine who wrote a thing to reach out
>> to
>>> them for context? If the latter, does a change in JIRA metadata give us
>>> more context than good git commit message hygiene (i.e. list all authors
>> on
>>> commit msg)?
>>>
>>> fwiw, no religion on the topic here. Just curious.
>>>
>>>
>>> On Mon, Apr 8, 2019 at 8:55 AM Benedict Elliott Smith <
>> benedict@apache.org>
>>> wrote:
>>>
>>>> A couple of people have recently raised the possibility of an Author
>> field
>>>> in JIRA, that permits multiple authors (much like we now support
>> multiple
>>>> reviewers).
>>>>
>>>> Unfortunately this can never be quite as clean as Reviewers, as Assignee
>>>> is a core Jira field and cannot be replaced entirely by Authors.
>> However,
>>>> when we (hopefully later) get the ScriptRunner add-on, we might be able
>> to
>>>> manage it transparently.
>>>>
>>>> In the meantime, I don’t see any harm in introducing an Author field
>>>> anyway. Does anyone have any objections?
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>>>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Jira: Author Field
Posted by Joshua McKenzie <jm...@apache.org>.
>
> It also permits searching in Jira for tickets by a particular person
That makes sense from an attribution perspective. Certainly easier than
git grepping (low bar on usability, that).
Having a multi-user Authors field, in addition to the multi-user Reviewers
> field that we already have, allows to more accurately reflect on the ticket
> who contributed in what capacity.
Also gives us symmetry / consistency, which scratches my OCD itch.
+1 from me.
On Mon, Apr 8, 2019 at 9:18 AM Aleksey Yeshchenko <al...@apple.com.invalid>
wrote:
> Some of it is just for clear attribution.
>
> Occasionally, you do get an extensive review that borders on
> authoring/coauthoring.
>
> Sometimes you get a large body of work co-created by several people in
> author capacity.
>
> Having a multi-user Authors field, in addition to the multi-user Reviewers
> field that we already have, allows to more accurately reflect on the ticket
> who contributed in what capacity.
>
> > On 8 Apr 2019, at 14:01, Joshua McKenzie <jm...@apache.org> wrote:
> >
> > What problem are we trying to solve w/this proposed change?
> >
> > Is the thinking for live querying of things in progress, or is the
> thinking
> > for after-the-fact research to determine who wrote a thing to reach out
> to
> > them for context? If the latter, does a change in JIRA metadata give us
> > more context than good git commit message hygiene (i.e. list all authors
> on
> > commit msg)?
> >
> > fwiw, no religion on the topic here. Just curious.
> >
> >
> > On Mon, Apr 8, 2019 at 8:55 AM Benedict Elliott Smith <
> benedict@apache.org>
> > wrote:
> >
> >> A couple of people have recently raised the possibility of an Author
> field
> >> in JIRA, that permits multiple authors (much like we now support
> multiple
> >> reviewers).
> >>
> >> Unfortunately this can never be quite as clean as Reviewers, as Assignee
> >> is a core Jira field and cannot be replaced entirely by Authors.
> However,
> >> when we (hopefully later) get the ScriptRunner add-on, we might be able
> to
> >> manage it transparently.
> >>
> >> In the meantime, I don’t see any harm in introducing an Author field
> >> anyway. Does anyone have any objections?
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> >> For additional commands, e-mail: dev-help@cassandra.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>
Re: Jira: Author Field
Posted by Aleksey Yeshchenko <al...@apple.com.INVALID>.
Some of it is just for clear attribution.
Occasionally, you do get an extensive review that borders on authoring/coauthoring.
Sometimes you get a large body of work co-created by several people in author capacity.
Having a multi-user Authors field, in addition to the multi-user Reviewers field that we already have, allows to more accurately reflect on the ticket who contributed in what capacity.
> On 8 Apr 2019, at 14:01, Joshua McKenzie <jm...@apache.org> wrote:
>
> What problem are we trying to solve w/this proposed change?
>
> Is the thinking for live querying of things in progress, or is the thinking
> for after-the-fact research to determine who wrote a thing to reach out to
> them for context? If the latter, does a change in JIRA metadata give us
> more context than good git commit message hygiene (i.e. list all authors on
> commit msg)?
>
> fwiw, no religion on the topic here. Just curious.
>
>
> On Mon, Apr 8, 2019 at 8:55 AM Benedict Elliott Smith <be...@apache.org>
> wrote:
>
>> A couple of people have recently raised the possibility of an Author field
>> in JIRA, that permits multiple authors (much like we now support multiple
>> reviewers).
>>
>> Unfortunately this can never be quite as clean as Reviewers, as Assignee
>> is a core Jira field and cannot be replaced entirely by Authors. However,
>> when we (hopefully later) get the ScriptRunner add-on, we might be able to
>> manage it transparently.
>>
>> In the meantime, I don’t see any harm in introducing an Author field
>> anyway. Does anyone have any objections?
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> For additional commands, e-mail: dev-help@cassandra.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org
Re: Jira: Author Field
Posted by Joshua McKenzie <jm...@apache.org>.
What problem are we trying to solve w/this proposed change?
Is the thinking for live querying of things in progress, or is the thinking
for after-the-fact research to determine who wrote a thing to reach out to
them for context? If the latter, does a change in JIRA metadata give us
more context than good git commit message hygiene (i.e. list all authors on
commit msg)?
fwiw, no religion on the topic here. Just curious.
On Mon, Apr 8, 2019 at 8:55 AM Benedict Elliott Smith <be...@apache.org>
wrote:
> A couple of people have recently raised the possibility of an Author field
> in JIRA, that permits multiple authors (much like we now support multiple
> reviewers).
>
> Unfortunately this can never be quite as clean as Reviewers, as Assignee
> is a core Jira field and cannot be replaced entirely by Authors. However,
> when we (hopefully later) get the ScriptRunner add-on, we might be able to
> manage it transparently.
>
> In the meantime, I don’t see any harm in introducing an Author field
> anyway. Does anyone have any objections?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: dev-help@cassandra.apache.org
>
>