How to hide or name pipelines for the manual run UI?
Asked by Douglas Knudsen:

I know we can name a custom pipeline and that name will appear in the pipeline choice dropdown in the manual run UI, but how to either name or hide the automatic pipelines?

As seen below I see the branch and pull-requests triggers which are incomprehensible to a user trying to figure out which pipeline to manually run.

![Screen Shot 2022-05-12 at 4.52.14 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/197168i93F30EB3A3165319/image-size/large?v=v2&px=999 "Screen Shot 2022-05-12 at 4.52.14 PM.png")


Answers:
author: Theodora Boudale
body: Hi Douglas,

I'm afraid that it is not possible to either rename or hide certain pipelines from this dropdown. The dropdown will show all pipelines available for the branch you have selected (or for a certain commit, if you are using the **Run pipeline** option of a commit's page). We provide the link **See configuration** next to the dropdown, so a user can view the yml file and details of each pipeline for that branch/commit.

That being said, I can create a feature request about either naming or hiding the automatic pipelines from the dropdown, for our development team to consider.  
Would you like me to proceed with that?  
If so, what would be preferable and more convenient for you? Giving a name to these pipelines? Or having a checkbox in this dialog to show only custom ones?

Kind regards,  
Theodora

comments: author: Douglas Knudsen
body: Yes, thanks! this is not very 'human' readable. Seems it would be following a common pattern to use the 'name' property for that eh? and use the manual property maybe to hide in the drop down?

a checkbox in this dialog to show only custom ones in the run uI could work, but I honestly think naming is better. Consider I want my QA team to manually trigger a build for a branch currently in a PR process and use the 'PR based pipeline' which is not a custom build. We devops devs could work around that though with reusable pipeline blocks ala \<\<: \*nameofpipeline

```
branches:
  'master':
  name: "name of trigger here" 
    - step:
        script: 
           - echo "foo"
        name: "name of a step"
  '{feature/*,bugfix/*}':
  name: "trigger CI build example name to see in run UI"
  'someother/branchpatter':
  manual: false 
```


author: Theodora Boudale
body: Hi Douglas,

Thank you for the feedback!

I went ahead and created a feature request in our issue tracker:

* <https://jira.atlassian.com/browse/BCLOUD-21912>

Please make sure to add your vote to that ticket (by selecting the **Vote for this issue** link) as the number of votes helps the development team and product managers better understand the demand for new features.

You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the **Start watching this issue** link) if you'd like to get notified via email on updates.

Implementation of new features is done as per our policy [here](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html) and any updates will be posted in the feature request.

Kind regards,  
Theodora


Tags: bitbucket-cloud

bitbucket-pipelines

cloud