-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
4
-
Currently there doesn't seem to be an option in the documentation to pull this data.
[BAM-15870] Provide API endpoint to GET build trigger data
Terrance MacGregor
added a comment - I agree with Angelo on this. I have a very complex operation that uses Bamboo. Bamboo is really amazing on all fronts, but this API limitation is killing or efforts to build a long term view of planned operations, builds and deployments. I have been using Atlassian software for a long time and haven't asked for a single change up until now.
I would love to see an expanded item called trigger.
Example: https://lawiq1.atlassian.net/builds/rest/api/latest/plan/LFC-DC?expand=triggers
Can you make this happen?
Terrance MacGregor
added a comment - I agree with Angelo on this. I have a very complex operation that uses Bamboo. Bamboo is really amazing on all fronts, but this API limitation is killing or efforts to build a long term view of planned operations, builds and deployments. I have been using Atlassian software for a long time and haven't asked for a single change up until now.
I would love to see an expanded item called trigger.
Example: https://lawiq1.atlassian.net/builds/rest/api/latest/plan/LFC-DC?expand=triggers
Can you make this happen? 
Angelo
added a comment - The only alternative way I have found to determine if a type of trigger is set on the plan is to analyze a successful plan build and check on the tag Build Reason. If it starts with Manual, it means that it has been run manually, otherwise it has been run automatically by some type of trigger.This way though it is not exahustive, meaning it cannot be considered a valid way to determine the presence of a trigger. What, for example, if a plan has no successful builds to analyze from?
The one I described above is a weak workaround: it is not a very good one because it does not cover all the possible cases.
Angelo
added a comment - The only alternative way I have found to determine if a type of trigger is set on the plan is to analyze a successful plan build and check on the tag Build Reason. If it starts with Manual, it means that it has been run manually, otherwise it has been run automatically by some type of trigger.This way though it is not exahustive, meaning it cannot be considered a valid way to determine the presence of a trigger. What, for example, if a plan has no successful builds to analyze from?
The one I described above is a weak workaround: it is not a very good one because it does not cover all the possible cases. Angelo
added a comment - Sending a Bamboo rest API request, I would like to get (in the response) info about any trigger set on the plan. There is a way to "expand" itens like stages, plans, actions, ect. , but it seems that there is not a way to expand trigger information.
In the Configuration page of any Bamboo plan (see attachment), there is a set of tabs that provide groupped info for every item, included triggers.
It would be awesome if, like for stages, plans, actions, could be possible to "expand" trigger info in the API endpoint request and get info in the response about whether a trigger (or more than one, of any type) has been set on the plan.
Angelo
added a comment - Sending a Bamboo rest API request, I would like to get (in the response) info about any trigger set on the plan. There is a way to "expand" itens like stages, plans, actions, ect. , but it seems that there is not a way to expand trigger information.
In the Configuration page of any Bamboo plan (see attachment), there is a set of tabs that provide groupped info for every item, included triggers.
It would be awesome if, like for stages, plans, actions, could be possible to "expand" trigger info in the API endpoint request and get info in the response about whether a trigger (or more than one, of any type) has been set on the plan.
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.
Kind regards,
Bamboo Data Center