Your Voice Shapes TeamDay — Introducing the Ideas Board and Bug Reporting
We’ve always read the feedback that comes in through email, Slack, and the occasional carefully worded support ticket. But scattered channels mean things slip through. A great idea buried in a thread. A bug reported twice because nobody knew someone else already filed it.
That ends today.
TeamDay now has a centralized feedback system — bug reporting and a public Ideas board — built directly into the product.
Here’s what’s new and how to get the most out of it.
The Feedback Button
Open TeamDay. Look at the bottom of the left sidebar. You’ll see a chat bubble icon labeled Feedback.
Click it. A modal opens with two tabs:
- Bug Report — for when something isn’t working the way it should
- Feature Idea — for when something you need doesn’t exist yet
That’s it. No external form. No digging through a help center. No emailing support@. Right there, while you’re in the middle of your workflow and the context is still fresh.
How to Write a Good Bug Report
Bad bug reports sound like this: “The thing doesn’t work.”
They’re not helpful because nobody can reproduce them. The faster you can help us reproduce a bug, the faster it gets fixed.
Fill in three things:
1. Title — One sentence that describes what broke. “Export to CSV fails on Spaces with more than 50 files” is better than “Export broken.”
2. Description — This is where the detail lives. Cover these four points:
- Steps to reproduce: What were you doing when it happened? List the exact steps.
- Expected behavior: What should have happened?
- Actual behavior: What happened instead?
- Environment: Which browser and device are you using? Which Space or page were you on?
3. Category — Optional, but helps us route it to the right person faster.
If you can attach a screenshot or screen recording, do it. “The button turns grey when I click it” paired with a GIF of the grey button is worth ten paragraphs of text.
“Steps to reproduce” is the single most valuable thing you can include. If we can’t reproduce it, we can’t fix it.”
How to Submit a Great Feature Idea
The most common mistake with feature requests: describing the solution instead of the problem.
“Add a button that copies the whole conversation to clipboard” is a solution.
“I often need to share a chat summary with a colleague who isn’t on TeamDay, and right now I have to manually copy each message one by one” is the problem — and it’s ten times more useful.
Why? Because when we understand the problem, we might solve it in a better way than the one you imagined.
What makes a strong feature idea:
- Describe the problem first — What are you trying to do? What’s getting in your way?
- Explain your use case — Which team? Which workflow? How often does this come up?
- Keep it focused — One idea per submission. Three good ideas > one bundled mega-idea.
Before you submit, check what’s already there. Visit teamday.ai/support and search for your idea. If it exists, vote for it instead of creating a duplicate. Votes are how we measure demand — and the more votes an idea has, the higher it rises in our planning conversations.
The Ideas Board at teamday.ai/support
Every submitted feature idea is public. Anyone can see it — not just the person who submitted it.
The board shows:
- The idea title and description
- Vote count
- A status badge that tells you exactly where it is in our process
Status badges:
| Status | What it means |
|---|---|
| Open | Submitted and under consideration |
| Planned | Accepted — it’s on the roadmap |
| In Progress | We’re building it right now |
| Completed | Shipped and available in the product |
| Rejected | Won’t be built, with a reason why |
You can sort by Most Voted to see what the community cares about most, or Newest to see what’s been submitted recently.
Bugs are private. Only you and the TeamDay team can see bug reports you submit. Ideas are public by design — shared visibility is what creates shared momentum.
Why Voting Matters More Than You Think
Internally, we have more good ideas than we have time to build. Every week, the list grows.
When we sit down to prioritize, vote counts are signal. Not the only signal — some things need to be built regardless of popularity, like security improvements. But for product features, widespread demand is real evidence that something matters.
If you’ve wanted something for a while, vote for it. A vote takes three seconds and directly influences what gets built next.
You don’t need to be a paying customer. The Ideas board is public — anyone can browse and vote. If you know someone who uses TeamDay and wants the same feature, send them the link. The community’s voice is louder than any individual’s.
What Happens After You Submit
For bug reports:
We review them and triage by severity. Critical bugs — things that block core workflows — jump the queue. We’ll often follow up directly if we need more information. You’ll hear back.
For feature ideas:
They land on the public board as Open. We review them in our planning cycles. When an idea gets accepted, the status moves to Planned. When someone starts building it, it moves to In Progress. When it ships, it moves to Completed — and we try to note what was actually built.
If an idea won’t be implemented, we mark it Rejected with an explanation. We’d rather be honest than leave something hanging in Open indefinitely.
Start Here
Report a bug: Open the app, click the Feedback button in the sidebar, choose Bug Report.
Submit a feature idea: Same button, choose Feature Idea.
Browse community ideas and vote: teamday.ai/support
We built this because scattered feedback means slower progress — for you and for us. A centralized system where the community can see, vote, and track ideas isn’t just a nice-to-have. It’s how good software gets built.
Tell us what’s broken. Tell us what’s missing. We’re listening.