Allow One Feedback Post to Belong to Multiple Categories

We previously used Sleekplan as the central place for collecting customer suggestions, internal ideas, and product requests while managing feedback for Wowzers. Overall, it made discussions much easier to follow and gave our team a clear place to review what customers were asking for. The one limitation that consistently created extra work was that a feedback post could only fit into a single category. Many requests naturally crossed multiple areas. For example, a customer might request improvements that affected booking, notifications, and account management at the same time. Choosing just one category meant the request became difficult for the other teams to discover unless someone manually searched for it. We often duplicated posts or copied links between categories just to keep everyone informed, which eventually became difficult to maintain. Why We Left Sleekplan As our feedback volume increased, the single-category structure became a bottleneck in our review process. Product discussions were spread across different areas, and duplicate entries started appearing because different team members categorized similar requests differently. That made prioritization less reliable and required additional manual organization, so we eventually moved to another platform that better matched our internal workflow. Why We're Considering Coming Back We've recently noticed that Sleekplan has introduced several meaningful improvements, and many of the reasons we originally chose it are still appealing. The interface, voting system, and overall experience appear to have matured considerably, so we're evaluating whether it fits our workflow again. Expected Benefit The one feature that would remove our previous obstacle is the ability to assign a single feedback post to multiple categories. This would let cross-functional requests remain as one discussion while still appearing wherever the relevant teams review feedback. It would reduce duplicate submissions, improve visibility across departments, simplify prioritization, and preserve one complete history of comments and status updates instead of splitting the conversation across multiple posts.