Our software department consists of a single-product team of three developers and two higher-ups with domain knowledge whose roles on our team are similar to that of a product owner.
We have organized our backlog into a single Trello board with four columns: Unreviewed, Wishlist, Future, and Soon. New items that come in through our help desk are added to Unreviewed so they can be reviewed, estimated, and sorted into one of the other three columns during our weekly meeting. When we create a new sprint, we populate it with items from the Soon column based on priority and scope of work.
Currently, we've been creating a new board for each new sprint, with the board being named something like "Sprint 6/6/19 – 6/12/19". This makes it easy to see just what's in the sprint and see what everyone's working on, but it also makes it hard to do reporting from a central place. There's also a tendency for long-lived items that take weeks to get through to keep getting kicked to the next sprint once that sprint is complete.
Are these just innate characteristics of multi-board projects, or is there a better way to organize things?