Editions define the time scope of your organisation in Ticketack (for example 2025 or 2026). They group and isolate season-related data: programming and screenings, applications, statistics, articles, pricing, sale points, and more. Every resource you create or view in Kronos is tied to the active edition.
What are editions for?
- Separate seasons so one year’s data does not mix with another’s.
- Prepare a future edition (ticketing, venues, price lists) before going live.
- Browse a past edition in read-only mode for history and reporting.
- Filter the Kronos UI: the edition selector (header) and API calls use the chosen edition context.
For a broader checklist when opening a new festival season, see How do I prepare my festival’s new edition?
Access edition management
Sign in to Kronos, then open Administration → Editions (/editions). The list shows each edition’s identifier, start and end dates, event dates, and status (Upcoming, Active, Past).
Switch edition in Kronos
In the sidebar, the Edition menu lets you switch between editions you can access.
- Past edition: view-only; changes are blocked (warning banner).
- Future edition: you can prepare data; it does not affect the public until it becomes the instance’s current edition.
- Current edition: the production edition for your instance (badge Current edition in the list).
Create a new edition
- On the editions list, click Add (or open
/editions/new). - Enter the identifier (e.g.
2026): it is unique and cannot be changed after creation. - Set start and end dates for the edition (administrative season window).
- Set event start and end dates (festival or event period).
- Click Create.
Event dates are used when shifting dates during resource copy (below). To roll a season forward by one year, enter dates that reflect that offset (e.g. edition 2025 from 1 June to 30 June 2025 → edition 2026 from 1 June to 30 June 2026).
Copy data from a previous edition
Resource copy is only available when creating an edition (not when editing it later).
- In the creation form, under Copy resources, enable Copy resources from another edition.
- Choose the source edition (the instance’s current edition is pre-selected by default).
- Select the data types to duplicate. Depending on your needs, you may copy for example:
- Programming: venues, screenings (activities)
- Ticketing: article categories, articles, ticket types, pricing lists, bucket lists
- Sales: sale points, cash registers
- Documents: PDF and e-mail layouts
- Applications: application types, phases
- Other: sectors, equipment orders, tags, settings overrides
- Keep Adapt dates to the new edition’s calendar enabled to automatically shift dates on copied resources (screenings, articles, ticket types, phases, etc.). The system computes the gap between the source edition’s event start date and the new edition’s event start date, then applies that offset. This is how you “shift by one year” when the new edition’s event dates are one year after the previous edition.
- Click Create. Copying runs right after the edition is created.
Notes:
- Turn off date adaptation if you only want the structure without automatic shifting (adjust dates manually afterwards).
- Copying does not overwrite an existing edition; it only fills the new edition.
- After copying, review screenings, sales windows and phases that use dynamic rule expressions; some fields are not shifted automatically.
Set the current edition
The current edition is the one used in production for your Ticketack instance. In the editions list, click Current edition on the desired row. The interface reloads with that edition as the server reference. Only users with edition administration rights can perform this change.
