Aha offers a ton of tools for creating, assigning, managing, and getting an overview of projects & their tasks. If you don't like one way it presents that information, you're sure to find a couple of different views that might give you what you want.
I was not using the high-level project timeline and overview pages, but they seemed like they could be helpful for someone who's overviewing multiple teams.
Their support team was very responsive, but did tend to ignore some problems even when presented with a solution and offers to work with them.
All of the tools it does offer are cluttered, over-complicated, and half-baked. There's not a good way to keep your focus to a single project (Referred to as a "release" in Aha!). You're either in the board that shows all of the features (What Aha! calls the top-level tasks in a release) for all of your releases, in the detailed view for 1 release which removes functionality like reordering priority, or you're on their attempt at a Kanban board which shows everything for all members, even ones who have no part in the current release you're looking at. With a team of ~30 members, having a board that shows 30 people for a project of 3 is just untenable.
Aha also doesn't seem to take a stance on how its features should be used. A "release" is comprised of "features", which can have attached the them "requirements" and "to-dos". Requirements MUST live on features, but to-dos can live outside of features. Todos and requirements have different fields which I always find myself wanting a combination of the two. And given all this, Aha offers no suggestion of how you should be structuring your projects. This caused every project in my organization to be managed in a different way, often leading to ignoring either todos, requirements, or both.
They also charge per user based on that user's permissions. We work in a very flat organization where everyone tends to have complete control, but because Aha gets costly when everyone's an admin, we had to bottleneck our flow to a few people who had full control.
For the usability issues, I resorted to writing a chrome extension to try and help people out on my team. You can find it here, though I've ceased development since we have stopped using Aha https://chrome.google.com/webstore/detail/hgohigknlcabobkokchfabjikhjhklgm/publish-accepted
Try using it and see if it makes sense to you. But don't try to force yourself to work in its ecosystem, if it's not working, it probably won't get better.
We're a product team that splits of developers and designers in to small teams to complete features for our product. These teams usually consist of 2-4 people in a team of ~30. Aha was good for keeping us all in the same system, but it was a complete mess within each team's organization of the individual projects.