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 a field mandatory if it can't be seen

Hi all,

I want to make the description field of all issuetypes mandatory.

However, if you create an issue using the roadmap or backlog views, it will only bring up the summary to enter.

How do I ensure that the description field is mandatory, no matter where you create it in Jira?

1 answer

1 accepted

0 votes
Answer accepted
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 31, 2023

Hi @Kevin Dickson,

When you make the description field required via the field configuration of your project(s), you will be forced to fill out the field when you create an issue, even when you create an issue from the roadmap view e.g.

Jira will show the create issue dialog when you try to create an issue inline there, so you can fill out the additional details.

Be aware though that the fields you manage through field configurations are used in company managed projects. Team managed projects have their own settings that are not shared with other projects. So you will not be able to manage settings for those projects centrally.

Hope this helps! 

Hi Walter, and thanks for this.

I've realised what I was doing wrong.
Instead of creating a new field configuration scheme, I was applying a validator to my workflow to make it mandatory. This only seems to work from the "create" button on the project menu, and not on the backlog or epic views.

I tried it again using a new field configuration for my project and all working now.

Really appreciate your input, all the best!

Like # people like this

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events