[FOLIO-1181] Assignee for code review Created: 09/Apr/18  Updated: 10/Jan/19

Status: Open
Project: FOLIO
Components: Documentation
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Julian Ladisch Assignee: Jakub Skoczen
Resolution: Unresolved Votes: 0
Labels: core, sprint44, sprint45, sprint46, sprint47, sprint48, sprint49
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-1119 Add IN CODE REVIEW Status to JIRA Closed
Sprint:
Development Team: Core: Platform

 Description   

I propose this change of our policy: Put the code review assignee into the "Assignee" field.

Our current policy is to put the code review assignee into the "Tester Assignee" field. This is in contrast to Jira's best practice where the person that currently is in charge of the issue should be in the "Assignee" field. The issue list in our roundups are sorted by "Assignee" and do not show the "Tester Assignee".

The information about the people that did the coding is still available in the issues history on Jira and also on the commit history at GitHub.

If this proposed change is accepted, document the new policy at https://dev.folio.org/guidelines/issue-tracker/



 Comments   
Comment by Jakub Skoczen [ 25/Sep/18 ]

Cate Boerema let's discuss this proposal.

Generated at Thu Feb 08 23:11:25 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.