Ok, there’s now an ‘Authors' field
> On 8 Apr 2019, at 15:03, Joshua McKenzie 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
>
> 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, all
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
fiel
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
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 th
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 Autho
