Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Find source pipeline for a triggered pipeline

Jon Bevan _Adaptavist_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 26, 2023

We've migrated a lot of builds from Bamboo to Bitbucket Pipelines.

In order to keep our monorepo but have many parallel build pipelines for different parts of the repo we're using the atlassian/trigger-pipeline pipe extensively.

When viewing builds for a repository which is triggered by the pipe, it's really hard to find out which source build pipeline triggered the pipeline.

We could update each of our atlassian/trigger-pipeline usage to include a source repo/build variable but it would be a lot more consistent if this was a feature that came out of the box somehow

1 answer

1 vote
Igor Stoyanov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 27, 2023

@Jon Bevan _Adaptavist_ hi. Thanks for your suggestion. We will think about how to implement this, and we will notify you, when this feature will become available.


Regards, Igor

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events