Appearance
Community Board
The Community Board is where you can share ideas, report bugs, suggest improvements, and ask questions about Plan Count. Your feedback helps shape the product roadmap.
Overview
The Community Board lets you:
- Submit feature requests with different post types (Idea, Bug, Improvement, Question)
- Vote on requests to help prioritize what gets built next
- Comment and discuss ideas with other users
- Subscribe to updates on requests you care about
- Filter and search to find relevant requests
Accessing the Board
Navigate to Community Board from the main navigation, or go directly to plancount.ai/feedback.
Submitting a Request
Creating a New Post
- Click the New Post button in the top right
- Choose a Post Type (see below)
- Enter a descriptive Title (5-200 characters)
- Select a Category that best fits your request
- Write a detailed Description explaining your idea or issue
- Click Submit Request
Post Types
Each request is tagged with a type that helps others understand what kind of feedback it is:
| Type | Use For |
|---|---|
| Idea | New feature suggestions or capabilities you'd like to see |
| Bug | Something that isn't working as expected |
| Improvement | Enhancements to existing features |
| Question | Questions about how something works or should work |
The default type is Idea. You can change this by clicking the toggle buttons above the category dropdown.
Categories
Categories help organize requests by product area:
| Category | Description |
|---|---|
| General | Requests that don't fit a specific area |
| Detection | Symbol detection and pattern matching |
| Export | PDF and CSV export features |
| Collaboration | Sharing, teams, and working together |
| User Interface | Layout, design, and usability |
| Integrations | Connections with other tools and services |
Duplicate Detection
As you type a title, the form automatically searches for similar existing requests. If a match appears, consider voting on the existing request instead of creating a duplicate.
Voting
Voting helps prioritize which requests get attention first.
How to Vote
- Click the upvote button on any request in the list or detail view
- Click again to remove your vote
- You must be signed in to vote
Vote Weights
Votes are weighted by your subscription tier:
| Tier | Weight |
|---|---|
| Free | 1x |
| Basic / Growth | 2x |
| Team | 3x |
Higher-tier votes carry more weight in the ranking, so paid users have more influence on priorities.
Browsing and Filtering
Status Tabs
Filter requests by their current status:
| Status | Meaning |
|---|---|
| All | Show all requests |
| New | Recently submitted, not yet reviewed |
| Under Review | Being evaluated by the team |
| Planned | Accepted and scheduled for development |
| In Progress | Currently being worked on |
| Completed | Shipped and available |
| Declined | Not planned at this time |
Post Type Filters
Filter by post type using the pill buttons below the status tabs:
- All Types | Ideas | Bugs | Improvements | Questions
Search
Use the search bar to find requests by keyword. Results match against both titles and descriptions.
Sorting
Requests are sorted by vote count (most voted first) by default. You can also sort by newest or oldest.
Request Detail Page
Click any request to see the full detail view, which includes:
- Post type badge and status badge showing the current state
- Category tag showing the product area
- Full description of the request
- Author name with subscription tier badge
- Date the request was created
- Vote button to upvote
- Subscribe button to get notified of status changes
Comments
Adding a Comment
- Open a request's detail page
- Scroll to the comments section
- Type your comment in the text field
- Click Post Comment
Comments are shown in chronological order. Official responses from the Plan Count team are marked with a special badge.
Subscribing to Updates
Click the bell icon on a request's detail page to subscribe. You'll be notified when the status changes (e.g., from "New" to "Planned").
Click the bell again to unsubscribe.
Tips
- Search before posting to avoid duplicates -- your vote on an existing request is more effective than a new duplicate
- Choose the right post type so others can quickly understand your feedback
- Write clear descriptions that explain the problem you're trying to solve, not just the solution you want
- Vote on requests you care about to help the team prioritize