Closed Bug 1060226 Opened 10 years ago Closed 9 years ago

Automatically add reviewer's name to reviewed patches

Categories

(MozReview Graveyard :: General, defect, P4)

Product:
MozReview Graveyard
Component:
General
Version:
Production
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1160479

People

(Reporter: bwu, Unassigned)

References

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2817] ) 

Currently when a patch has been reviewed, submitter needs to add the reviewer's name to the commit message, re-submit a new patch, and make the previous patch obsolete. It looks not smart for everyone to do the same thing. Is there anyway that bugzilla system can help on this reviewer's name addition?
we are close to deploying reviewboard into production for tracking firefox reviews; there isn't much value in addressing this issue in bugzilla.

i don't know if this is still an issue with how things will work once we start using rb; moving to a reviewboard component so those closer to the project can comment.
Status: NEW → UNCONFIRMED
Component: Extensions: Other → rbbz
Ever confirmed: false
Version: Development/Staging → Production
Product: bugzilla.mozilla.org → Developer Services
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2807]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2807] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2815]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2815] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2817]
This will be part of autoland-to-inbound.
Depends on: 1128039
We have too many P1s, so I'm spreading out the priorities.  P3 -> P4, P2 -> P3, and some portion of P1s will become P2.
Priority: P3 → P4
Duping this to the corresponding autoland bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Product: Developer Services → MozReview
You need to log in before you can comment on or make changes to this bug.