Fields in Jira are either required or not. For the entire life-cycle of an issue. (This is a known weakness in Jira, but it's not obvious at first). You control that with field configurations.
Screens are pretty much irrelevant here, all they do is say "show these fields to users if they're on this screen".
The work-around is to use "validators" on the workflow, so that a user trying to leave your field blank when going between status is thrown back to the screen with a "this field is mandatory" type message. There are no validators like this built into Jira, but many highly recommended plugins all provide them (Jira suite utilities, jira misc workflow extensions, etc)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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