Hi @Enrique Ramirez ,
Yes, you are correct when saying the entityId is the id for what you have described in assignmentType, so if you have selected JOB (as in your case), the entityId 3637249 must represent the Job's id.
There is a Suggestion https://jira.atlassian.com/browse/BAM-19659 - REST APIs for Jobs should show the Job id filed waiting to be implemented. If possible, I would encourage you to comment on the link mentioned, as well as voting and becoming a watcher so you can keep up to date with changed to it.
In the meantime, you could get the Job id by running SQL statement against Bamboo's database:
# build_type, can be either CHAIN, CHAIN_BRANCH or JOB where:
# CHAIN relates to a plan
# CHAIN_BRANCH relates to a branch
# JOB relates to a job
where full_key like 'PROJ-PLAN%';
Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events