Pipeyard Documentation

Pipeyard is a Jira app that brings Bitbucket Pipelines visibility into Jira. It shows pipeline status, repository activity, and runner health in a single dashboard inside Jira, so teams can track delivery progress without switching tools.

What problem it solves

Engineering and product teams plan and track work in Jira, but CI/CD status lives in Bitbucket. That split creates context switching, slows incident response, and makes it hard for non-engineering stakeholders to see when a build is ready. Pipeyard closes that gap by surfacing the right pipeline data where the work is already being discussed.

Who it is for

Engineering teams that use Jira and Bitbucket Pipelines.
Release managers who need a workspace-wide view of pipeline health.
Product managers and stakeholders who want to understand delivery status without asking for screenshots.
Teams with self-hosted Bitbucket runners that need quick runner status checks.

Key features

Workspace-wide pipeline overview.
Repository-specific pipeline views.
Self-hosted runner monitoring.
Configurable refresh interval.
Secure Bitbucket OAuth connection through Atlassian Forge.
Built-in onboarding and settings.

Supported Atlassian products

Jira Cloud (host application).
Bitbucket Cloud (data source).
Atlassian Forge (runtime and storage).

Supported Bitbucket functionality

Pipeyard reads the following data from Bitbucket:

Repository list and metadata.
Pipeline status (successful, failed, in progress, stopped).
Build details such as branch, commit, duration, and step results.
Self-hosted runner status.

Known limitations

Pipeyard supports Bitbucket Pipelines only. Other CI providers are not supported.
Runner monitoring is limited to self-hosted runners.
A Bitbucket workspace with Pipelines enabled is required.
Source code, build logs, and secrets are not read or stored.

Ready to install? Continue to Getting Started.