Where Timma's features stand, and what shipped each week. Written for everyone, not What changed in Timma, week by week, written for everyone rather than 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 | Who can use it | Epic | ||||||
|---|---|---|---|---|---|---|---|---|---|
Tap to Pay on iPhone |
| All salons in Finland | |||||||
Kletta accounting integration |
| All salons in Finland. 10 €/month per business ID, first month free. | |||||||
Prerequisite forms |
| All salons. Forms customers fill in before their appointment. | |||||||
Series cards |
| All salons. Existing customers were migrated across in August 2026. | |||||||
Refreshed marketing site |
| Public website, live in every market. | |||||||
Online booking, new version |
| New salons get it automatically. Existing salons can switch it on themselves. | |||||||
New gift card shop |
| Requires Adyen. Not generally offered yet. | |||||||
Blocking clients |
| Only works for salons on the new online booking. | |||||||
Pay by link |
| — | |||||||
PowerOffice GO accounting integration |
| Will be for Norway. | |||||||
Genie AI analyst for salons |
| — | |||||||
Online booking email improvements |
| — | |||||||
Rescheduling an online booking |
| — | |||||||
New marketing tool |
| — | |||||||
Scheduled availability |
| — | |||||||
Scheduled pricing |
| — | |||||||
Hano transfer tool |
| — |
How to read the statuses
Status | What it means for a customer | ||||||
|---|---|---|---|---|---|---|---|
| Agreed and on the list, but work has not started. No date to promise. | ||||||
| Being built now. Do not offer it to customers yet. | ||||||
| A named list of salons is using it. Nobody else can be added without asking the product team. | ||||||
| Any salon can turn it on, and new salons usually get it by default. Safe to recommend, but say it is new. | ||||||
| On for everyone in the listed countries. Sell it and support it freely. |
Weekly releases
Timma releases every Thursday. Each release gets its own page listing what changed, in plain language.
Timma releases every Thursday, and each release gets its own page.
For where a feature stands overall — planned, in development, or released, and in which countries — see Product Team.
Every release, newest first
| Children Display | ||||
|---|---|---|---|---|
|
How to read a weekly page
Each one Each weekly page is split into three parts, because "we shipped it" and "a salon can tell" are not the same thing:
Section | What goes in it |
|---|---|
Highlights | Features that reached more customers than the week before, plus the two or three biggest items. Read this if you read nothing else. |
Changes your customers will notice | Changes to features salons are already using, so the difference is visible straight away. This is the section support and sales need. |
Everything else | Collapsed. Groundwork on features that have not launched, plus internal and commercial work. Nothing here changes anything for a salon this that week. |
The split between the last two sections follows the feature's status aboveon the Product Team page: work on something still In development cannot be customer-visible, because the feature is not out yet. That is why a week's biggest body of work sometimes sits in the collapsed section .
| Expand | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
These are long since live and stable. They are kept out of the table above so it only shows what is changing.
|
How this page is maintained
Every Thursday morning, before the Jira board's Done column is cleared:
— in week 34, ten tickets of Kletta groundwork did, because Kletta only went live the following week.
How these pages are made
Every Thursday morning:
Whatever is left in the production column moves to Done.
The slide deck for the company weekly is built from the Done cards worth showing. Each one picked is tagged
SLIDESin Jira as it is selected.The release is created in Jira and every Done card assigned to itEverything finished that week is stamped with the week's release version in Jira.
A new weekly page is written generated from that list release, and added under the current year.The table above is regeneratedthe Product Team status board is refreshed.
The release
...
version in Jira
...
Tickets worth mentioning at all are tagged SLIDES in Jira. That tag decides whether an item is the durable record of a week, so these pages can be regenerated from it at any time. The SLIDES tag from step 2 decides what appears; the feature's status decides which of the three sections it lands in.
| Warning | ||
|---|---|---|
| ||
A feature's status cannot be read off a Jira workflow or off the code. Epics sit in "In Progress" for months after a feature is live, and the step that switches a feature on for every existing salon is often run straight against the production database, leaving no trace anywhere. So each epic carries an explicit label — |
...
| Note |
|---|
Anything closed without being built is listed at the bottom of the weekly page rather than quietly dropped, so an omission is always visible. |