fossasia/eventyay

On the organiser Sessions overview, several columns can already be sorted, but the Speakers column cannot. Organisers should also be able to sort sessions according to the assigned speaker(s). Expected behavior Make the Speakers column sortable. Support ascending and descending sorting. Sort alphabetically by speaker name. For sessions with multiple speakers, use a consistent rule, e.g. the first listed speaker. Sessions without a speaker should be grouped consistently at the beginning or end. Use the same sorting icons and behavior as the other sortable columns. Acceptance criteria Clicking Speakers sorts sessions alphabetically by speaker. Clicking again reverses the order. Multi-speaker sessions sort consistently. Sorting works together with the existing search and filters. The active sort direction is visibly indicated.

The organiser overview tables under Rooms, Tracks, Types should support sorting by the columns available on each page. This should follow the same sortable-table behavior already used elsewhere in Eventyay. Expected behavior Add ascending/descending sorting to all meaningful columns on: Rooms Name Capacity Tracks Track Color Proposals Session Types Sort by the columns shown on that page, excluding action/control columns Do not make the final Actions column sortable. Acceptance criteria Column headers show the standard Eventyay sorting indicator. Clicking a sortable column toggles ascending/descending order. The active sort column and direction are clearly indicated. Sorting works together with any existing filters/search. Actions/reorder controls remain unaffected. The implementation is consistent across Rooms, Tracks, and Session Types.

The organiser Speakers overview should allow organisers to sort the speaker table by the most relevant columns. Currently the table does not provide sorting for these values. Expected behavior Enable ascending/descending sorting for: Name Accepted Proposals Proposals Arrived / Not arrived Use the same sortable-column behavior and icons already used in other Eventyay tables. For the arrival column, sorting should group speakers by their arrival status, e.g. Arrived and Not arrived. Acceptance criteria All four columns can be sorted ascending and descending. The active sort column and direction are visually indicated. Sorting works together with existing search and filters. The selected sorting is preserved while filtering/paging where applicable. The implementation follows the existing Eventyay table sorting pattern.

Problem Description Currently, the email.bulk.monthly (Monthly Bulk Emails) capability limit defined in eventyay-business is only enforced and recorded for emails dispatched via the Talks / CFP mailer (app/eventyay/orga/views/mails.py). In the Tickets / Orders area (app/eventyay/plugins/sendmail/), organizers can also compose and dispatch bulk emails to attendees/orders. However: There is no call to check_entitlement(organizer, 'email.bulk.monthly', quantity=recipients_count) before queuing or scheduling emails in sendmail/views.py. When bulk emails are dispatched via send_queued_mail in sendmail/tasks.py, no entitlement_usage_recorded signal is dispatched to deduct the quota from the organizer's monthly limit. As a result, bulk emails sent through the Tickets section bypass plan allowances and can be sent without limit. Expected Behavior Entitlement Check on Composition & Queueing: Before an email is added to the outbox or scheduled in app/eventyay/plugins/sendmail/views.py, calc

Timezone names are currently displayed using their internal identifier format, for example: Asia/Ho_Chi_Minh This is not user-friendly and exposes the technical timezone identifier directly. Expected behavior Display timezone names in a readable format, replacing underscores with spaces. Example: Asia/Ho_Chi_Minh → Asia/Ho Chi Minh Apply this consistently wherever timezone names are shown to users, including: public event header event date/time information schedule speaker/session pages organiser views where timezone names are displayed The underlying timezone identifier should remain unchanged internally. Acceptance criteria Timezone labels no longer display underscores. Asia/Ho_Chi_Minh is shown as Asia/Ho Chi Minh. Other timezone identifiers containing underscores are formatted the same way. Time calculations and stored timezone values remain unchanged.