Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Task]: Implement soften and harden block actions in the admin #15084

Closed
2 tasks
diox opened this issue Oct 14, 2024 · 1 comment · Fixed by mozilla/addons-server#22827
Closed
2 tasks

[Task]: Implement soften and harden block actions in the admin #15084

diox opened this issue Oct 14, 2024 · 1 comment · Fixed by mozilla/addons-server#22827
Assignees
Labels
repository:addons-server Issue relating to addons-server
Milestone

Comments

@diox
Copy link
Member

diox commented Oct 14, 2024

Description

Follow-up from #15013

The admin should support a way to directly change a hard-blocked version to being soft-blocked and vice-versa, with full logging/confirmation like other blocklisting actions.

Acceptance Criteria

Milestones/checkpoints

Checks

  • If I have identified that the work is specific to a repository, I have removed "repository:addons-server" or "repository:addons-frontend"

┆Issue is synchronized with this Jira Task

@diox
Copy link
Member Author

diox commented Nov 13, 2024

mozilla/addons-server#22827 has some screenshots of the new UI bits. There are notably new harden/soften buttons when you're viewing a block. It should require the same permissions as for creating a block (Blocklist:Create) and the same sign-off as normal if that's a high adu (> 100k) add-on.

All the changes to the blocklist itself haven't landed, but you should be able to view the changes in the admin once processed. A hard blocked version can be softened to a soft-block, a soft-blocked version can be hardened to a hard-block.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
repository:addons-server Issue relating to addons-server
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant