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

Defaults for issue types are applying haphazardly

I've setup a bunch of issue types in my project then set defaults up on particular fields such as the description. 

When I create a new entry (in any view - board, list etc) with one of these issue types, sometimes the defaults are applied, sometimes they're just blank. Weirdly I seem to have more success in the board view but I can't find a reason as to why sometimes the fields are populated and other times they aren't, it seems totally random.

Seems like a bug?

I have no automations enabled.

Appreciate any insight!

1 answer

Just to add more context, if I use the 'create' button in the header I can switch between issue types just fine and the correct defaults are loaded in the 'description' field.

It's when I use the quick create methods in list view for instance, after adding a title and hitting enter then going into the ticket, the defaults for that issue type have not been applied (but sometimes they are).

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events