Old Jira Ticket: https://mozilla-hub.atlassian.net/browse/ADDSRV-671

I looked over the main scenarios and some additional (with abuse reports attached) but I'm going to complete it later (noticed something and atm not sure how to interpret that so I'll re-test)

• emails sent to developer at disable are ok ✅
• activity logs are registered but the reason, decision/policy would only be present in the reviewer pages ❓ - not sure if ok reading instructions
• 2nd level approvals have a "Held" activity log ✅
• not sure for 2nd level approvals with "approve content instead" if it's alright that it's not being registered anywhere (activity log or rev tools) ❓

activity log at disable:

More detailed testing:

normal add-on disabled, email is sent, activity log registered ✅
https://reviewers.addons-dev.allizom.org/en-US/reviewers/review-listed/635672

recommended add-on disabled, "proceed with action" from 2nd level approval queue disabled the add-on and sends an email ✅
https://reviewers.addons-dev.allizom.org/en-US/reviewers/review-listed/635673

line add-on disabled, "proceed with action" from 2nd level approval queue disabled the add-on and sends an email ✅
https://reviewers.addons-dev.allizom.org/en-US/reviewers/review/635674

spotlight add-on disabled ✅

• with "approve content instead" action from 2nd level approval queue -> there is no trace of this action into rev tools or activity log ❓
  https://reviewers.addons-dev.allizom.org/en-US/reviewers/review/635675

notable add-on disabled, approve content instead -> does not send an email , content stays enabled ✅
https://reviewers.addons-dev.allizom.org/en-US/reviewers/review-listed/635676

not sure for 2nd level approvals with "approve content instead" if it's alright that it's not being registered anywhere (activity log or rev tools) ❓

Approving instead leads to a silent approval. To me this was intended, but I'm not sure whether the expected behavior was described anywhere, maybe it should be more explicit in the logs. Can you file a follow-up for this and we'll triage it ? Thanks.

About 2nd level approvals with abuse reports:

• there's an abuse report that flags the version in rev tools
• it's rejected/disabled from the manual review queue the version is sent to 2nd level approval queue
• from 2nd level approval queue a decision is taken: proceed or approve

Only after decision is taken in 2nd level approval queue the NHR and due date are cleared from the Manual Review Queue. -> It sounds like it should be the expected behavior but not 100% sure ❓