# Create or update an issue

Canonical: https://fairleadhq.com/docs/recorder/issue-trackers/

Updated: 2026-10-10
Publication state: published
Product version: Recorder source f6ed5b96

Agent summary: Use Explore, Test case, or Verify fix to create, update, replace, or add evidence to an issue, then verify independent delivery outcomes.

## Prerequisites

- A connected project with a configured tracker destination

## Inputs

- Reviewed evidence, Description, and an issue choice supported by the session type

## Outputs

- A verified tracker mutation with attachment and storage outcomes

## Limitations

- Issue commands, attachments, report storage, and issue status changes are independent

## Permissions

- Project access and required tracker authorization through Control Plane

## Privacy

- Review content and destination before sharing


Choose the session purpose, prepare Description, and send reviewed evidence to a configured tracker.

The tracker actions depend on the recording's session type. Your administrator configures the destination in Control Plane; Recorder never asks you to enter a tracker token or Bridge URL.

## Prepare the destination

[Sign in and select the project](https://fairleadhq.com/docs/recorder/projects/), then choose the appropriate session type:

| Session | Issue lookup | Supported tracker actions |
| --- | --- | --- |
| **Explore** | Optional; empty means a new issue | Create; or Update / Replace description for a selected issue |
| **Test case** | The field holds a test-case ID, not an issue | Failed/Blocked can Create issue or choose No issue; Passed has no issue action |
| **Verify fix** | Required issue | Add evidence only after Fixed/Not fixed is chosen |

For Explore or Verify fix, search or type the issue key. A found issue can fill Title when you have not intentionally changed it. Recorder offers **Add** when the issue has a description; Add appends the text to Description and records its origin. It never replaces your current text or remains synchronized. **Not now** leaves Description unchanged.

For Test case, TMS lookup is unavailable and the typed case ID is never sent as an issue header. A new issue created for a failure includes the case reference and selected result.

## Prepare Description

Description is the unified Markdown account for current local recordings. Include the attempt, build, expected/actual behavior, reviewed evidence, gaps, and next check. It saves after a pause or blur; resolve any save error before sending.

Older stored reports can contain a separate legacy reproduction-notes value. The current local Description editor does not edit that legacy field.

## Choose the send action

After Stop, open the split send menu. Picking an item only changes the primary button; nothing is sent until you press it.

- **Create issue** uses Title and Description.
- **Update ISSUE-123** adds Description as Fairlead's issue section and uploads supported screenshots; Recorder substitutes the selected key.
- **Replace description of ISSUE-123** makes Description the issue description. Use it only after checking current tracker text.
- **Add evidence to ISSUE-123** sends the verification result and Description as evidence. Recorder does not change issue status.
- **No issue** keeps a Failed/Blocked Test case from creating a defect.
- **Send data to Fairlead** stores the report without sending anything to the tracker or TMS.

Creating a linked issue and performing a default fix-verification transition are shown as locked **Soon** actions. They cannot be selected. TMS result delivery is also unavailable.

## Verify and recover

Open the resulting issue and verify its text and attachments. Issue creation/update, screenshot attachments, and report storage can succeed or fail independently. HAR files are not attached automatically; attach a reviewed file manually when needed.

Use a failed attachment's retry control when available. Do not create the issue again because attachment or storage failed. A timeout can leave the command outcome unknown, so check the tracker before retrying to avoid a duplicate.

Use **Download report** for a manual handoff or recovery. See [connection troubleshooting](https://fairleadhq.com/docs/recorder/troubleshooting-connections/) for missing credentials, project access, destination, or compatibility errors.