Pull Requests at a Glance, GitHub Issues in Sync
If you work across multiple code repositories, you know the problem: pull requests are scattered across GitHub, GitLab and Bitbucket, and there's no single place to see the full picture. At the same time, issues often live in GitHub while the actual work happens in Spedy. Both of these change now.
Pull Requests — All Providers, One View
Spedy aggregates pull requests and merge requests from GitHub, GitLab and Bitbucket into a single overview. You instantly see what's open, where CI is running, what's failing and what's been merged.
KPI Cards
Five cards at the top of the page show the current state:
- Open PRs — how many PRs are waiting for review
- Running Pipelines — CI jobs currently in progress
- Failed — PRs with failed CI (highlighted in red when > 0)
- Merged This Week — completed PRs from the last seven days
- Success Rate — percentage of PRs that passed CI without failures
Filter and Search
The filter sidebar on the left offers:
- Provider filter — show only GitHub, only GitLab, or only Bitbucket. Providers you haven't connected yet show a link to the integrations page
- State filter — Open, Draft, Merged, Closed
- Quick filters — "Only open" and "Only failed" PRs with one click
- Sorting — by last updated, creation date, or merge date
- Full-text search — across PR titles and branches
Details at a Glance
Each PR in the list shows a provider badge, review status, branch info and CI pipeline as compact dot visualization. Expand a PR to see the description, individual pipeline steps and review comments.
Real-Time and Backfill
New PR events arrive via WebSocket in real time. Additionally, a daily backfill sync (2 AM) catches all open and last-90-days merged PRs — so nothing is missed even if a webhook was lost. Manual sync is available at any time via the API.
Activating the Feature
The PR view is available behind a feature flag. Enable PULL_REQUESTS_VIEW under Settings → Features, and the new "Pull Requests" sidebar entry appears.
GitHub Issues Sync — Your Backlog in One Place
If your team manages issues on GitHub but does the daily work in Spedy, you no longer need to transfer them manually. The new GitHub Issues Sync connects a GitHub repository bidirectionally with a Spedy project.
Two Modes
| Mode | Description |
|---|---|
| Live Sync | Continuous two-way sync via webhooks and configurable polling (5–60 min). New issues become tickets, status changes flow both ways, comments are mirrored. |
| Import Once | One-time import of all matching issues. No ongoing sync — ideal for backlog migrations. |
What Gets Synced
- Status: GitHub issue states (
open,closed) are mapped to Spedy project statuses — and vice versa. Move a ticket to "Done" in Spedy and the GitHub issue closes automatically. - Comments: Bidirectional. Comments on GitHub appear on the Spedy ticket and the other way around.
- Labels → Priorities: Map GitHub labels to Spedy priorities (e.g.
bug→ High). - Direction is configurable: Outbound sync (Spedy → GitHub) is optional. You can also sync inbound only.
Loop prevention ensures changes don't bounce endlessly between systems.
No Separate Provider
GitHub Issues Sync is embedded directly into the existing GitHub integration. You configure it on your GitHub connection's manage page — repo mapping, status mapping and sync options in one place. The configuration page shows sync status, synced tickets and an audit log for every event.
More details in the Integrations documentation.
Better Together
The pull request view and GitHub Issues sync complement each other: issues describe what needs to be done. PRs show what's in progress and what's been completed. Together, they give you a continuous overview — from backlog to merge — without switching between tools.
Over the past weeks, we've also hardened security under the hood. Validations, access controls and webhook handling have been systematically strengthened. No headlines, but important for a product teams rely on every day.
Getting Started
- Pull Requests: Enable the feature under Settings → Features → PULL_REQUESTS_VIEW. Connect GitHub, GitLab or Bitbucket under Settings → Integrations.
- GitHub Issues Sync: Go to Settings → Integrations → GitHub, select a repo and click Configure Issues Sync.