Where Timma's features stand, and what shipped each week. Written for everyone, not just the development team. If you support customers or sell Timma, this page should answer "can my customer use this yet, and where?" without asking anyone.
Feature status
Feature | Status | Available in | Details | ||||||
|---|---|---|---|---|---|---|---|---|---|
Tap to Pay on iPhone |
| Finland | |||||||
Kletta accounting integration |
| Finland | |||||||
Online Booking 3.0 |
| — | |||||||
Tripletex accounting integration |
| Norway | |||||||
Fiken accounting integration |
| Norway | |||||||
Subscription billing |
| Estonia, Latvia | |||||||
New gift card shop |
| — | |||||||
Blocking clients |
| Online Booking V3 salons only | |||||||
Pay by link |
| — | |||||||
Forms |
| — | |||||||
Marketing site refresh |
| — | |||||||
PowerOffice GO accounting integration |
| Norway | |||||||
Online booking email improvements |
| — | |||||||
Rescheduling an online booking |
| — | |||||||
Genie AI analyst for salons |
| — | |||||||
Series cards |
| — | |||||||
Hano transfer tool |
| — |
| Note |
|---|
Rows showing — under "Available in" are not yet filled in. Country coverage is only recorded for features where a ticket states it explicitly, so treat a dash as "ask the product team", not as "everywhere". |
Weekly releases
Timma releases every Thursday. Each release gets its own page listing what changed, in plain language.
How to read this page
Status | What it means for a customer | ||||||
|---|---|---|---|---|---|---|---|
| Agreed and on the list, but work has not started. No date to promise. | ||||||
| Being built now. Not visible to customers yet. | ||||||
| A handful of hand-picked salons are using it. Do not offer it more widely. | ||||||
| Open to salons who ask, and expected to work. Rough edges are possible. | ||||||
| Live for every salon in the listed countries. Sell it and support it freely. |
How this page is maintained
Every Thursday morning, before the Jira board's Done column is cleared:
Everything finished that week is stamped with the week's release version in Jira.
A new weekly page is written from that list and added under the current year.
The feature status table above is refreshed.
The release is marked as released in Jira and the board is cleared.
Tickets that matter to customers, support or sales are tagged SLIDES in Jira. Those become the visible sections of the weekly page. Everything else is grouped under "Behind the scenes" so the page stays readable without hiding anything.
Spotted something wrong or missing? Tell the product team rather than editing the table directly — it is regenerated from Jira each week, so manual edits get overwritten.
| Create from template | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...