When your team reports a coding problem, you can follow it to delivery. Go to [Your updates](/changelog#your-updates) to see the issues your organization reported.

## Where to find it

"Your updates" is a section of the Changelog page. The Changelog page is public. It carries the release notes for every HANK product, newest first. You can filter the releases by product and by release status. Each product also has its own changelog page with a status table.

"Your updates" sits below the release notes on that page. The link above takes you straight to the section.

## Sign in

Sign in with your Hank console account. The Changelog page uses the same single sign-on as every HANK product. No separate password exists.

If you are signed out, the section shows a **Sign in** link. Select the link and sign in. The rest of the Changelog page stays open to everyone, so you only sign in for this section.

The section is scoped to your organization. You see the issues your organization reported. You do not see other organizations' issues.

## What each issue shows

Each issue in the section shows:

- A plain-language title. The title describes the coding problem, not the internal engineering work.
- A short summary, when one is available.
- The product the issue applies to, when the issue names one.
- A delivery status.
- A target release date, when the team can commit to one. This date is optional and can change.
- The delivery date, after the fix goes live.
- The date of the last activity on the issue.

Some rows carry a **Platform** tag. A platform row is product work for every customer. It is not a request from your organization.

## The status ladder

| Status | What it means |
|---|---|
| Open | Your organization reported the issue. Work on a fix has not started. |
| In progress | The team is building a fix. |
| Fix merged | The fix is written and accepted. It waits for the next deployment. |
| Deployed | The fix is live in production. The section shows the delivery date. |

Read the ladder in order. A status only moves forward.

Note the difference between **Fix merged** and **Deployed**. A merge is not a deployment. HANK CODES deploys on a separate schedule, so a merged fix can wait before it changes your results. Use **Deployed** and its delivery date as the point where you expect new behavior.

An issue can also show as closed. A closed issue was reviewed and will not get a fix, for example because the reported behavior is correct.

## Report a new issue

Report new issues to your Hank representative. Give the affected codes, the specialty, and what you expected instead. Your representative records the issue. The issue appears in the section after triage. A new issue is not visible in the section immediately.

## Use for audits

Auditors can use the section as the delivery record for reported coding issues. Each row shows what your organization reported and the state of its fix. The delivery date on a Deployed issue gives the date the corrected behavior went live.