Date field shows raw i18n key fields.validation.date.form

[Vadym Chu]

Date field shows raw i18n key fields.validation.date.form... instead of validation message
Also the form formatting looks different, maybe it's a plugin issue.


Environment: Jira Cloud, site: brainstack.atlassian.net
▎ Project: HRM (HR Management 2.0)
▎ Issue type: Employee (Full-time)
▎ Steps to reproduce: Trigger the Re-hire workflow transition on a Terminated employee card → enter a date in the "Start date" field
▎ Expected: Normal date validation message
▎ Actual: Raw i18n key fields.validation.date.form... displayed instead of localized message
▎ Note: The Re-hire form formatting also looks different from standard Jira screens, suggesting it may be rendered by a plugin or Jira Forms feature

[Germán Morales _ Hiera]

Hi @Vadym Chu, your intuition is on track. A validation message rendering as the raw i18n key (fields.validation.date.form...) almost always means a localization bundle that is failing to resolve, and Jira core would not surface a key like that to the UI for a standard date field. Combined with the project name "HRM (HR Management 2.0)", the "Employee (Full-time)" issue type, and the form formatting being different from standard Jira, this looks like a third party app or template doing the rendering, and that app's i18n bundle is missing the entry (or your active locale is not covered by it).

To narrow this down, can you confirm:

• What is rendering the Re-hire form? Is it Atlassian's native Forms (the one that lives under Project settings > Forms), a Marketplace HR app you installed, or a project template you applied? On the issue view, the form should display a small attribution or you can check Apps > Manage apps in admin to see what is installed.
• What is your user language? Profile > Account preferences > Language and region. If you switch your language to English (United States), does the validation message render normally? If it does, this is a missing translation in your locale and is squarely the app vendor's problem.
• Does the same broken message appear on a vanilla date field (not inside the Re-hire form), or only inside that custom form? If it only happens in the form, that confirms the app / form engine is the one missing the i18n entry.

Two things to do in parallel while you gather that:

• If you identify the app from Manage apps, open a support request directly with the vendor (every Marketplace app listing has a Support link). They are the ones who can fix the missing translation key.
• If it turns out to be Atlassian's native Forms and the issue is reproducible, it is worth reporting on the public Jira tracker at jira.atlassian.com so other tenants can vote and track it.

If you share the app name (or a screenshot of Manage apps) I can probably pinpoint whether this is a known issue.

Hope this helps.