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?

TIA!

 

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 Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira Service Desk

Wy are we still using email for Service Desk workflows?

...attest to the experience of an urgent approval that gets lost in the boss’s inbox and requires that special “Please Approve” email or text message. In an age where we have distributed teams...

113 views 0 2
Read article

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