@GMikesell-WMF - AC2 is OK by me. I think the fuzzy search is useful.

Update: since we cannot reliably place server messages contextually to specific form fields, we are going to remove this task and put it in our backlog.

A few thoughts here.

I think it's OK to scroll in to the top of the page. When a username or IP address is typed in, don't we populate the data to see if there are active blocks?

Is this suggesting an admin can search a block via blockID?

@MusikAnimal just so I understand the scope of this task... It sounds like this represents the need for an admin to edit or modify an existing block. The use case is that an admin looks up a username and IP address, and then clicks a button, which loads the existing block, which could be updated?

This proposal makes sense without "codexifying" it.

@Theklan - we've explored the newcomer use case as well on a few different paths.

CommTech is planning to address some of this with Favorite Templates

Hey @ovasileva @Jdlrobson this is a seemingly smaller wish and would be impactful to making iterative and responsive progress via the Wishlist. Any way to prioritize it in the next 1-2 months?

@MusikAnimal could you share why we need to throttle the API requests? What are the potential states that you're suggesting we need?

@Prototyperspective wanted to reply to your comment re: the wishlist.

Updated requirements:

Moving this to our backlog as we haven't seen it in production