Help / Field guide
Feedback that stays in context
Pin, reply, resolve and reopen without losing the release or your draft.
Place a pin
Open the authorized release and use its feedback controls to select a point or element. Add enough detail to explain the change. The pin belongs to that release; moving to a different release does not rewrite its original evidence.
Continue the conversation
Open a thread to reply. Assignment and thread decisions depend on the permission returned for the current review. A read-only viewer can inspect feedback but cannot post simply because a control exists elsewhere.
Resolve is not approval
Use Resolve when the thread is addressed, and Reopen when it needs more work, if your role allows those actions. Closing or resolving a thread is separate from approving the release. Open feedback can require an explicit confirmation and reason before approval.
Keep unsent work safe
Drafts can remain in this browser and are scoped to the review and identity. A draft is not a posted comment. If a request is interrupted, check the recovered server state before repeating it. Do not clear browser data while recovering unsent work.