It’s simple enough to go to bugs / requests, search to see if my issue is already reported/suggested, and then either upvote & comment on the existing issue or write up my own. But then what? The process can’t stop there or it will be no better than Slack or Trello were.

BUGS

Who applies the “severity” tags to bug reports? Moderators? Will there be any moderators aside from those on the Legend team?
How often do moderators triage the bugs category? Lots of posts have no tags at all aside from the category they are posted in.
There are “low” and “high” priorities but no “middle”. Are there only two grades of severity and no-tag means it hasn’t been graded yet?
What about non-severity tags; can we apply our own tags at all? It appears the forum categories work like google Labels – so a post could exist in multiple categories at once. For example: ‘bugs’ + ‘mobile’. Users could be more helpful by applying relevant tags such as ‘mobile’ and save the moderators from having to do that. Presumably just tagging with ‘bugs’ means mobile, desktop, and web – but what if an issue is only on desktop/web and not mobile (or n/a for mobile because the feature doesn’t exist)? What if a bug appears in both beta and stable – there’s no explicit ‘stable’ tag so how would this be made clear?
Suggestion: add a “reproducible” tag. Having a tag to identify bugs that actually have reproduction steps would let the Team quickly identify “actionable” bugs and knock them out. Yet it would still allow us to document those mystery bugs we can’t quite figure out. Someone later on might encounter it again, search on it, review our notes, and be able to figure out the pattern to actually reproduce. Then they could apply the ‘reproducible’ tag and that bug can find its way into the queue…otherwise those will just never get fixed.

It seems like having a couple more tags and a clear, public process about how they get used could not only allow users to help out the team with more detail for better sorting/triaging, but also take some of the workload off the mods and garner more community engagement.

FEATURES

Will there be any tags used with feature requests so we can see the status of individual requests? Say I have a request, search for it, and find an existing post – it’s 8 months old and has lots of upvotes but has no comments and no tags. I’m going to wonder if you’ve actually “noticed” that request and have it on your roadmap, deferred it for later, dismissed it as being impractical/too difficult, or maybe have overlooked it entirely. If you want folks to search before posting, the things they find need to show evidence that the rest of the process is actually working. If all I ever see are old posts with no upvotes or comments…then we’re back where we were with Trello and Slack. It doesn’t look like you’re paying attention or care. And you’ll probably see more ‘features’ entered as ‘bugs’ because they get more attention that way – which just makes your bug triaging harder.
Feature requests can easily get buried due to lack of interest. If a bug only happens to one person once, nobody will ever search for it, it’ll never get upvotes, and will just get buried – which is appropriate. But feature requests should not be handled the same way. Sure – if someone has the same idea as my request and searches for it, they can upvote and improve the chances of that feature happening. But this means only features that more than one person independently conceive of have any chance of implementation – and that’s not right. A suggestion can be “good” even if only one person thinks of it. If we were all reviewing the “requests” channel regularly and diligently upvoting every post that we liked, there would be no issue – but I don’t think that’s a realistic expectation. I certainly don’t “check in” with ANY forum regularly, and Legend isn’t going to be an exception. If I get an email notification or have something to submit, I’ll look around while I’m here. But I’m not going to just crawl the forum for new posts like its my job. I think you may miss a lot of great suggestions because of this, and you may end up with a big pile of requests that have no tags and no votes, just languishing in purgatory because nobody sees them – which sends the wrong message to the community.
So, suggestion: What if the moderators periodically dug out old posts and highlighted them to the community for feedback? Like once a week? Maybe there is a “weekly digest email” that the forum SW automatically generates, and this can be added to it? Just start with the oldest and surface each post for upvotes and discussion. If it doesn’t hit some threshold, tag it as ‘rejected’ and move on.

GENERAL
Finally, a general question: How will duplicate posts be handled? Can moderators merge or attach them to each other? If I discover two posts about the same thing and each has 3 upvotes, can I ask a mod to combine them into a single post with 6 upvotes?