I understand that I can configure the field to be mandatory editing "Default field configuration", but even if the field is only associated to the "close issue" screen when I create a new issue in the "created issue" screen I do not see my custom field but when I click on create it always fails because it says to me that my custom field is required.
As I said, I created a new Field Configuration to make the fields mandatory and did not just edit the default configuration.
This worked for me because the fields were only required for one project so I was able to associate that project with the new Field Configuration.
However, as yours is for the closed issue screen, I am not sure how this would be done as I assume that you would need the custom field for all projects, and then you would be back to the same problem that you have with editing the default configuration.
How about using a 'field required' validator for any transitions that take you to this closed status? That's ho we're requiring a comment at ticket closure....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events