Keep Code and Tasks in One Flow: How Vaiz Tracks Pull Requests Across GitHub and GitLab

Most issue trackers treat code as an attachment on a task. If a developer remembers to put CORE-214 in the branch name or pull request title, the link shows up inside that ticket.

That works when you already know which ticket to open. It breaks down the moment you ask the questions engineering leads, product managers, and QA ask every day:

• What is actually open or waiting for review across all our repositories right now?
• Which pull requests landed in main or release/4.2 today?
• What code is being shipped without a task attached to it?

To answer those questions, we built Code—a dedicated view in the Vaiz sidebar that brings every pull request from GitHub and every merge request from GitLab into one live feed, side by side with the tasks they move forward.

Why Task-Only Code Links Leave Blind Spots

When pull requests only live inside individual task drawers, three things happen in practice:

1. Unlinked work becomes invisible. Hotfixes, dependency upgrades, infrastructure tweaks, and quick refactors often open without a task key in the branch name. Because no ticket references them, they never appear on any board.
2. Multi-repo teams lose the big picture. A modern product rarely lives in one repository. Between cloud-api, web-client, ios-app, design-system, and self-managed GitLab services, checking what is in flight means jumping across half a dozen browser tabs.
3. PMs and QA have to hunt for branch context. Knowing that a task is "In Review" is less useful than seeing at a glance whether its pull request is still a draft, targets main, or was already merged into release/4.2.

How Vaiz Approaches Code Flow (and How It Compares to Linear)

Linear popularized fast GitHub and GitLab linking for engineering teams, and its Reviews view is built as a personal developer inbox—focused on pull requests you authored or were asked to review.

In Vaiz, we designed Code around workspace-wide delivery visibility for the whole product and engineering team:

What You Can Do in the Code View

1. See Every PR and MR in Real Time

Each row in Code gives you the signal you need without opening GitHub or GitLab:

• Status icon & label — color-coded for Open (green), Draft (muted grey), Merged (purple), and Closed (red).
• Number & title — #418 for GitHub pull requests and !128 for GitLab merge requests.
• Repository, author & branch direction — e.g. horizon-hq/cloud-api · alex-chen · feat/CORE-214-webhook-hmac → main.
• Linked Vaiz tasks — clickable task keys that open the task sidebar right over the list.

When a single pull request closes or touches several tasks, Vaiz collapses them into a compact 3 tasks menu so the row stays scannable:

2. Spot Unlinked Pull Requests in One Click

Not every pull request starts from a board. With the Tasks filter, you can switch between:

• With linked tasks — changes traced to a planned task.
• Without linked tasks — pull requests and merge requests that have no Vaiz task attached.

For engineering leads and release managers, this turns release audits from a manual git-log comparison into a two-second check.

3. Curate Which Repositories Appear in Vaiz

Sometimes a GitHub App installation grants access to repositories you don't want cluttering your workspace—archived services, documentation sandboxes, or experimental forks.

In App center → GitHub, you can uncheck any repository without changing your GitHub organization permissions. Unchecked repositories are hidden from Code and task pickers and won't auto-link branches or pull requests.

4. Ask Vaiz AI About Your Code Activity

Because pull requests, branches, and commits are part of the workspace graph, you can ask Vaiz AI Chat questions like "Which PRs were merged into release/4.2 today?" or "What commits are linked to CORE-214?"—and get back interactive links with live PR status icons, branch badges, and short commit SHAs that open directly in GitHub or GitLab.

Get Started with Code in Vaiz

Ready to bring your repositories and tasks into one flow? Follow our step-by-step guides in the Vaiz Help Center:

• How to use the Code view in Vaiz — browse pull and merge requests, filter changes without linked tasks, and curate active repositories.
• How to set up the GitHub integration in Vaiz — connect your GitHub organization, auto-link branches and pull requests by task key, and sync PR activity (or see the GitLab integration guide).