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

Making story points mandatory

I'm trying to enforce story points by making them required for a ticket to move out of the To Do column. I've had no problem doing this with the standard version of Jira but can't seem figure it out with the next-gen version. Would love some insight on if this is even possible, and if so, how to do it.



2 answers

My solution is to provide a default value for each issue type. This is not ideal but at least the field is populated unless someone explicitly empties it.

Unfortunately this wouldn't solve my needs as a default value would just allow my engineers to do what they are doing now - which is start work without providing an LOE and thus negating the ability to use velocity as an output measuring tool. Definitely appreciate the suggestion though :)

1 vote

Hi Michele,

Unfortunately, you can't do it yet on the next-gen, but there is a feature request opened here. I strongly recommend you to vote in this feature request and drop a comment to let the product management know about your use case. By doing this, it will ensure you're proactively informed of progress and updates going forward.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events