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).
Is there any javascript available that would do it?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's added in the Create Issue screen, you can try and reproduce it. This is JIRA 6.1.5
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The format is defined as dd/MM/YYYY in the Admin/Look and Feel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, right you are. I tested and verified and raised a bug for this under https://jira.atlassian.com/browse/JRA-45776. Perhaps someone else can offer suggestions on validating it with JS.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.