I would also find it very valuable to be able to execute certain independent steps before and after an import of a pipeline.

Setting up dynamic pipelines and using forge to achieve this, seems to be like a lot of overhead.

we need this 

Hello! We need a simple solution to replicate pipeline steps. The most obvious solution would be to use an "export" and "import" mechanism. In fact, this feature exists in platforms like GitLab and GitHub. The use of the "Dynamic Pipelines" mechanism should be an option and not the only solution to this problem.

If you are looking for an example of how to achieve this with Dynamic Pipelines, you can check out the following resources which include the link to a repository with a reference implementation for you to get started:

• Article on Community: https://community.atlassian.com/t5/Forge-for-Bitbucket-Cloud/Share-a-step-across-pipelines-Dynamic-Pipelines/ba-p/2712403
• YouTube video: https://youtu.be/YwnpPm_bpX8

Dear bitbucket team,

Clearly, the person who designed the shared pipelines solution never had to configure one. Importing the entire pipeline is overly complex because you need to design a complete pipeline for every single modification you need.

It's not that complicated to replicate the functionality that other CI/CD solutions offer, allowing us to add only the steps we need to execute. SIMPLE!!!

---------
Requirements:

One repository to define steps (security, test, build (python, flutter, go, java), deploy)
Import only the steps you need into your repository, meaning you build the pipeline from the service/app repo.
---------

You should consider changing your product owner; this functionality is fundamental for configuring pipelines across a large number of services!

But as I said at the beginning, the person who designed this solution never had to use it!

And the "Dynamic Pipelines" are way too complex for a simple pipeline.

Simple is better!

+1

Please add this feature. shared pipelines provide a simple way to centralize pipelines and make it much simpler to manage them at large. However without this feature, it can be extremely limited in some scenarios. From a user perspective it's basically a must have

Hi all - with the release of Dynamic Pipelines a few weeks ago, there is now a range of new capabilities available for sharing and reusing modular blocks of Pipelines functionality.

Info: https://bitbucket.org/blog/introducing-dynamic-pipelines-a-new-standard-in-ci-cd-flexibility

Dynamic Pipelines allows you to carve up your Pipelines at whatever level of granularity works for your teams, reuse and share config via industry standard tools like NPM Packages, and reuse logic through sharing Dynamic Pipelines apps across multiple repos.

+1

Please add this, way more useful. 

Really needed, the current export/import of an entire pipeline has very little application. Reusing steps is far more beneficial.