Ladna
Current version 0.175.0

What's new in Ladna

0.134.0

Actionable Festival application queues

  • Festival application lists now use compact, mutually exclusive work queues for review, requested corrections, incomplete payments, participant submission, completed registrations, and closed applications.
  • Organizers can combine each queue with always-visible search, category, application-status, current-step, checklist, and current-step payment filters. Counts adapt to the other selected filters, and every selection survives queue changes and pagination.
  • Current-step checklist and payment filters follow the actual registration flow, so teams can find an approved first step with an unpaid second step or a later step that has not yet been completed without scanning every application.
Pending release commit.
0.133.0

Event ticket operations and safer Festival exceptions

  • Studios can configure Event ticket options on dedicated pages, require at least one active option before publication, and manage issued tickets through searchable status, check-in, source, and ticket-type filters.
  • Authorized Event staff can issue paid or complimentary venue tickets, record the offline payment method, enforce event and ticket inventory, email tickets when contact details are available, and move consistently between setup, orders, tickets, and scanning.
  • Festival managers can exceptionally delete an application with paid or unresolved payment history after handling any refund manually and typing an explicit confirmation. Ladna rechecks payment history before deletion and retains the related audit and fiscal evidence, while the Festival owner help is now organized into focused chapters with current screenshots.
Pending release commit.
0.132.0

Complete Festival applications and complimentary tickets

  • Festival teams can issue secure complimentary venue tickets to individual guests or automatically to accepted participants and active judges, while managing guest profiles and remaining capacity from one workspace.
  • Application lists now show distinct workflow, payment, and current-step states. Category capacity limits prevent over-acceptance, manually declined draft payments no longer block safe deletion, and participants receive localized review, correction, payment, and acceptance updates.
  • Studio owners can opt into each Festival update through the main Ladna Telegram bot, notification settings are grouped by purpose, and the customer booking bot now provides clearer back navigation through locations, dates, and classes.
Pending release commit.
0.131.1

Class passes for unpaid room rentals

  • An unpaid anytime room rental now uses a compatible active class pass immediately or when one is issued later, starting with the oldest compatible unpaid rent. Direct cash-payment history remains unchanged and prevents automatic conversion, while anytime duration must exactly match the selected rental type.
Pending release commit.
0.131.0

Live Festival operations and protected online viewing

  • Festival teams can run synchronized real-time timelines for multiple scenes, adjust the live order, pause or resume operations, and publish current and next timings to visitors.
  • Guest ticket cabinets now support protected live-stream admission with revocable tickets and viewer devices. Streaming remains unavailable until Ladna's dedicated infrastructure is configured.
  • Festival registration and payments now provide clearer completion rules, correction windows, participant phone verification, payment and fiscal details, and polished public and Help presentation.
Release commit.
0.130.0

Clearer Festival registration and public discovery

  • Festival registration fields now use grouped settings with contextual help, separate yes/no radio answers from required agreement checkboxes, and save both asynchronously.
  • Festival participants can save a Telegram contact and complete missing phone verification directly from their profile, with inline login and profile validation plus clear one-time-code guidance.
  • Public studio pages now show current and upcoming Festivals as hero-image cards with dates, summaries, and links to all published Festivals.
Release commit.
0.129.0

Specialist Festival judging and knockout battles

  • Festival categories can now use scored or knockout formats with minimum entrant requirements, submission-age rules, duplicate-track protection, roster pricing, and approval-relative payment deadlines.
  • Organizers can assign judges to specific rubric sections, use structured deductions, reopen submitted sheets for audited corrections, preview results, and record reasoned jury ordering for exact ties.
  • Exotic Battles now supports randomized single-elimination brackets, judge and audience voting with a 50/50 result, byes, tie decisions, and automatic winner advancement.
Release commit.
0.128.0

Focused Festival management and judging

  • Festival configuration now uses focused, searchable pages for directions, categories, registration workflows and steps, registration fields, fees, content sections, documents, and media, with consistent filters, ordering, and actions.
  • Judging is now split into Judges, Criteria, Score sheets, and Results. Managers prepare sheets and publish generated rankings without seeing another judge’s private scores, while assigned judges see only their own work.
  • Authenticated Ladna workspaces now use consistent responsive breadcrumbs, and the Festival help guide reflects the updated management flow.
Release commit.
0.127.0

Simpler Festival directions and categories

  • Festival settings now use simple Directions and Categories: every category belongs to one direction, and the Classification builder has been removed.
  • Categories are created and edited on focused pages with grouped participation, performance, registration, deadline, and formatted-requirement settings. Applicants choose accessible category cards grouped by direction.
  • Existing entries always show and validate the category’s current direction, limits, deadline, and requirements. Typed questions and uploads keep their behavior under the clearer Registration fields name.
Release commit.
0.126.2

Consistent Ukrainian Festival terminology

  • Ukrainian Festival settings now use natural Ukrainian wording for guidance, examples, file types, links, identifiers, and email labels.
  • System-created registration workflows from earlier Festival releases are localized for Ukrainian studios without changing organizer-customized wording or historical entry snapshots.
Release commit.
0.126.1

Clearer Festival setup and settings

  • Festival edition forms now group identity, dates, registration, venue, and public content into focused sections with short guidance for every field.
  • Festival settings now use clearer high-contrast explanations and consistent right-aligned icon actions across directions, classifications, categories, workflows, requirements, fees, and content.
  • Internal Festival identifiers are generated automatically from organizer-visible names and remain stable after renaming, so organizers no longer see or enter technical codes, keys, or option values.
Release commit.
0.126.0

Configurable Festival registration and focused settings

  • Festival organizers can now build ordered registration workflows with application, payment, technical-form, and summary steps. Categories select a workflow, while requirements and fees can be attached to the relevant step.
  • Festival settings are now split into focused pages for directions, classifications, categories, registration workflows, requirements, fees, and content. Each page explains the entity and its dependencies directly in the interface.
  • New entries preserve a snapshot of their category, workflow, requirements, and prices, so later organizer changes apply only to future entries. Current answers and judging corrections remain editable, while affected published results are safely withdrawn until recalculated.
Release commit.
0.125.0

Standalone Festival competition workspace

  • Studios can now manage complete Festival competitions in a dedicated workspace with Series and editions, public pages, a separate participant portal, applications and requirements, schedules, judging and results, spectator tickets, secure QR admission, and organizer communication.
  • Festival administration has its own focused navigation and visual identity, while participant identities and competition data remain completely separate from studio Customers and ordinary Events.
  • Festival editions use prepaid tariff packages with fixed participant and guest-ticket limits. Studio owners can purchase a package with their saved Ladna card or hosted checkout, and authorized Festival managers can redeem an available package to create the edition.
Release commit.
0.124.0

Self-service payment method replacement

  • Studio owners can now change or relink the saved card from either the SMS account or SaaS billing page. Ladna confirms the change, unlinks the previous Mono token, and verifies the new card for 0 UAH.
  • Replacing a card does not retry or create a payment. SMS auto top-up stays suspended until the new card is verified, while its thresholds and limits remain saved.
Release commit.
0.123.0

Explicit trainer-overlap exceptions for one-off classes

  • Studios can now enable simultaneous one-off classes for the same trainer in different rooms from General settings. Ladna still requires an explicit confirmation for every trainer conflict, while an occupied room always remains unavailable.
  • The exception works for manually created group and closed classes, including additional trainers. Weekly schedule generation keeps its existing behavior.
Release commit.
0.122.0

Focused workspaces for multi-location studios

  • Studio teams with multiple locations can now choose all locations or one working location from the global header. The choice is remembered and automatically scopes dashboards, schedules, finance pages, rooms, events, class passes, and related forms where location context is available.
  • Account-wide pages and records are clearly identified while a concrete location is selected, and one-location studios keep a simpler interface without a redundant location switch or account-wide labels.
Release commit.
0.121.1

Safer class-pass date management

  • Purchased class-pass dates are now displayed as system-managed, read-only values. Studio staff use the audited session and validity-day adjustment controls instead of editing lifecycle dates directly.
Release commit.
0.121.0

Booking bot links and safer cancellations

  • Studios can now independently show a Booking bot button in the customer account, the public studio page header, and the bottom contact block. Each link is visible only while the studio customer Telegram bot is active.
  • Customer class cancellation now asks for confirmation before releasing the place and returning a reserved class-pass session.
Release commit.
0.120.0

Individual lessons in studio Telegram bots

  • Customers can now book individual lessons directly through a studio-owned Telegram bot by choosing the location, direction, service, trainer, room, date, and time. Studios that use trainer availability timeframes get the same room-after-time selection as the Ladna schedule.
  • The bot respects studio opening hours, trainer and room availability, existing customer bookings, and published events. It books exactly one participant, reserves a suitable class pass when available, clearly warns when no pass is found, and checks availability again before creating the booking.
Release commit.
0.119.0

Safer Telegram customer access

  • Linked customers can now open their customer cabinet from the studio bot without signing in again. The bot uses a short-lived, single-use link that stops working after it expires, is used, or the Telegram connection is revoked.
  • The booking-history button now reliably shows previous and cancelled classes.
  • Telegram message, update, and customer-notification histories now follow the same automatic retention period configured for the activity log.
Release commit.