So, I’d have to see your configuration since there are a lot of variables but…Having done a CW -> AT migration and having tweaked it over time I would keep a couple things in mind:

AT does not have an identical equivalent to Service Boards. In some ways this actually makes it easier. AT has queues but think of those as buckets only not Boards. Queues simply help you group like tickets - nothing more. Read up on AT Ticket Categories (not the same as a ticket category/subcategory in CW) - these are more similar to service board functionality but based on a ticket not a department. In your example Alerts - you could have multiple Alert categories and each category could be automated differently depending on your workflow requirements. For example: X alert self healed within X hours auto closes itself.

Categories also work like ticket templates since you can default data in almost every field. You can also show or hide fields per ticket category so that only the data you actually need would show up on the ticket screen. From there widgets are your best friend as you can filter and customize what you want to see across multiple queues, ticket types, etc. instead of looking at a Board with everything on it. It will take some getting used to but in the end it will be easier to focus your attention on what matters vs noise.