I'd like to mask date fields, in order to restrict dates values and avoid inputs like 01/01/20016 (which would be accepted by JIRA but it would make the indexing fail).
Thanks in advance,
What kind of Custom Field are you using? If you use a Date Picker Custom Field it will already restrict the date input appropriately, using the Day/Month/Year Format as defined in https://confluence.atlassian.com/display/JIRA/Customizing+the+Look+and+Feel
Jira will let me input 01/01/20016: https://casari-asoc.mangoapps.com/sf/Njc1NTRfMTU1MTc5OQ The format is defined as dd/MM/YYYY in the Admin/Look and Feel This caused me once a failed reindexing. I need to avoid this and also would like to restrict future dates, say duedates no later that 01/01/2018. Thanks.
That's odd, JIRA is supposed to validate input with JS in the client. I imagine you may be able to workaround that by populating the field with the Update Issue Post-Function, or another similar function. Was the data added through the edit field normally, or another way?
What are you look & feel settings for the Day/Month/Year format? https://confluence.atlassian.com/display/JIRA061/Customizing+the+Look+and+Feel If you have this set to something like dd/MMM/yyyyy it could cause the problem..
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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