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
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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!
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