You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a build plan for a library that publishes the binary as a shared artifact. I have build plans for several applications that consume the library via an Artifact Download task. When the library changes, I want the application build plans to trigger so they re-build against the newer version of the library.
I know I can go the Library plan and add each of the applications as a "Child" plan. That will trigger them. But this seems backwards to me. I shouldn't need to go to a library and add links to each application that consumes it. It would require admin privileges' on that library, even though I'm only a user of it. Ideally the Artifact Download task should already imply a dependency and should act as a trigger.
Do I have the wrong idea here? Why are "child plans" the standard approach when it seems me a "depends on" relationship in the other direction would be more natural?
Hello @Ben Welcome to Atlassian Community!
We have a feature request that suggests adding such a feature:
Make sure to vote on it and make yourself a watcher so you will get notified of any changes to it.
Atlassian Support APAC