HAICON Build Tracker

The tracker is the single place for HAICON's feature progress, user acceptance testing (UAT), tickets, client decisions and releases. Everything you change is saved straight away and everyone sees it live, so there's no Save button.

1. Open the tracker link and sign in. First time? Select Create an account and use your work email.
2. Check your role next to the title at the top. If it says "No role yet", you can look around but not change anything. Ask the tracker admin to assign you a role.
3. Start on the Activity tab. "My items" lists what needs your attention, and the feed shows recent changes. A red number on a tab means there are changes you haven't seen.

Report a bug, request a change or ask for help

1. Go to Tickets and select Submit a ticket.
2. Choose the type. Bug / defect is for something that's broken in the live system. Change request is for something new or different. Support is for questions.
3. Add a clear title and a description. For a bug, list the steps to reproduce it. For a change, explain the business reason.
4. Optionally pick the related feature (for example B4-05) and attach screenshots or a short video.
5. Select Submit ticket. You'll get a number like HT-004. Follow progress and reply in the ticket's Activity section.

Found a problem while testing a feature for UAT? Add a UAT note on that feature instead of raising a ticket.

Test a feature (UAT)

1. On the Activity tab, "Ready for UAT" lists features waiting for you. You can also open UAT and select a feature.
2. Read the Acceptance check at the top. It describes what "working" means.
3. Test it in HAICON, then type what you did and what happened under UAT notes and select Add UAT note.
4. Add screenshots or videos as evidence under Add pictures or videos.

Videos must be MP4 or WebM and under 20 MB. iPhone videos are .mov files: share them through an app that converts to MP4, or record a shorter clip. Pictures can be PNG, JPEG, GIF or WebP.

Keep track of things waiting on you

"Waiting on you" on the Activity tab lists tickets where the team needs information from you. Open a ticket and add a comment to reply.

Decisions and sign-off

The Decisions tab shows the questions KoVantage needs you to answer. Release sign-off is recorded by the project coordinator after you confirm it with them. The Releases tab shows what's in each release and how close it is.

Your changes show as "Dev - KoVantage" to everyone, including the client.

Update a feature's build stage

1. On Progress, change the Stage drop-down in the feature's row. You can also open the feature and use the stage buttons.
2. Every change is logged with the date and time in Stage history.
3. If you're stuck, open the feature and tick Blocked, then explain why in General notes. General notes are internal and the client can't see them.

Work a ticket

1. "Tickets assigned to you" on the Activity tab lists your tickets.
2. Change the Status as you go: Triaged, In progress, Waiting on client, Resolved. Each change is logged in the ticket's activity.
3. Comment to update the client. Tick Internal note for anything only the team should see.

UAT

Move the feature's stage to UAT when it's ready for the client, then set the UAT status to In testing. Read client UAT notes on the feature's UAT section. Add your own notes there too, ticking Internal when they're for the team only.

Your changes show as "PC - KoVantage" to everyone, including the client. You can do everything a developer can, plus the tasks below.

Plan releases

1. Open Releases and select a release. Use Edit release to set the target date and acceptance criteria.
2. Under "Add features", filter by module or priority, tick features (or Select all), then Add to release.
3. To move one feature, open it and change Release.

Record client sign-off

1. Check the warning above the sign-off form. It lists features not yet accepted in UAT, open tickets and blocked items.
2. After the client confirms, set Status, Signed off by (for example "Josh, HAICON"), the date, and any conditions.

Run UAT

On each feature's UAT section, record Tested by, Accepted by and dates, and set the UAT status. When a feature is accepted, use Mark stage Done to move it to Done.

Manage tickets

Triage new tickets, then set priority and Assigned to (pick a team member so it appears in their My items) and write the resolution. For an approved change request, select Add to catalogue as a new item to create a CR item that's tracked like every other feature.

Other regular tasks

• Tick Demoed on the Progress tab after a client demo. The date and time are recorded, and you can add notes in the feature.
• Record decision outcomes on the Decisions tab.
• Mark the client's story review (Confirmed, Amend, Remove, Needs discussion) on each feature.
• Create or edit journeys and add steps on Story flows.
• Use Export (top right) for status reports. Exports open in Excel or Google Sheets.

Invite people

1. Send people the tracker link and ask them to create an account with their work email.
2. New accounts can't see any tracker data until you give them a role, so it's safe to share the link.
3. Ask each person to sign in once so they appear under Waiting for a role.

Assign roles

1. Open Access. Search for colleagues by name, or find people under Waiting for a role.
2. Pick Admin, Project coordinator, Dev or Client. People without a role can only view.
3. Only admins can change roles. The database enforces this.

Look after the data

• Only the admin can delete. Deleting a journey, ticket, note, file, release or added catalogue item can't be undone.
• Download Full backup (JSON) from Export regularly, for example weekly.
• Role limits and internal notes are enforced by the database, not just the page: a client can't read internal notes or change anything their role doesn't allow.
• Forgotten passwords: people can use Forgot password on the sign-in screen once email is set up (see the setup guide), or you can reset them in Supabase under Authentication > Users.

Why are the fields greyed out?

Your role doesn't include that action. Check the Access tab to see what each role can do, or ask the admin.

Why does it say "Dev - KoVantage" instead of a name?

Changes by KoVantage developers and project coordinators are shown under a team label, on purpose.

My video won't upload.

Use MP4 or WebM under 20 MB. iPhone .mov files need converting first.

A picture shows as broken.

Picture and video links expire after an hour. Reload the page to refresh them.

Where did a change go?

Check the Activity tab. Every stage change, comment, upload and status change is listed with who made it and when.

Can I work offline?

No. Changes save as you make them and need a connection.