So, while it is nice to be able to set a custom field as required, the error message the user gets makes no sense for lots of users; i.e.,
customfield_10100: Customer Name is required.
Why on Earth would anyone want to see customfield_10100. For my particular set of users I am attempting to appease currently, I'll get crucified if this is my solution to making custom fields required. Do I really have to jump into velocity or whatever to remove this garbage? Please help.
I have implemented mandatory field setting in the workflows, and while I have issues with this:-
1) JIRA doesn't add an asterisk
2) Isn't consistent with the number of errors (i.e. may only print an error for 1 mandatory field at a time
The messages always uses the field name that I have given the custom field.
We are on 6.3 if that is of any help?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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