Is it possible to trigger a custom pipeline from the Pull Request Details view, scoped to the PR's b

[Panos Pagonis]

Hello,

We have a repository that uses Bitbucket Pipelines with custom manually triggered pipelines. 

A common need we run into is being able to trigger a specific pipeline directly from the Pull Request Details view — similar to how Approve, Merge, or Decline are available — without having to navigate away to the Pipelines section.

Our specific use case:
- We have multiple manually triggered pipelines, each intended for a different branch naming convention (e.g. pipeline-1 for xe/* branches, pipeline-2 for mjn/* branches).
- When viewing a PR, we'd like only the relevant pipeline(s) to appear as options, determined by whether the source or destination branch matches the convention that pipeline is designed for.

This would significantly improve the CI/CD experience by keeping pipeline execution contextual to the PR being reviewed, rather than requiring engineers to manually locate the right branch and pipeline elsewhere in the UI.

I understand this may be two separate asks:
1. Surface manually triggered pipelines as an action within the PR Details view.
2. Allow pipelines to declare a branch pattern they apply to, so only relevant pipelines are shown per PR.

Happy to elaborate further if useful. Voting on this and adding our use case in hopes it gains traction. 🙏

[Saxea _Flowie_]

Hi @Panos Pagonis ,

This is currently not possible. You could try extending Bitbucket yourself to achieve something like this.

Alternatevely, we provide Flowie, which is an Bitbucket app that adds more options around triggering the pipelines and restricting it to specific branches. We don't have a manual trigger yet, but usually you can implement workflows using label events to trigger it instead.

[Aron Gombas _Midori_]

@Panos Pagonis 

There is no out-of-the-box feature for this use case.

You could:

• Build a Bitbucket Forge app. Forge allows you to add custom UI extensions to Bitbucket, including on the PR page. You could build an app that reads the PR source branch, determines which custom pipelines are relevant based on your naming conventions, and presents buttons to trigger them via the API.
• Then use the Bitbucket Pipelines API to trigger a custom pipeline on a specific branch programmatically. The endpoint is POST /2.0/repositories/{workspace}/{repo_slug}/pipelines with a request body specifying the custom pipeline and the target branch ref.