Start with one real problem.
A customer message, a recorded error, or something you want to change. Give it an owner and a clear next step. Connections can come later.
Give the problem an owner.
Your first result is a real Work Item with an active owner. A slow screen, a confusing checkout, or a repeated question is enough to begin.
Choose the project
Open your workspace setup guide or an empty project and choose a starting path. If you create a project, your chosen path continues afterward.
Describe the change
Create a Work Item with a specific title and the behavior you want to improve. You do not need an ingestion key or a connected provider.
Assign the next step
A workspace owner or administrator can create the Work Item, choose an active owner, and set its priority. Add the next check or decision to the discussion.
The setup guide recognizes the real owned Work Item as your first result. Changing its status alone does not prove the problem is fixed.
Bring customer messages together.
Verified owners, administrators, and members can record or import feedback in an active project. Open Feedback in the project navigation.
Paste the messages
Choose Import feedback for up to 25 messages. Separate them with
---on its own line and choose a category if useful. For one message, choose Record feedback.Review the redacted preview
Choose Preview messages. Check the text and message boundaries. Use Edit messages to correct them, then Confirm import.
Open the saved group
Processing continues in the background. Check the saved, queued, and rejected counts. Choose Review feedback groups to inspect matching messages; your team can correct the grouping.
Connect the work
An owner or administrator can choose Create Work Item, or expand Link existing Work Item to find work in this project. Its status stays visible beside the messages.
Queued messages are not saved feedback yet. The import page reports rejection or expiry and keeps the messages already recorded.
Start from what failed.
Choose the error path in setup. Use the evidence you have now; you can connect your app afterward.
Review the Signal
If the project has a recorded error, open its Signal and inspect the available context. Check what happened, when it began, and any linked work.
Describe the failure
If no error is recorded yet, describe it in a new bug Work Item. Include what happened, what you expected, and steps that reproduce it.
Make the next check clear
Ask an owner or administrator to create or link the Work Item and assign an active owner. Follow the owned-work steps to make the next decision explicit.
To send events from your app, follow the project’s Event intake instructions. Review the available connection paths before choosing a provider.
Try the optional sample.
Explore a labeled Signal and Work Item in a test environment. The sample does not count as a real result, send customer data, or test delivery from your app.
Run the built-in check
Create a test key
In the workspace setup guide or project overview, expand Try an optional sample. Create a non-production test key and save its secret when shown; it is displayed only once.
Queue the sample
Open Event intake, choose the test key, and select Queue sample error. A workspace owner or administrator must perform this step.
Follow the result
Check the request status on Event intake. When it finishes, open the Signal and linked Work Item. Both remain labeled as sample records.
Get unstuck.
Check the workspace and project in the header first. Then find the step that needs attention.
I cannot see an action
Actions depend on your role. Ask a workspace owner or administrator if you need access. Creating owned work and sending the optional sample require one of those roles.
The sample has no result yet
Check the request status on Event intake before queuing another sample. If it failed, use the reported error and available recovery action. You can also start with a Work Item.
Feedback is empty
Verified owners, administrators, and members can Record feedback or Import feedback. Follow the import steps and check the saved count. An owner or administrator can then create or link work. Anonymous widgets and attachments are not available yet.
A connection is saved, but no data arrived
A saved provider mapping records setup details; it does not activate provider access. For GitHub, choose Connect GitHub on the project’s Connections page and authorize repositories for reading. Review its status after returning. For app events, follow Event intake.
I cannot find a Work Item
Open Search and enter a phrase from its title or description. Work Items search includes archived work; the Work items list normally shows active work.
Still stuck? Contact us with the step you reached and the error message. Leave out passwords, keys, and customer data.
One problem. One owner. A next step.
Choose the work your team can act on first.