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
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%';