-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: non dsa add-ons forwarded to Legal Escalations in Cinder don't seem to work with policies that take content down #15278
[Bug]: non dsa add-ons forwarded to Legal Escalations in Cinder don't seem to work with policies that take content down #15278
Comments
@wagnerand would you expect the (promoted|auto-approval-disabled|etc) NHR for the review to be cleared in the reviewer tools if the add-on is forwarded on to legal? (I'm assuming so, but double checking) |
I spoke with Andreas and we decided:
|
Looking at first scenario and trying Ignore/Not enough information policy won't send any email either. |
yes, there isn't any need to try to any other types of decision from cinder - they will all fail. |
What happened?
Followup for #15255 (comment)
And the note from #15259 (comment)
First scenario
Result:
content is not disabled on AMO
Escalate to AMO policy for such an add-on -> won't send back or flag for review the version in rev tools
Second scenario
Result:
add-on is not disabled, the awaiting review versions are still flagged for HR in rev tools.
What did you expect to happen?
Disable content.
Are these add-ons supposed to go in Cinder if there are no reports/appeals attached? Right now any add-on can be forwarded to Legal queue in Cinder.
Is there an existing issue for this?
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: