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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Why does the plan key have job name appended to it.

I am writing a Bamboo plugin. The PlanKey get the I get from the context "public boolean shouldDisplay(Map<String, Object> context)" is TPRO1-TPLAN1-JOB1.

PlanKey planKey = PlanKeys.getPlanKey((String) context.get("planKey"));

why does it have the job id appended to it? 

Should it not only be the plan key i.e TPRO1-TPLAN1?


1 answer

1 vote
Jobin Kuruvilla [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.
May 10, 2018

You can have multiple jobs within the same plan. And each job can run in parallel, acting as if they are different mini-plans. Most of the time, you will need the job id as well when you automate something, if it has to work in all scenarios.

If I remember correctly, PlanKeys has other methods to retrieve different parts of the full key.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events