-
Notifications
You must be signed in to change notification settings - Fork 16
Date and Time Formats
FreeITSM lets you choose how dates and times are written β 25/08/2026, 25.08.2026, 25 Aug 2026 and six other arrangements, with either a 24-hour or a 12-hour clock.
There are two places to set it, and they answer slightly different questions.
Go to System, then the Date and time formats card.
You will see nine ways of writing a date and two ways of writing a time, each shown as a real example rather than a name:
| 25 Aug 2026 | 25/08/2026 | 2026-08-25 |
| 25 August 2026 | 25.08.2026 | 25/08/26 |
| Aug 25, 2026 | 25-08-2026 | 08/25/2026 |
and 14:30 or 2:30 PM.
Pick one of each, check the preview underneath, and press Save. That becomes the default for everybody, and it is also what people see on the self-service portal.
You need to be an administrator to change this.
Not everyone in an office agrees about this, which is rather the point. Go to System β Preferences, and on the General tab you will find three settings that sit together:
| Setting | What it decides |
|---|---|
| Interface language | What words FreeITSM uses |
| Timezone | Which time you see β whether a ticket arrived at 14:30 or 15:30 |
| Date format and Time format | How that time is written β 14:30 or 2:30 PM
|
Both format dropdowns start on Use the system default, and the option tells you what that currently is β so you can see what you would be changing before you change it. Pick anything else and it applies to you alone. Nobody else is affected, and your choice follows you to any browser you sign in from.
Worth separating, because they are easy to run together:
- Timezone changes the time itself. An analyst in Sydney and one in London looking at the same ticket see different clock times, correctly.
-
Format changes only how it is written down.
14:30and2:30 PMare the same moment.
Changing your format never moves a time, and changing your timezone never changes the arrangement.
Choosing German does not force German date conventions, and that is on purpose:
- A German speaker working at a British company may well want German wording and British dates.
- Even within one country people disagree β plenty of British users prefer
25.08.2026or2026-08-25. -
25 Aug 2026does not belong to any language at all. It is simply a preference.
What does follow your language is the words. Choose 25 Aug 2026 with German selected and you will see 25 MΓ€r 2026 in March.
- Not the times themselves, in any respect.
- Not your service level targets. SLA timings are calculated from the stored values and never look at how a date is displayed.
- Not reports or exports.
- Not sorting. A list ordered by date stays in the same order whatever you pick.
Dates are stored the same way regardless of what you choose here. The setting affects presentation only.
If you have used FreeITSM before, the setting starts on exactly what it showed you previously β 25 Aug 2026 and 14:30. Nothing moves until you choose something.
- Timezones and Time Handling β which instant a time refers to
- Internationalisation β the 24 languages
- Date and Time Formats β developer guide β for anyone writing code that renders a date
FreeITSM β an open-source IT Service Management platform Β· github.com/edmozley/freeitsm Β· MIT licence
- Installation
- β° Scheduled tasks (cron jobs)
- Architecture
- AI Providers
- Internationalisation (i18n)
- Timezones & Time Handling
- π Date & Time Formats
- Theming & Dark Mode
- β¨οΈ Command palette (βK)
- π Searching inside tickets
- π Attached documents
-
MobileβFriendly
- β³ π« Mobile: Tickets
- β³ π» Mobile: Assets
- β³ π Mobile: Calendar
- β³ π Mobile: Knowledge
- β³ π¦ Mobile: Service Status
- β³ πΌ Mobile: Watchtower
- β³ π§© Mobile: Problem Management
- β³ π Mobile: Change Management
- β³ πΏ Mobile: Software
- β³ β Mobile: Tasks
- β³ π§° Mobile: Techniques & Tricks
-
Security
- Layer 1 β which modules you can enter
- β³ π§© Module Access Control
- β³ π οΈ Module Access β Developer Guide
- Layer 2 β what you can administer
- β³ π Roles & Permissions
- β³ π οΈ Roles β Developer Guide
- β³ π€ Why capabilities are constants
- Layer 3 β the System module
- β³ π Admin Access Control
- Hardening
- β³ π Security review response 2026-08
- β³ π‘οΈ Security hardening 2026-08
- β³ π οΈ Security hardening 2026-08 β Developer Guide
- β³ π‘οΈ Round three β plain English
- β³ π οΈ Round three β Developer Guide
- Single Sign-On (SSO)
- ποΈ LDAP & Active Directory
- Browser Extension
- API Reference
-
π REST API β how it works
- β³ π« REST API: Tickets
- β³ π» REST API: Assets
- β³ π΄ REST API: Problems
- β³ π REST API: Changes
- β³ π REST API: Knowledge
- β³ β REST API: Tasks
- β³ ποΈ REST API: CMDB
- β³ π REST API: Contracts
- β³ ποΈ REST API: Calendar
- β³ πΏ REST API: Software
- β³ π¦ REST API: Service Status
- β³ βοΈ REST API: Morning Checks
- β³ π REST API: Forms
- β³ βοΈ REST API: Workflow
- β³ πΊοΈ REST API: Network Mapper
- β³ π§ Using the API docs page
- β³ π OpenAPI specification
- β³ β OpenAPI: kept correct
- β³ π οΈ Maintaining the catalogue
- Watchtower
-
Tickets
- β³ Mailbox Authentication
- β³ π€ Email send log
- β³ Basic IMAP mailboxes
- β³ Email rendering & images
- β³ SLA Management
- β³ WhatsApp channel
- β³ π¬ Web chat channel
- β³ π£ Slack channel
- β³ π Linking tickets
- β³ π Ticket notes: internal or shared
- β³ ποΈ Canned responses
- β³ βοΈ Limiting replies to particular senders
- β³ βοΈ Email signatures
- β³ π The public web address
- β³ π’ Ticket numbering
- β³ π Raising a ticket for someone else
- β³ π Merging tickets
- β³ β Splitting tickets
- β³ β Selecting several tickets
- β³ ποΈ The folder pane
- β³ π οΈ Snoozing tickets β Developer Guide
- β³ π₯ Collision detection
- β³ β±οΈ Time tracking
- β³ π Scheduled work in your own calendar
- Problem Management
- Tasks
- Assets
- Knowledge
- Change Management
- Calendar
- Morning Checks
- Reporting
- Software
- Forms
- Contracts
- Service Status
- π Notifications
- π¨ War Room
- Self-Service Portal
- LMS
- Process Mapper
- CMDB
- Network Mapper
- Workflows
- Issue trackers (Jira, Azure DevOps)
- System
-
Overview
- β³ π Progress tracker
- β³ Concepts & vocabulary
- β³ Email routing & mailboxes
- β³ Settings: global vs per-company
- β³ Users & self-service
- β³ Staff cross-company access
- β³ Worked examples
- β³ Pitfalls & gotchas
- β³ Scope: what it's for
- β³ π οΈ Developer Guide (make a module multi-company)
- β³ ποΈ Case study: CMDB (a linked graph)
- β³ π§ͺ Test harness (prove it's isolated)