Mandatory Custom Field Validation issue

Mandatory Custom field added in Screen "A", Even though not showing in Screen "B", But Mandatory Validation is displayed while saving screen "B"

1 answer

0 votes

Mandatory fields are not related to screens.   A screen is just a list of the fields, it says nothing about their behaviour.

There are broadly two ways to do mandatory fields:

1.  On the transition - a validator is running.  You'll need to have two separate workflows, one using screen A, and the other for B

2.  Field Configurations are the standard way, and make a field mandatory at all times.  You will need two field configuration schemes here - one for A and one for B

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

27,471 views 2 7
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