The problem is that when feedback is first submitted, it goes into open status as well, so it's hard to keep new, unreviewed feedback distinct from items in Open status - items we are not actioning on at this time but could at some future date. Potential solutions: 1) Add a Backlog status. I'm not sure "Backlog" is the right word, but it would be nice to have a status other than "open" that indicates we're not going to do anything with this feedback in the near future 2) Add a New status that feedback goes into first instead of Open. That way, we can review all New feedback, take action on it, and move it to Open if we plan to keep it around for comment without actioning on it for awhile. The custom statuses request could also accomplish this, but okay with something more lightweight in the meantime.

When people come to our board, the title is not always enough to give them context about what kind of feedback we keep on that board vs. another board. It would be great if we could give users a little more context, via some kind of board description visible to end users that could be edited.

Let us customize the names of the statuses. Specifically I want to change "Under Review" to "Researching" or "Scoping". "Under Review" sounds like the post is under review and might get deleted

Similar to https://feedback.canny.io/feature-requests/p/being-able-to-vote-on-behalf-of-your-users, except for creating posts.

When adding manually a voter, I'm not always sure if it's the right person. It'd be nice to have also the email preview with the name of the user. Only when adding it (in the admin view), not in the list of voters of course because that is public.

It’s often we see feature requests that are depending on other features to be completed first. It would be helpful for our users to see what features need to be completed before another feature can get started. Having a simple label with a list of features that the current post depends on below would be useful. I made a quick mockup to give you an idea of what I mean.

We currently have 10 boards and each day we delete/merge different posts across these boards. When dug deeper, found that when creating a post, the current board is search and not all of them.

It would be great if we could also embed the roadmap via a widget just like we can with the boards.

It would be great to be able to set the order in the roadmap column? I'm fairly confident our users would assume there's an order of implementation implied by the order (and we'd like to be able to do that). Would a drag and drop option be possible? Failing that shorting alphabetically so we can do a 'a) Feature X', 'b. Feature Y' type workaround?