Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Flat weekly index, no year pages

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

Status
colourGreen
titleAvailable to all

All salons in Finland

TIM-193

Kletta accounting integration

Status
colourGreen
titleAvailable to all

All salons in Finland. 10 €/month per business ID, first month free.

TIM-51

Series cards

Status
colourGreen
titleAvailable to all

All salons. Existing customers were migrated across in August 2026.

TIM-97

Refreshed marketing site

Status
colourGreen
titleAvailable to all

Public website, live in every market.

TIM-758

Online booking, new version

Status
colourYellow
titleOpen beta

New salons get it automatically. Existing salons can switch it on themselves.

TIM-2

Prerequisite forms

Status
colourYellow
titleOpen beta

On by default for salons created since February 2026. Older salons can switch it on.

TIM-4

New gift card shop

Status
colourBlue
titleIn development

Requires Adyen. Not generally offered yet.

TIM-897

Blocking clients

Status
colourBlue
titleIn development

Only works for salons on the new online booking.

TIM-1237

Pay by link

Status
colourBlue
titleIn development

—

TIM-53

PowerOffice GO accounting integration

Status
colourBlue
titleIn development

Will be for Norway.

TIM-1031

Genie AI analyst for salons

Status
colourBlue
titleIn development

—

TIM-1034

Online booking email improvements

Status
colourBlue
titleIn development

—

TIM-1304

Rescheduling an online booking

Status
colourBlue
titleIn development

—

TIM-1352

New marketing tool

Status
colourGrey
titlePlanned

—

TIM-1384

Scheduled availability

Status
colourGrey
titlePlanned

—

TIM-1385

Scheduled pricing

Status
colourGrey
titlePlanned

—

TIM-1386

Hano transfer tool

Status
colourGrey
titlePlanned

—

TIM-312

How to read the statuses

Status

What it means for a customer

Status
colourGrey
titlePlanned

Agreed and on the list, but work has not started. No date to promise.

Status
colourBlue
titleIn development

Being built now. Do not offer it to customers yet.

Status
colourYellow
titlePilot

A named list of salons is using it. Nobody else can be added without asking the product team.

Status
colourYellow
titleOpen beta

Any salon can turn it on, and new salons usually get it by default. Safe to recommend, but say it is new.

Status
colourGreen
titleAvailable to all

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.

Expand
titleOlder features, available for more than six months

These are long since live and stable. They are kept out of the table above so it only shows what is changing.

Feature

Available since

Who can use it

Epic

Tripletex accounting integration

December 2025

All salons in Norway

TIM-3

Fiken accounting integration

January 2026

All salons in Norway

TIM-95

Subscription billing in Estonia and Latvia

January 2026

All salons in Estonia and Latvia

TIM-108

Note

The Tripletex and Fiken integrations existed long before these dates. The 2025–2026 work rebuilt their settings screens; it did not launch the integrations.

How this page is maintained

Every Thursday morning, before the Jira board's Done column is cleared:

  1. Everything finished that week is stamped with the week's release version in Jira.

  2. A new weekly page is written from that list and added under the current year.

  3. The table above is regenerated.

  4. 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 goes under "Behind the scenes" so the page stays readable without hiding anything.

Warning
titleThe status column is set by hand, on purpose

A feature's status is a product decision, not something that can be read off a Jira workflow. An epic can sit in "In Progress" for months after the feature is live, or in "To Do" while it is being built — both happen here regularly. So each epic carries an explicit label — STAGE_PLANNED, STAGE_DEV, STAGE_PILOT, STAGE_BETA or STAGE_GA — and that label is what this page shows. Country labels (FI, SE, NO, EE, LV) record where it is available, ARCHIVED moves it into the older-features list after six months, and NOT_A_FEATURE keeps internal projects off the page entirely. Any epic with no stage label is reported as missing rather than guessed at.

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
sortcreation
reversetrue

How to read a weekly page

Each one 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 that week.

The split between the last two follows the feature's status on 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 — 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:

  1. Whatever is left in the production column moves to Done.

  2. The slide deck for the company weekly is built from the Done cards worth showing. Each one picked is tagged SLIDES in Jira as it is selected.

  3. The release is created in Jira and every Done card assigned to it.

  4. A new weekly page is generated from that release, and the Product Team status board is refreshed.

The release version in Jira 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.

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

...

.