| What you need to say | Use |
|---|---|
| Answer a question about one request | A public comment on that request |
| Discuss a request with your team | An internal comment |
| Tell followers that a request's status changed | A status update with Email followers selected |
| Announce a release to changelog subscribers | A changelog entry with Notify subscribers enabled |
| Explain how to use a feature | A knowledge-base article linked from the update |
Use comment notifications for discussion behavior and status notifications for progress updates. A changelog announcement reaches subscribers to that board, which can differ from the followers of one request.
Personal notification preferences affect optional updates. See which emails are sent before planning a customer announcement.
For an existing feature, a duplicate request or a decision not to build something, follow Reply to feedback and close the loop. That guide covers the response and whether the customer can revisit it. The notification guides explain who receives an email.
For a new release, tell request followers what shipped and decide separately whether to announce it to changelog subscribers. Linking a release note to a request does not itself send that request's followers an update.