Release 2025.09

Sept. 29, 2025

In this release we offer the users of Maki nice new features, below you can read the complete overview of all the changes in this release of Maki.

What is in this release?

Hyperlinks automatically open in new tab

New: All hyperlinks within Maki now open in a new browser tab by default. This prevents loss of context and improves usability regardless of the browser used.

Blocking the archiving of categories that are still in use in organization settings.

New: Categories that are still set as default in the organization settings can no longer be archived. Attempting to archive them now displays a clear error message. Once the category has been removed or replaced in the settings, archiving is possible again. This behavior is enforced in both the front-end and back-end.

Merge task name and project name instead of relationship name and project name

New: In task views, the “Task Name” and “Project Name” columns have been merged into one column, with the task name on the first line and the project name below it. This has freed up space in the relationship name column to also show the corresponding contact person, providing more context and consistency in display.

Resolved bugs

Pagination of time entries within the ticket page does not work optimally

Improved: When switching pages in the time registration section of a ticket, the focus now remains on the correct section. This prevents the screen from automatically scrolling back up, providing a smoother user experience when viewing or approving multiple registrations.

Incorrect history when changing ‘Executive employees/groups’ in a task

Resolved: When changing the “Executive employees/groups” field in a task, the communication feed now shows the correct history messages immediately. Previously, incorrect messages appeared temporarily until the page was refreshed, which could lead to confusion. This has now been resolved.

Relationship is clickable for a contact and causes error message

Resolved: In project and task views, linked relationships are no longer clickable for contacts. This prevents #403 error messages and provides a clearer, accessible user experience without confusion over permissions.

The contact person is no longer recorded when logging time via the communication feed

Modified: For new activities logged via the communication feed, a contact person is no longer linked to the time entry. Time entries are now only associated with the underlying entity (ticket, account, project, or task). Only when a response is added on behalf of a contact person will the link to that contact remain visible. This change makes the system behavior more consistent and prevents confusion when multiple contact persons are involved.

When creating a company, unwanted default values of the organization are used

Resolved: When creating a new company, the values from the front-end are now saved correctly. The organization default settings no longer overwrite them, leaving the correct financial and general settings visible on the relation card.

Reminder sent despite status “Resolved”

Resolved: Tickets set to “Resolved” no longer send reminders to affected contacts. This prevents unnecessary notifications and ensures that reminders are sent only for tickets that are still open.

Invoice lines cannot be created for some time entries.

Resolved: Invoicing approved time entries now works correctly. The status remains permanently set to “Invoiced,” the icon stays visible, and the invoice lines are created and linked to the correct invoice, even after refreshing or reopening the entry.