Bugs and feature requests
You reported it. You will hear what was done.
The team you reported to uses FEATit. Their own rules decide who handles your report, a person, an AI agent or both, and what it must pass before they call it done. Nothing is asked of you here.
What happens to your report
You hear what was done
Once the work is released, you hear what was done and in which release, in words, not as a status change.
Questions reach you
If the team needs more from you, the question reaches you, and your reply goes straight to the work it is about.
Confirm it, if it matters to you
If the problem is critical for you, you can ask to confirm the fix yourself. Nobody else is asked to.
An AI agent says so
When an AI agent writes to you about your report, its message is labelled as AI.
Your report belongs to the team you sent it to, and their privacy policy applies. Ours covers what FEATit itself stores. FEATit’s privacy policy
You asked to check the fix yourself: critical — month-end close.
Check it works for you
- Yes, it works
- No, still broken
LenaWed 10:40
For teams
Bring the people who asked into the work.
Customers, testers and stakeholders are part of the work, not an inbox beside it. They file, follow their request and hear what was done once it is released, all without a seat.
Known by name
Each reporter is known by name and has their own conversation, so a question or a reply reaches the person, not a shared inbox.
Everyone who asked hears back
Requests are linked to the idea they support, so when it is released, every person behind it hears what was done.
Public work areas
Make a work area Public, and the people you serve can find it and follow the work. They join at the role you choose, or ask you for access.
No seat for the people who ask
Reporters and testers take no seat, with generous free limits on every plan.
Let everyone who asked hear back.
Bring your customers into the work, and tell each of them what was done.