Some initial feedback: Your homepage demo launches with someone entering Task #1. Task #1 isn't the problem, the problem is Task #5509 opened yesterday child of Task #803 opened two years ago and subsequently deferred by people who no longer work at the company who pointed to a planned technology project that has since been cancelled.
Everyone does Task #1 fantastically. Task #1 is easy, it's greenfield by definition.
How does your solution scale to Task #5509 when things have gone pear-shaped and there are legacy considerations that demand consideration?
The idea here is the "Roadmap" view you're seeing only shows tickets which are not completed. You might have Phase 1 -> Bugs (e.g. #803) opened 2 years ago and not closed if you choose to organise them that way but the Task #5509 comes, get completed then is removed from the view.
Still playing with how to scale projects across multiple departments and show only the tasks your team cares about though, which would make that view even smaller. Right now I'm thinking either by being able to filter on any single Task or just use the existing Labels. Thinking about how to do this without bloating the language with Teams or Squads etc. though is interesting.
Everyone does Task #1 fantastically. Task #1 is easy, it's greenfield by definition.
How does your solution scale to Task #5509 when things have gone pear-shaped and there are legacy considerations that demand consideration?