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

Control Freak's "Jira Policy" and "Jira Ticket Checks" fail if the HEAD commit does not comply


We activated the "Jira Policy" and "Jira Ticket Checks" section of Control Freak on repositories which didn't have this section enabled yet, and in some of the repositories the HEAD commit does not satisfy these conditions.

If a developer now tries pushing a new branch (with or without commits), Control Freak will complain that the commit which is the base of the branch does not reference a Jira Ticket, or references a Jira Ticket which is already in status "Done".

We were able to get it to work properly on a brand new repository, but surely there must be a way to make use of this on an existing one?

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events