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)
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...
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