Where to See Your Reported Issues
2 min read
Last updated
DevelopersWhat's new
When your team reports a coding problem, you can follow it to delivery. Go to https://docs.hank.ai/updates to see the issues your organization reported.
Sign in with your Hank console account. The updates page uses the same single sign-on as every HANK product. No separate password exists.
The page is scoped to your organization. You see the issues your organization reported. You do not see other organizations' issues.
Each issue on the page carries:
| 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 page shows the deploy 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 deploy 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 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 on the updates page after triage. A new issue is not visible on the page immediately.
Auditors can use the updates page as the delivery record for reported coding issues. Each row shows what your organization reported and the state of its fix. The deploy date on a Deployed issue gives the date the corrected behavior went live.