Some fields are require on certain issue types?

I actually have two questions:

  1. Why is <RootCause> field only require on Bugs and not on other Issue Types?
  2. The <RootCause> says it's "Required" however we have custom screens that has it disabled. Will it be required for all projects because it states that it is required or will the project follow its screen?



1 answer

1 accepted

1 vote
  1.  Because that's the way you have chosen to configure it.  You can remove that if you want, or add it to more issue types.
  2. The projects don't use screens for the mandatory flag.  They will follow
    1. the mandatory flag as set in the project's "field configuration scheme"
    2. any validators in the workflow that make the field mandatory

Thank you so much Nic! thumbs-up

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,331 views 14 20
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot