Skip to main content

1. Create an account

Go to app.getwaterline.dev/auth and sign up with your email and password. After confirming your email, you’ll be prompted to create a workspace — name it after your organization or project.

2. Connect a GitHub repository

1

Click Connect GitHub

From the dashboard, open Settings → Integrations → GitHub and click Connect GitHub.
2

Grant repository access

On the GitHub authorization page, select the repositories you want Waterline to access. You can start with one and add more later.
3

Select a repo to connect

Back in Waterline, choose which repository to connect to this workspace. Waterline registers a webhook and begins indexing immediately.
4

Wait for indexing

Waterline builds a semantic index of your codebase. For most repos, this takes 5–15 minutes. Progress is shown in the dashboard.
Waterline never pushes code, creates branches, or modifies your repo.

3. Connect your issue tracker

Jira

Go to Settings → Integrations → Jira and click Connect Jira. You’ll complete the Atlassian OAuth flow. No admin permissions needed.

GitHub Issues

Go to Settings → Integrations → GitHub Issues and toggle it on. No separate OAuth required.

Asana

Go to Settings → Integrations → Asana and click Connect Asana. After connecting, select which projects to sync and click Sync tasks.

4. Analyze a ticket

Once the repo index is ready:
  1. Go to Analyze in the sidebar
  2. Select your issue tracker (Jira, GitHub Issues, or Asana)
  3. Enter a ticket key or task GID
  4. Select the repository
  5. Click Analyze
Results arrive in seconds when cached, or 10–30 seconds for a fresh analysis. You’ll see:
  • Overall progress % — how much of the ticket is implemented
  • Per-criterion breakdown — SATISFIED / PARTIAL / UNSATISFIED for each acceptance criterion
  • Evidence list — the specific functions and classes behind each score

5. The index stays current

Waterline’s webhook keeps the index in sync automatically. Every push to any branch triggers an incremental update — no manual action needed. Processing typically completes within a few minutes.

Next steps