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

Can you make a field in next gen a mandatory field?



i'm looking into this new JIRA agility board and can't find anywhere I can make some of the fields mandatory


Is there a specific way I need to do this on next gen projects?




6 answers

1 accepted

5 votes
Answer accepted

Hi @Ravi Mistry,

Unfortunately this is not possible yet. As many thing currently this is on Atlassian Roadmap...

"Required fields, default values and more custom field types and options coming soon."

When this could be live? No idea. That is not an official information yet.

Pavel V Atlassian Team Dec 17, 2018

Hi Mirek and Ravi, please follow the roadmap page for updates:

Like Dave Liao likes this

Anybody know the status for required fields?  

@Pavel V, yes we are very aware of the roadmap page but what was once updated with "Shipped" items almost weekly or biweekly, now has zero updates for exactly 3 months.  Has JIRA Next-Gen reduced in priority for Atlassian as a whole?  

Eoin Atlassian Team Jan 30, 2019

@Tom Leser apologies regarding the roadmap. This has slipped through the gaps for a while - I'm currently compiling all the updates and I will publish a new roadmap next week. 

With regards to required fields, a change in priorities means this will be removed from shipping soon and falls back into the backlog of changes for next-gen projects.

Again apologies for the inconvenience this will cause.

Like Dave Liao likes this

Can we vote to raise priority or something?


Really miss this in nex-gen projects.

Like # people like this

This is over a year! This is a public company! OMG! wow 

Like Sam Mohyee likes this

Hello! 2020 arrived and a pretty basic functionality such as mandatory fields is not there yet. Bump for this.

As everyone else is saying, when can we expect this basic feature to be available? It's like selling an expensive car without windshield wipers. 

Nov. 2018 - first comment. 

Jan. 2020 - still no update. I DO NOT want to go through a migration back to classic just to have basic functionality. 

hmmm, ther is a lot i like about next gen projects, but some things i expected to be available are not. bummer... considering migrating back

Dave Liao Community Leader Sep 21, 2020

If anyone here is interested in making fields required in next gen projects, I would vote up JSWCLOUD-17631 (which I just did).

Like Pavel V likes this

Nov. 2018 - first comment. 

Jan. 2020 - still no update. 

Feb. 2021 - still no update. 

Like # people like this

@hullen - typical JIRA - Nothing ever gets done.

I wonder if the JIRA team uses a broken JIRA how could we expect anything more?

Atlassian - please add this basic feature asap!

Almost 4 years and this basic requirement isn't available in NextGen.

If Atlassian was a new company and they released NextGen as a product it would fall flat on its face. It's an incomplete offering.

2 votes
Eoin Atlassian Team Feb 02, 2021

Hi @Ravi Mistry - it's not possible to have a mandatory field on issue creation in next-gen projects; however it is possible to create a workflow rule to check a field has been populated on transition to another status "Check an issue's field",workflows%20in%20next%2Dgen%20projects.


For mandatory fields on issue creation, you can add your vote to the feature suggestion here  This will happen, although not likely in the next 12 months. 


Apologies for the inconvenience!

This rule doesn't work for us. Should it stop the transition from happening if the rule isn't fulfilled?

Eoin Atlassian Team Mar 02, 2021

@matt_belway it should prevent the transition happening. Can you share a screenshot of your rule and explain what it is you are trying to do?

Is there an add-on app we can use for this?

I suffered this issue for a while. With the recent automation feature, I had the following workaround solution as the site admin. 

Trigger: when a new task is created and required custom field is not filled. 

Action: Send the initiator an email cc to me telling the required field is blank. 

You still let the task to be created with the blank "mandatory" field. If you have standard jira this automation could easily use up the 1000 max usage per month.

0 votes

I'm new at Jira, at work before we suppose to use our developed product. But from now on what I see, is Jira need to make money on APP so they get rid of basic functionality and literally force companies to use external JIRA APP. 
It is a big shame. 

0 votes
Deleted user May 09, 2020

Any forecast for having this Field Mandatory option?

Dave Liao Community Leader Sep 21, 2020

@[deleted] - doesn't seem so. I'd vote up JSWCLOUD-17631 if you're interested in being able to set fields as required in next gen projects.

Like Pavel V likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

1,364 views 10 22
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you