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

how to disable the new plan when cloning from old plan

When a new plan is cloned from the branch, the new plan is enabled by default and new build will be kicked off. But, the new build will be kicked off with the details from the cloned branch.  This will be a problem since we don't want builds with the old branch repositories.

Previously, we had an option to disable the branch when we were cloning it. This helped us to edit the repository information or the variables. Looks like, it is removed with the recent update.

Can anyone suggest on how to disable the plan when we are cloning the old plan?

1 answer

1 vote

You're right, it was caused by changes to Create plan dialog:

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events