What's new

A boards overview, a comment heatmap, and pagination for the list and Kanban views

• NewA "Boards overview" arrived in settings: every board you belong to, with your role, in one table. A workspace admin gets an admin view alongside their own, so who is where and with which role is visible on a single screen. The table is paginated on the server, so it opens on an installation with hundreds of boards too.
• NewA new board widget: a heatmap of daily comment volume. It has month and day labels and a "3 months / 6 months / 1 year" range picker; clicking a day lists which task got how many comments that day and takes you straight to it. Built to show which week the discussion piled up on which piece of work.
• NewA status in a workflow can now be marked "edit locked". Tasks sitting in that status can only be edited by authorised roles; changing the status itself is unaffected, so work keeps flowing while, say, an approved record can no longer be altered after the fact.
• NewBuilt-in fields (sprint, start and due date, class of service, fix and affects version, watchers, labels, issue type) can be marked required one by one in board settings. Workflows gained an optional constraint too: when enabled, only the transitions you defined are allowed. It is off by default, so existing boards behave exactly as before.
• ImprovedThe list view now fetches only the page you are looking at (25/50/100) and columns can be resized by hand. Search and filters still run across the whole board. Kanban columns load as you scroll as well, so a large board no longer has to pull every card at once. Column sorting has three modes now: manual, newest first, oldest first. The versions page is paginated too.
• ImprovedEveryday shortcuts: assign yourself with one click from the assignee field in the task drawer, a new "Assignee: me" filter, and the last-updated time on Kanban cards. Mentioning a person or a group in a comment, and bulk assignment, now list only the members and groups of that board.
• ImprovedOn the review side: starting a review with many participants used to get slower the more people were on it, notifications now go out together and the start time no longer depends on participant count. Starting a review with someone who reaches the board only through a group was failing as well, and the picker now suggests only the groups actually added to that board.
• ImprovedLanguage handling was tidied up: pick the language when sending an invite email, a language switcher was added to the sign-up and sign-in screens, and on a first visit the language can be detected from the browser. A few labels left in English in the sidebar and the version fields were translated.
• Heads-upCreating a board is now restricted to workspace admins, and the restriction is enforced on the server as well. If ordinary members used to create boards, they no longer can after this update and will need to ask an admin. A "new board" button, visible to admins, was added to the boards page.
• FixedWith a built-in field marked required, updating some other field without touching it wrongly raised a "required field is empty" error. Members with a custom role showed no role name in the boards overview tables. A user added to a board through a group had the wrong role displayed. Some comment events appeared as raw codes in the activity feed. The list export wrote a meaningless code instead of the assignee. Priority was repeated in two places on the task detail. The GitLab connection status on the boards page was wrong. A version description could not be cleared and saved. The column picker on the list screen overflowed the screen on boards with many columns.

GitLab can connect to a whole group, plus Board Codes and a Boards management page

• NewA board can now connect to a GitLab GROUP instead of a single repository. Pick the group and every project under it (subgroups included) is registered on the board; when you open a branch, merge request or issue from a task you choose which project to work in. Branch, commit and MR lists show the originating project as a badge on each row, and same-named branches in different projects are now listed separately.
• NewWith a group connection, auto-creating issues is managed per project: each project has its own switch and one can be marked "default". The project picker on the new task screen opens with that default; to open an issue in several projects at once you deliberately pick "Open in all enabled projects" at the bottom of the picker. The "Linked issue" section on a task lists every related issue with the project it belongs to, and all of them sync when the task title, description or status changes.
• NewBoard Codes arrived. You define a catalogue of codes in workspace settings (e.g. 12-P25001 · "Platform Project"); when a board is created one of them can be picked and it is prefixed to the board name. The same code can never be given to two boards. Each code can carry an optional description and a type chosen from a managed list, and it can be marked "do not prefix the name". Codes match both in global search and in the board search box in the sidebar.
• NewA Boards management page arrived. Every board you can reach in one screen, with Active and Archive tabs, search, a type filter, and columns for board type, member count and GitLab connection status. Archiving a board removes it from the sidebar without deleting it: it stays here with an "archived" badge and comes back with one click. The list is filtered and paginated on the server, so it stays fast on an installation with hundreds of boards.
• ImprovedNames are consistent in the audit log now: a deactivated account, and non-user targets such as boards, sprints, pages and groups, show their real names instead of a raw record id. The notification bell resolves deactivated accounts correctly too, and automation-driven events (a GitLab integration moving a task, for instance) are labelled "System".
• ImprovedThe invite links list in board settings now shows who an invite was emailed to. It used to show only the role, so there was no way to track where an invite actually went.
• FixedOn wide screens the scrollbar clung to the edge of the centred content box instead of the window; fixed on the settings, inbox, board settings, audit log and saved filters pages. The duplicated "Settings" heading in workspace settings was removed as well.
• SecurityDependencies were updated to versions that close known issues. No user-visible behaviour change.

A template for task titles, plus a batch of small fixes

• NewA task title template can be defined in Board Settings > General. If the title is left empty it is computed from the template: {reporter} for the creator, {assignee} for the first assignee, {cf:field} for the value of a custom field (the person's name for person-type fields). On a time-off board, for example, "Time off - {reporter}" fills in the title of every new task by itself.
• ImprovedWatchers, labels and issue type were added to the show/hide list of task screen fields, so a team that does not use them can simplify the task screen.
• FixedA formula field referencing a person-type field now shows the person's name instead of an internal id. The invite acceptance screen also shows the real name of a custom role.
• FixedRemoving all labels or all assignees on the GitLab side now propagates to the task; previously it only synced while at least one remained, so clearing never came through. A duplicate row for the same commit in the commit panel was fixed too.

Transition rights can now hang on a person field

• NewWorkflow transitions used to accept only a fixed role or a fixed list of people. A person-type custom field can now be picked as well: whoever is named in that field on the task may make the transition. On a time-off board, the person written into an "Approver" field can move the task along without being granted rights task by task.
• FixedThe brief white flash seen while navigating inside the app in dark mode was fixed. The root cause was the theme preference resetting to the default for a moment on page transitions; the theme now stays put.

GitLab smart commits: "Closes CJ-123" advances the task by itself

• NewIf the title or description of a merge request contains something like "Closes CJ-123", "Fixes CJ-123" or "Resolves CJ-123", merging it advances the linked task automatically. Merely mentioning the task key is not enough: closing intent is recognised separately, so an MR that only references a task does not close it. Which status it moves to is chosen in board settings, like the other GitLab automation mappings.
• ImprovedThe show/hide list for fixed task fields now covers watchers, labels and issue type.

Fix Version and Affects Version became multi-select, holidays show on the calendar

• NewFix Version (where a fix will ship) and Affects Version (which releases a bug hits) can now hold several versions. A bug can affect more than one release and a fix can go out in more than one. Filtering, export, bulk edit and CSV import all support the multi-value field.
• ImprovedPublic holidays defined in a board's work calendar are now visible on screen: the calendar view highlights the day and shows its name, and the timeline shades it like a weekend. They used to affect only formula calculations.

Half-day holidays and a lunch break

• NewThe work calendar only handled full-day holidays. A manually added holiday can now carry a time range (09:00-13:30, say), which makes half-day holidays possible. Public holidays pulled per country stay full-day; half days are for your own company decisions. A lunch break can also be defined, and when it is, it comes off the daily capacity in both work-hour and work-day calculations.

A work calendar per board and work-hour formulas

• NewBoard settings gained a "Work calendar" section: working hours and the public holiday list are now defined per board. Holidays can be entered by hand or fetched for a chosen country and year in one click, across 40 countries. If the external service cannot be reached, manual entry keeps working and existing holiday labels are not overwritten.
• NewFormula fields gained a "calculate as work hours" option: the gap between two date/time fields is computed in hours against the board work calendar, excluding weekends and holidays and prorating partial days outside working hours. The "calculate as work days" option now accounts for public holidays and half days too, and counts both ends (Monday to Friday = 5 work days, the same rule as Excel NETWORKDAYS).
• FixedClearing the start date with "x" on the task screen looked like it worked but the old date came back on refresh, because the clear request never reached the server. Fixed.
• ImprovedAs settings tabs multiplied, reaching the ones that did not fit got awkward: the bar now stays on one line and clickable scroll arrows appear at the edges when it overflows. The GitLab Pipelines panel was also put behind the same on/off switch as the other GitLab surfaces.

A new "Task screen" tab in board settings

• ImprovedThe "Custom fields" tab held both task screen sections and field definitions. The boxes and fixed fields of the task screen now live in their own "Task screen" tab, leaving "Custom fields" to field definitions and field groups, with the section order tidied up as well.

Fixed fields can be switched off, the calendar can read your own date field

• NewSprint, start date, due date, class of service, Fix Version and Affects Version used to be fixed on every board. Fields a board does not use can now be switched off in board settings. Since Kanban boards have no sprint concept, the Sprint field and its setting no longer appear there at all.
• NewThe calendar view can read one of the board's own date-type custom fields (an optional start and end pair) instead of the default dates, and the timeline follows the same setting. Settings > Preferences also lets you choose whether the calendar and timeline start on Monday or Sunday.
• NewA formula field can compute the difference between two date fields in days, with a "calculate as work days" option that excludes weekends. Workflow auto-assignment can also target a board member you pick directly, alongside the reporter and person-field options.
• ImprovedGitLab activity on the task screen (branches, commits, merge requests, issues) is now a collapsible, reorderable box like Custom fields and Attachments. Person-type custom fields can carry a default person, so a new task opens with them already filled in.
• FixedA due date chosen while creating a task was not saved; it is now stored correctly at creation time. The invite role picker no longer runs off the bottom of the screen, opening upwards when there is no room.

Board-scoped labels, workspace-wide dashboard management

• NewLabels (bug, feature, chore and the like) now belong to each board separately - they used to be one shared list across the whole workspace, editable only by an admin. A new "Manage labels" permission lets you hand that off to other roles if you want. Your existing labels were split by whichever board actually used them during the upgrade; nothing was lost. New boards come with a handful of common labels ready to go (bug, feature, chore, design, docs, tech-debt), and copying a board now carries its labels over automatically too.
• NewA workspace admin can now see every dashboard in the workspace, delete one that belongs to someone else, and mark one as the "workspace default" - a dashboard marked this way is automatically shared with every new sign-up and becomes their personal default. A new hire's first day now starts with the dashboard the team prepared, not a blank screen.
• ImprovedWhen adding the "Activity stream" dashboard widget, you can now pick "entire workspace" as well as a single board.

Editable built-in roles and a kanban column sort mode

• NewYou can now rename the Developer, Tester and Viewer roles and change which permissions they carry, from Board Settings > Roles - they used to be completely locked. The Admin role stays immutable so nobody accidentally loses management access, and you can never hand out a permission you do not hold yourself.
• NewEach kanban column can now be set to sort by "Last updated" or "Manual" order. The default, last updated, brings the most recently touched card to the front; manual mode keeps whatever order you set by dragging.

Task section order, persistent kanban card order and dark mode fixes

• NewBoard Settings > Task sections can now be reordered by dragging. You decide the order the Custom Fields, Attachments, Links, Subtasks and Diagrams boxes appear in; the task screen opens in that order.
• ImprovedDragging a kanban card in front of or behind another card within the same column now keeps that order. Previously, dragging only changed status - it never remembered the position within the column.
• ImprovedA search box, incremental loading and an "X of Y members shown" line were added to both the board members list and the Settings > Workspace member list - as the member count grows you can search by name, handle or email instead of loading everyone at once, and the search box now appears for small workspaces too.
• ImprovedFormula, URL and email type custom fields now get the correct operators in the advanced filter; the quick filter in list view now works on every custom field column.
• FixedThe open dropdown list of single-select fields in dark mode was still a white surface drawn by the browser itself - an earlier fix had only addressed the look of the selected value. Single-select fields now use the same fully theme-aware dropdown as multi-select fields.

Starting from a task template, per-person transition rules and auto-assignment

• NewThe new task screen now offers a task template: status, assignee, labels, issue type and custom fields arrive prefilled and you only write the title. Templates could be defined in board settings but could not be applied anywhere, so a defined template sat there unused. Recurring work (a release, a customer request, an incident record) now opens without filling the same fields by hand every time.
• NewWorkflow transitions can now be opened to specific people, not just to a role. Restricting "Release" to two names no longer requires defining a role for them. A transition can also assign the task automatically when it lands in a status: to the reporter, or to whoever is named in a person field on the task. Work moved to "In review" lands on that task’s reviewer on its own.
• NewThe "who fills this in" rule on form sections gained a status condition: a section can be editable only while the task sits in a given status. Review information can be filled in while the work is "In review" and locked afterwards. It works alongside the role, person-field and assignee conditions.
• NewBulk import from Excel gained an "update existing records" option. When the task id in the key column already exists on the board, the row updates that task instead of creating a new one. Exporting, editing in bulk in a spreadsheet and loading the file back is now a workflow that actually works.
• ImprovedBoard folders in the sidebar can be renamed and reordered. Folders could be created but neither renamed nor moved, so fixing a typo in a folder name meant deleting it and moving every board back one by one.
• ImprovedThe workspace member list now has a search box and loads progressively. On an installation with hundreds of people you find someone by name or email instead of scrolling, and the list no longer loads in full at once.
• ImprovedTask numbers are no longer reused. When a task was deleted the next one took its number, so the same number could refer to two different pieces of work. Numbering now always moves forward, which means a task number points at exactly one thing in your records and in conversation.
• FixedThe "Home" page of a newly created docs board now opens the same rich text editor as every other page; this first page used to fall back to an older editing mode.
• FixedMentioning a username that contains a hyphen now works correctly in comments, and the suggestion box opens at a readable width. Select boxes on custom fields position properly in dark mode and near the edge of the panel. The notification you get when someone is added to a task through a custom field no longer has missing text.

One-click status steps and an installation fix

• NewTwo arrow buttons now sit next to the status in the task panel: one click moves the work to the next or previous step in the workflow. Attempting a transition you are not allowed to make now tells you so; it used to be reverted silently with no explanation.
• FixedScheduled jobs now also run on systems installed without an administrator account. The previous version moved these jobs into the installer, but on systems installed without root (which many are) the job still failed silently. The job log now lives under your installation directory, no matter who installed it.
• FixedOn a Kanban board, changing a status from the task panel and closing it now moves the card to the right column; it used to stay in its old column until you refreshed the page. The role list in the "Add member or group" dialog no longer overflows and gets clipped at the bottom edge either.

Subtask permissions, a leaner task screen and bulk editing

• NewCreating a subtask, attaching an existing task under another one and removing that link are now a separate permission. Until now anyone who could fill in a task could also restructure the work; from now on you choose who may change the breakdown from the role matrix. Your existing roles keep the ability, so nobody loses work they could do yesterday.
• NewThe built-in sections on the task screen (Custom fields, Attachments, Links, Subtasks, Diagrams) can now be hidden or start collapsed, per board. They used to appear on every board with no way to turn them off: a team that never draws diagrams still saw an empty "Diagrams" box on every single task. Because it is a board setting, everyone on the team sees the same screen, and it carries over when you copy a board.
• NewBulk editing got wider. Select several tasks from the list and change priority, issue type, fix and affects version, and person/select custom fields in one go - and remove labels. Adding labels was already there; removing them was not, so undoing a wrongly applied label meant opening tasks one by one.
• ImprovedForm sections can be reordered by dragging. They were already drawn in a set order on the task form, but there was no way to change that order.
• FixedUpdated and created timestamps now include the time of day. The data always held the full timestamp but only the date reached the screen, so the detailed time looked identical on every task. Hovering a date in the list now shows the full stamp down to the second - "which one was updated first" is sometimes a question of seconds.
• ImprovedIn dark mode the surfaces the browser draws itself (open select lists, the date picker, scrollbars) stayed light; they now follow the theme. Also: the list column header stays pinned to the top while scrolling, the mention box no longer gets squeezed in narrow comment areas, the priority column shows a colour badge, and the Inbox and Filter Management pages use the same fixed header strip as every other page.
• SecurityPermission checks were tightened: bulk editing and some actions in the task panel now require the same permission as editing a task one by one.

Form sections, fill-in permissions and the formula field

• NewCustom fields can now be split into sections on the task form. Instead of twenty fields flowing in one list you get collapsible headings; Attachments, Subtasks, Linked Items and Diagrams moved into the same frame. Fields without a group stay in a single list, so your existing boards are unchanged.
• NewEach section can carry a rule for who fills it in: anyone, specific roles, the person named in a person field on the task ("the reviewer of this task fills in the review section"), or the task assignee. The rule is enforced on the server - a request from someone without access is rejected, bulk import included. The person who fills in a section is shown in its heading. Deleting a section does not delete fields: they and every value entered stay in place.
• NewA formula field: its value is calculated from other fields - multiply, divide, add, subtract or join side by side. The result can be a number or text, with decimal places and a unit ("days", "$"). Because the calculated value is stored, filters, sorting, list columns, CSV/Excel export and dashboard cards need no extra setup. It recalculates the moment a source field changes, even while creating the task.
• Heads-upScheduled jobs in your installation are now set up by the installer itself. Due-date notifications, review reminders and event cleanup were documented but had to be added by hand; in practice most installations never ran them and the notifications silently never went out. In this version the installer writes the jobs, runs one once to verify, and needs no extra configuration. WHEN UPGRADING, run the installer: updating the image alone does not set up the scheduled jobs.
• FixedA person-type custom field listed everyone in the workspace; now it only offers members of the board, and the picker works like the built-in "Assignee" field (avatar, search, multi-select). The name of someone removed from the board no longer disappears from the field either.
• FixedA required field, or a field with a default value, could block task creation when it sat in a restricted section. A field is now only required from the person who can actually fill it in.

Exports carry every field, and roles are the same everywhere

• FixedCSV and Excel exports now carry every field of a task. The export wrote the columns selected on screen, and since description is not a list column it never appeared in the file - yet the importer understands it, so re-importing your own export silently wiped descriptions. The same gap applied to start date, sprint, versions, class of service, reporter, parent task and every custom field. PDF export keeps the selected columns: it is a printed report, and twenty columns do not fit a page. Which rows are exported is still decided by the filters and sorting on screen.
• ImprovedThe importer understands the same fields. Sprints and versions match by name, class of service by its label, and columns that match no fixed field are matched against your board's custom field names. Parent links are resolved in a second pass, so a parent may appear further down the file. Sprints, versions, custom fields and parents with no match are reported by name and do not drop the row.
• ImprovedAdding members and groups is now one flow: the "Add member or group" dialog searches both people and groups, and the role is chosen before adding. People, groups and invite links now all offer the board's full set of built-in and custom roles - previously only the member row showed custom roles, which meant defining a custom role made it impossible to give to a group or an invite. Groups can also carry more than one role.
• FixedOn boards with a required field, a subtask created from the full form did not appear in the list until the parent task was closed and reopened. The diagram feature also has a single name now: the tab said "Diagrams" while the permission list said "Create schemas". And since the "Manage custom fields" permission also governs issue types, versions and task templates, its label now names all of them.

Attachments on the new task screen, and subtasks on boards with required fields

• NewYou can now attach files while creating a task. Files wait in the draft and upload as soon as the task is created; if one fails the task is not rolled back and the file is reported by name. Subtasks, linked items and diagrams are still not on the create screen - all three attach to an existing task and naturally come after it is created.
• FixedOn boards with a required custom field, subtasks could not be created from the task screen. The inline subtask box asks only for a title and could not fill the required field; the request was rejected without even naming the missing field, and the only thing left was linking an existing task. Required fields that have a default now fill in from the inline box, and when a required field has no default the full task screen opens with the parent already set.
• ImprovedBoard settings tabs you have no permission for are no longer shown. Previously you could open a tab and see its contents but do nothing; every attempt was refused. Also, adding a workspace admin to a board with a narrower role no longer weakens them: an admin who was not a member of the board could do everything, yet the same person added as a "developer" was blocked from some management actions.

Role permissions now describe what roles can actually do

• Heads-upThe "Viewer" role is now genuinely read-only. Until now it could not move cards, yet it could create tasks, edit every field, write comments and close sprints. After the upgrade it can only read and watch tasks. Make people who need to write a Tester or Developer, or define a custom role and tick the boxes you want. Your existing CUSTOM roles are not affected: create, edit and comment permissions are added automatically during the upgrade, so what worked yesterday still works. The one exception is the audit log - grant it explicitly to the roles that need it.
• NewCreating tasks, editing tasks and writing comments are now boxes in the role matrix. Until now none of the three was tied to a permission: anyone on the board could do them, and since the matrix had no rows for them, nobody could see that. The same gap existed for uploading attachments and linking items.
• NewThe sprint permission now covers the whole lifecycle. The old "Start sprint" permission gated only starting; the same role could create sprints, delete them, and even complete them, carrying unfinished work along. It is now "Manage sprints". On kanban boards the box is no longer listed - kanban never opens a sprint screen, so the box controlled nothing there.
• NewViewing the audit log and editing diagrams are now separate permissions. The audit log is a record of who changed what and when, and anyone on the board could read it. Diagram editing was tied to the document permission, and because that box is not shown on task boards, there was no way to grant diagram editing on a task board at all.
• ImprovedThe interface now knows your permissions: people without them no longer see the "New task" button, the comment box or the audit log tab, and fields open read-only. Previously you filled in a form and were refused at the end. Watching a task needs no permission - adding yourself as a watcher is your own notification preference, not an edit to the task.

Multi-line custom fields were treated as empty even when filled in

• FixedTyping into a multi-line custom field and clicking away did not keep the value; only the field's own Save button carried it. On the new task screen that button means nothing, because the task is written with "Create" in the first place. So people saw their text on screen, pressed "Create", and were told the field they had just filled in was required. Clicking away now saves, the same as single-line fields. The field keeps its Save and Cancel buttons, and Cancel still discards what was typed.

Editing tasks on a board with a required custom field is fixed

• FixedA single required custom field on a board prevented other fields on that board's tasks from being saved. The symptom differed by field type, which hid the cause: multi-line fields showed a "required field" warning on their Save button, while single-line fields silently reverted to their previous value. The task screen saves each field on its own, and the server was treating any required field absent from that request as if it had been cleared. A field absent from a request is now read as "untouched". Actually clearing a required field is still rejected, and required fields are still enforced in full when a task is created.

People named in a person field can watch the task

• NewPerson-type custom fields gained a "people in this field watch the task" setting. When it is on, anyone named in the field is added to the task's watchers and receives status change and due date notifications too. Until now someone named in a field heard once and then nothing: a person set as "Reviewer" never saw that the work they were meant to review had passed its due date. The setting is per field and off by default; switching it on unconditionally for a field like "Requested by", which carries the same person across hundreds of tasks, would make their notification list unusable. People added this way appear in the watcher list and can remove themselves.

The field column on the task screen now looks like one thing

• ImprovedThe field column on the right of the task screen is a quiet column: most values sit as plain text and highlight on hover. Type, version and date fields, however, carried their own heavy frames; with three of fourteen rows being boxes and the rest text, the column looked untidy. Those controls are now quiet too, framing only on hover and while editing. The default class of service dropped its box; the colours on expedite, fixed-date and intangible carry meaning and were left as they are.

Custom fields on the task form were redesigned

• ImprovedCustom fields now look like a form. Fields used to sit in a single column with no heading and no control chrome: text and number fields were plain writing until clicked, a dropdown stretched across the whole row and a date field stayed narrow. With some fields looking like text and others like form controls in the same list, it was unclear which ones could be filled in. Every field now shares the same frame and height, fields lay out in two columns, and long text and multi-select span the row. The section has its own heading and required fields are marked with an asterisk.
• FixedThe placeholder on link and email fields, and the "checked by default" setting on checkboxes, were not saved when the field was created. Editing the field afterwards and setting the same value worked, but the initial definition silently forgot it.
• FixedA filled-in link field can be edited. Once a value was entered, clicking the field only opened the link and there was no way into edit mode. Clicking the box now edits, and clicking the link text goes to the address.

Boards go into folders, history and the audit log became readable

• NewYou can group boards into folders in the sidebar. A folder belongs to you: a colleague looking at the same board can keep it under a completely different heading, and nobody changes anybody else's sidebar. If you do not use folders, the list looks exactly as it does today.
• NewComments now appear in a task's history. Until now history showed only field changes, so understanding what happened on a task meant switching back and forth between two tabs. Writing, editing and deleting a comment all land on the same timeline, and a deleted comment leaves its trace.
• NewCustom field value changes on tasks now land in the audit log. Who changed a field like "Approver" or "Risk class" and when is now visible in the board-wide record as well, and can be picked out with the event filter.
• ImprovedCustom field lines in task history became readable. They used to print the field's internal key and raw value; now you see the field name and the option label, with product-supplied values such as priority in your own language.
• FixedCustom field settings could be created but not updated. The placeholder, default value and the "treat as a deadline" switch were saved when the field was first defined, but editing that same field afterwards returned an error.
• FixedEditing a workflow transition showed two rows in the list. Changing the required role on an existing transition left the old one in place and added the new one below it; a page refresh collapsed them back to one, so the record was right and only the screen was wrong.

Field settings were not saved, row selection on import

• FixedOn custom fields the placeholder, default value and "treat as a deadline" switch were not being saved: the field dialog rebuilt the settings object from scratch and silently dropped anything not listed there. Placeholders now also appear on number, link and email fields.
• NewOn import you choose which rows are taken; every row has a checkbox and there is a "select all". It used to be all-or-nothing, so removing one unwanted row meant splitting the file by hand.
• FixedRecords that already exist on the board are no longer duplicated on import. Export writes the task id, but import did not recognise that column: loading an exported file back recreated every row. A row whose id matches is now marked "already exists" and comes in unchecked.

Mentions, comment editing and field defaults

• FixedMentions with hyphenated usernames are no longer broken. Typing "@jane-doe" sent the notification to the right person, but on screen only "@jane" was highlighted and the rest trailed off as plain text. The mention list is easier to read too: the name and username competed for the same line in a narrow box and both were clipped.
• FixedEditing a comment now opens the same editor you write in. Editing was only a bare text box: no write/preview tabs, no formatting tools, no mention list, no attachments - two different surfaces for the same job felt like something was broken.
• NewCustom fields can carry a placeholder and a default value. A placeholder is a grey hint inside the empty box and is not stored; a default value fills the field in on a new task and does not touch existing tasks.

Person and date fields now notify

• NewYou are notified when your name is set in a task field. The whole point of a person-type custom field (Reviewer, Tester, Requester...) is to put someone's name on a task, yet nothing ever reached that person. The notification carries the field name and goes only to a newly added person; it can be turned off in settings.
• NewDate fields can behave as deadlines: turning on the switch in the field definition sends a notification when the date is near and when it has passed. The switch is off by default, because not every date field is a deadline.
• Heads-upPeople who can be set in a person field are now validated. This was never checked: even a non-member of the board could be set, and a notification would then invite them to a task they cannot open.
• FixedYou no longer have to click the handle on the left to type into a custom field option; the whole row was marked draggable and the browser treated a click on the text box as the start of a drag. The heading and spacing of the release notes section in the Updates tab were fixed too.

Excel support, WIP limits and approval permissions

• NewReal Excel (.xlsx) support, both for export and import. The CSV round trip no longer breaks accented characters either: in a Turkish locale Excel writes a file saved as "CSV" in ANSI, and reading it as UTF-8 mangled the text; the encoding is now detected automatically. Accented characters in PDF output are fixed too.
• Heads-upWIP limits now apply when a task is created, too. Until now they only applied on moves: a column saying "at most N items" still accepted a task created directly in it, so the limit did not do what it announced. Creating into a full column now tells you what the limit is; moving an item out makes room.
• Heads-upThe "Approve and reject" permission now does something: only people holding it can be named as approvers, and the choice is validated - previously even a non-member of the board could be named, and the approval never moved. The permission is on for the Editor and Commenter roles and can be tightened from the role matrix. Approval permissions were removed from task board settings, since the approval flow only exists in the document space.

Accessibility fix for the task panel

• FixedThe task panel is announced to screen readers as a dialog and carries an accessible name. In the previous release the create and edit screens moved into a shared shell, and this marker was lost in the move.

Export, bulk import and built-in fields

• NewThe list view can be exported to CSV and PDF. The file carries what is on screen: your filters, sorting and chosen columns. The CSV opens in Excel on a double click with accented characters intact. The Versions tab has a report too, and the list can be sorted - newest first by default.
• NewTasks can be created in bulk from a CSV. When you pick a file you first see what will happen: how many rows will be taken, which will be skipped, which columns were not recognised. Status, assignee, label, issue type and priority match by name. If a row fails it does not pass silently and the rest are still created; names with no match on the board are reported separately.
• Heads-upThe priority and estimation fields are now marked as built-in and can no longer be deleted. The product adds these two when a board is created; the card priority badge, the capacity report, sprint metrics and filters assume they exist, and deleting them left those screens silently blank. Teams that do not use them can now turn them off instead: a field that is off is hidden from forms and existing values are kept.
• FixedThe board activity stream now shows task events - creating, moving and assigning tasks never appeared there. Event names are readable now too.
• ImprovedThe right column on the task screen was widened: the assignee and label pickers were wider than their own column and overflowed. Priority options now follow the interface language, and about 40 strings that had stayed in English in the Turkish interface were corrected.

Release notes in your own language

• ImprovedIn Settings > Updates inside the app, release notes are now shown in the reader's language. Notes arrived as a single text written in Turkish, so an administrator using the English interface had to decide "what changed in this update" from text they could not read.
• ImprovedThe update steps now describe the recommended path from the documentation. The screen only showed the manual commands, while the install script also fills in settings the new version needs and does not ask again for anything already answered. Updating by hand is kept as a secondary option, with a note on what it leaves out.

One colour picker everywhere

• ImprovedBoard colour, workflow status colour, profile colour, label colour and custom field option colours now all come from a single palette. The lists used to live in each screen's own file and had drifted apart: board colour is asked in two places (creating a board and board settings) and the two lists differed, so a colour you could pick in settings was not available when creating a board.
• ImprovedColour codes are now shown alongside the swatches, and a brand colour outside the list can be entered anywhere a colour is picked. A swatch on its own never told you which colour was selected.
• FixedThe new-task screen opened in the wrong place: instead of a side panel, a window or full screen, it landed at the bottom of the page. The view you prefer now applies to new tasks as well.

One screen for creating a task

• NewA new task now opens in the same screen you edit one in. Until now there were two surfaces: a short summary form for creating, then the full screen once you clicked the task. The two field sets drifted apart, and every field added later landed on only one of them. The task reaches the server only when you press Create, so an abandoned attempt leaves nothing behind on the board.
• ImprovedThe quick-add box inside a column now opens the full screen, carrying the title you typed, on boards that have a required field. It only accepts a title, so on those boards the request used to come back rejected.
• ImprovedThe custom field dialog is larger, and the colour palette now shows each colour code alongside the swatch, with a custom colour input for a brand colour that is not in the list.
• NewNew installations arrive with eight ready labels: bug, feature, improvement, chore, docs, security, design, infra. The label list used to start empty. On existing installations, labels that already carry the same name are left alone.
• SecurityThe code that keeps login timing uniform has been updated.

Custom fields, admin permissions and dashboard visibility

• FixedA board with a required custom field could not accept new tasks: the create form did not show custom fields at all, so the server rejected every task for the missing value. The form now shows all of the board's custom fields and tells you which required one is empty.
• NewCustom fields can carry a description: a short instruction on what belongs in the field, shown when the user hovers the (i) next to it. Optional, filled in only where it helps.
• Heads-upOnly a superadmin now sees every board. Previously any administrator saw all boards and could open one they were not a member of, so a closed workspace was not possible. An administrator now sees only the boards they can reach - if they need to work on one, they are added as a member and that action is recorded in the audit log. Administrators who see boards they are not members of today will no longer see them after this update.
• NewPermanent user deletion was added (superadmin only). Deactivation keeps the records; permanent deletion removes the user and their own activity records and cannot be undone. If the user has comments, approvals or reviews the deletion is refused - that content belongs to the team - and you are pointed to deactivation instead. A superadmin can now also assign another superadmin from the interface.
• FixedThe "My tasks" card also listed tasks you opened and handed to someone else; it now lists only what is assigned to you. The colour palette opened outside the screen when creating a custom field. After creating a new release, the list view showed its identifier instead of its name.

The login lockout now belongs to a person, not an office

• FixedIn teams behind a single network address, one person's failed password attempts locked out their colleagues: the counter was tied to the address alone, so everyone sharing it fell into the same bucket. The counter is now per person. A second ceiling still guards against bulk attempts from one address, so protection is not weakened, and a successful sign-in clears both counters.
• FixedEntering an invalid email on the login screen showed a message that ignored the interface language; it now follows it.

Fixes to task assignment, the login screen and GitLab import

• FixedA task could be assigned to someone with no access to the board: they received a notification, clicked it and could not open the board. The assignment list now shows only people who can reach the board (including access through a group). Assigning a task does not grant access - you add the person to the board first. Existing assignments are preserved.
• FixedEntering a wrong password reloaded the page and showed a generic "network error": a rejection on the login screen was being confused with an expired session. It now says exactly what happened.
• ImprovedGitLab import now brings issue comments over, along with the due date, the assignee and the closed state. Tasks imported earlier get their missing comments filled in without duplicating anything. When the GitLab authorization lapses, the message now says what to do instead of showing a server error.
• ImprovedThe sign-up screen no longer asks for a username - it is derived from your full name, and a clash with an existing one is resolved automatically. The login lockout now builds up only from failed attempts; a successful sign-in clears the counter and the remaining time is shown on screen.
• Heads-upThe document review process was removed from the task screen. It was designed for documents: it stamps the approved version and locks the content during a round, and since tasks have no version those fields stayed empty. The approval flow on tasks is unchanged.

The login lockout no longer blocks normal use

• FixedThe login lockout counted successful logins too: the fifth person signing in from the same network was locked out for 15 minutes even with the right password. The lockout now builds up only from failed attempts, and a successful sign-in clears the counter. The limits were raised as well.
• FixedA locked-out user saw a generic “network error”, assumed the password was wrong and kept trying, which extended the lockout further. The message now says what happened and how many minutes remain.
• ImprovedErrors in the sign-up form now appear under the field they belong to. The form showed only the first error, so the username warning masked the password warning and someone fixing their password kept seeing the same message. The texts follow the interface language now, the username is derived from the full name, and hyphens are accepted.

Internal-network installs work in one step

• FixedOn internal networks without a domain name the installer now finishes in one step. If the server has no domain name it detects the server address and offers it as the default, skips the certificate email, and serves HTTPS over the IP address. Previously browsers connecting over an IP address got a connection error.
• ImprovedRemoving the browser warning on installations that use a self-signed certificate is now simple: the root certificate is placed in the install directory as myway-root-ca.crt, ready to be installed as a trusted root on client machines.
• Heads-upDo NOT use a name like myway.localhost as the install address. Such names resolve to the local machine everywhere, so another computer on the network never reaches the server. Outside a single-machine trial, use the server's domain name or IP address.

You choose the published port during setup

• NewThe installer now asks which port the application should be served on. If something else already uses 80 and 443 on your server, you can pick a pair such as 8080/8443; your choice is stored and not asked again on later upgrades. The default stays 80/443, so existing installations are unaffected.
• Heads-upChoosing a non-standard port means no automatic certificate. The certificate authority connects from the outside to ports 80 and 443 to validate your domain, which cannot happen on another port. In that case the installer falls back to a self-signed certificate and browsers show a warning. For a trusted certificate, either stay on 80/443 or put MyWay behind your existing TLS-terminating proxy.
• FixedThe explanation screen did not appear when the license key was entered incorrectly. The page that reports an invalid key redirected onto itself and the browser showed only a redirect error, leaving the installer with no idea that the key was the problem. The page now opens directly.

Document permissions split apart, Turkish interface reworked

• Heads-upPublishing, deleting and document settings are now separate permissions. Previously the "edit documents" permission alone meant writing, deleting and publishing; in a quality system the "can write but cannot publish" distinction is standard. Templates, code series and page permissions were also separated from member management: a quality manager no longer needs the right to add members in order to define a template. The upgrade narrows nobody's access - roles that can edit documents today received publish and delete as they were; restricting them is one click in the role matrix.
• ImprovedThe review report now shows who raised each finding. Until now the audit report carried only the name of the person who dispositioned it; the author appeared nowhere. Both the on-screen report and the PDF now show "Raised by" and "Dispositioned by" separately.
• ImprovedMixed-language wording in the interface was cleaned up. 125 half-translated strings were corrected across the product, and the Turkish terminology was made consistent throughout.
• FixedIn document spaces, collapsing the left menu now widens the document as well; previously the reclaimed space was used only when the page list was collapsed.
• FixedTables are back in PDF exports, the diagram editor no longer opens underneath the page header, task links of a deleted diagram are cleaned up, and the review badge updates without a page refresh once a document is published.
• FixedTwo display issues in the roles screen were fixed: on newly created boards the member role list came up empty, and built-in role permissions appeared incomplete in the matrix. Authorization was correct in both cases - only the screen was wrong.

Diagrams in documents, real Word output, and approval notifications

• NewYou can draw diagrams inside documents and tasks. While editing a document, the diagram button opens a full-screen editor; saving places the diagram into the document, and clicking it opens the editor again. The same diagram can be used in several documents as a single record rather than a copy. Every diagram keeps a version history you can roll back to, and rolling back does not erase history - it is recorded as a new version. Before deleting one, you can see which documents and tasks reference it.
• Heads-upThe drawing editor runs on your own server: your diagrams never reach a third-party service and the editor has no outbound access. Air-gapped installations need no extra setup step - the editor ships with the product. The cost is size: the application image grew from about 345 MB to 515 MB, so keep roughly 1 GB of extra free disk during an upgrade.
• ImprovedWord export is now a real .docx file. What you downloaded before was HTML with a .doc extension; Word could warn about it and Google Docs or LibreOffice could not open it fully. More importantly, embedded images were missing - diagrams, images, tables, lists and the table of contents now all land correctly in the Word document.
• NewYou are notified when an approval reaches you. When an approval chain starts, the person whose turn it is gets both a bell notification and an email; in a sequential chain only the current approver is notified, in a parallel one everybody is. When a decision is made, the requester is informed. The approval switch under Settings > Notifications did not actually control anything until now; it does.
• Heads-upA document can no longer be published while an approval is still pending. The publish gate previously considered only reviews, so publishing during an open approval chain was possible - which defeated the approval exactly when it mattered.
• ImprovedIn document spaces the page list can now be collapsed on desktop too and your choice is remembered; with the panels closed the document uses the space that frees up. You can also share dashboards and saved filters with people and groups, star the ones shared with you, and choose which page opens when you sign in.
• FixedFor people using the dark theme, diagrams appeared black, the confirm button in document version history showed a code instead of a label, and the group selectors in board settings stayed white. All three are fixed.

Share a dashboard, and let everyone keep their own favorites

• NewYou can now share a dashboard you built with people and groups. “Share” in the header lets you pick who sees it; they find it in their own list under “Shared with you”, so nobody has to rebuild the same view by hand. A shared dashboard stays read-only on the other side: editing, adding cards and deleting belong to its owner. Anyone who wants their own arrangement takes a copy in one click, and that copy is entirely theirs.
• Heads-upSharing a dashboard is not sharing data. Every card shows the data its viewer can access; a card pointing at a board you cannot see says so plainly instead of drawing an empty chart. Personal cards such as “Assigned to me” show each viewer their own work. A dashboard shared with a group follows group membership: whoever joins starts seeing it, whoever leaves stops.
• ImprovedFavorites are now personal. You can star a dashboard or a saved filter that was shared with you; until now the star lived on the item itself, meaning it was the owner’s preference and never appeared on shared ones. Your star does not change the sharer’s list, and theirs does not change yours.
• NewYou choose where you land when you open the app: your first board, the dashboard, or the inbox (Settings › Profile). You can mark one dashboard as your default; opening the dashboard section brings that one up first, or the first of your favorites if you have not set a default. A dashboard shared with you can be your default too.

Quality documents: codes, versions and a stricter review

• NewDocuments can now carry a code. You define a series in board settings (prefix, separator, digits) and bind a page template to it; every document created from that template receives the next code automatically: MAN.4-TL.01, MAN.4-TL.02 and so on. The code appears in the tree, in search, in the document header and in PDF/Word exports. A deleted document’s code is never reissued, so no two documents can share a code in an audit. Codes can also be entered manually (moved documents keep theirs), and changing a code is a board-admin action recorded in the audit log.
• NewDocument versions are tracked. A new document starts as 0.0 draft, becomes 0.1 on first save, moves to 0.2 and 0.3 through review rounds, and rounds up to 1.0 when published. Editing a published document makes it 1.1; publishing again makes it 2.0. Every entry in the version history shows which version it belongs to, and published versions are highlighted. Version and code are separate fields: the code is the document’s permanent identity.
• ImprovedReviews got stricter. While a review is open the document’s content and title are frozen (they reopen for the rework round), so everyone looks at the same version. Findings receive permanent numbers (#1, #2) that match in the panel and in the audit report: saying “the third finding” in a meeting now points at exactly one thing. The published version is stamped onto the review (“1.0 published”) and never changes afterwards.
• ImprovedThe table of contents now lists headings deeper than level four, is included in PDF and Word exports, and works in editing mode. In some documents clicking a heading silently did nothing; the page now actually scrolls.
• ImprovedWord import was fixed: no links at all were carried over, not even external ones, and they are now preserved (the editor toolbar also gained a link button). Word’s own table-of-contents block is dropped on import, since its page numbers are meaningless and it duplicated the product’s live TOC. If a file name starts with a document code, that code is suggested during import. Word import is now available on every document page; it was missing from the menu on documents created from a template.
• ImprovedConfirmations now use the product’s own dialog. Decisions such as deleting, cancelling and publishing appear in a window that matches the theme and language instead of the browser’s box, and irreversible actions are marked in red.
• FixedWhen creating a board, the “copy settings from another board” list is filtered by board type: picking a document space for a task board produced a board without page templates. Template icon names are now translated in both languages, and error messages say which field they came from.

Board settings now sit in the same place everywhere

• ImprovedThe board settings button lived in the top bar on document spaces but inside the board header on task boards. There is no reason for the same button to move around depending on the board type; both now sit in the top bar.
• ImprovedThe sprint screen is one row shorter. The average cycle time occupied a row of its own with the rest of it left empty; it now sits next to the task counters. The same figure was shown somewhere else in list view, and that has been unified too.

Connecting GitLab now needs a single scope

• FixedThe application asked GitLab for two scopes at once (api and read_user). If either one was left unchecked on the GitLab side, connecting failed with "The requested scope is invalid, unknown, or malformed" and did not say which one was missing. read_user was never actually used; it became mandatory purely because it was requested. Only api is requested now - a single box to tick during setup.
• ImprovedExisting connections are unaffected: since api is already granted, asking for a narrower scope does not require re-authorisation.

GitLab integration now fixes itself on update

• FixedThe previous version generated the missing GitLab keys during installation, but that only reached installations that re-ran the installer; anyone who refreshed just the application image still saw the integration fail. When a key is not provided the application now derives it from its own session key: upgrading is enough, you do not have to add anything to your configuration file.
• Heads-upIf you set the keys explicitly in your configuration file nothing changes - your value always wins and stored access tokens stay readable. Derived keys depend on your session key: if you rotate it, the GitLab connection has to be reconnected once. Set the keys explicitly if you would rather avoid that.
• ImprovedThe integration error now names the setting that is missing; it used to say only "not configured", leaving the administrator with nothing to check.

GitLab integration now works on your own server too

• Heads-upThe update procedure has changed: after extracting the new package, run ./scripts/install.sh. The installer is safe to re-run - it never overwrites values you already have, only fills in settings the new version needs, and does not ask again for answers you gave before. Previously an update refreshed only the application images and never added new settings to your configuration file. The GitLab fix below reaches your existing installation only through this step.
• FixedGitLab integration could not connect on self-hosted installations. One of the two keys required at setup was never generated; the connect step failed with "GitLab integration is not configured" and gave no hint about what was missing. Both keys are now generated during installation.
• FixedOpening a task through a direct link showed "GitLab not connected" in the commit, merge request and pipeline panels. The same task worked when opened from the board, which made this hard to spot. In that view the issue type was also missing and clicking a linked task did nothing.
• ImprovedIf a document is edited after its review completes, the panel now says so: the approved version and the current version are shown side by side. Previously it simply read "approved", even though the reviewed content might no longer be what is on screen.
• FixedText fields on the review screens did not match the rest of the interface and appeared as white boxes in dark theme. The "use the Publish button to publish" hint that stayed in the panel after a document was already published is gone as well.
• SecurityA dependency was updated to its current version.

The PDF report is in your language too

• FixedThe review report was translated on screen but the PDF still showed technical values: ready instead of “Ready to publish”, accepted instead of “Accepted”, critical instead of “Critical”. Status, comment severity and decision names now follow your interface language in the PDF as well.

The review report is easier to read

• ImprovedThe report now opens with the document it belongs to and the state of the review. Comment severity and decision outcomes are shown as proportion bars rather than bare counts, and each decision carries a severity-coloured stripe so critical items stand out at a glance. The PDF output follows the same layout.
• FixedThe downloaded PDF used "Review report" as both its filename and subtitle instead of the document name.

Formal document review

• NewYou can put a document through a structured review before publishing it. You pick the reviewers (people or groups) and a deadline; they leave comments, you decide each one (accepted, accepted with conditions, rejected, duplicate, deferred), address the accepted ones and move to final approval. If someone says “I have comments” during final approval the review returns to disposition and the round counter advances, so past rounds never blur together. It works for tasks too.
• NewThe audit trail is complete: a rationale is required for rejections and conditional acceptances, the reviewed version and the approved version are both recorded, and the report shows who took part and who never opened the document. The report downloads as a PDF, and when a document goes through several reviews the earlier reports stay available.
• Heads-upOnce you start a review on a page, that page cannot be published until the review finishes. Pages without a review are unaffected. A Publish button was added to the editor so pages can be published at all - previously the page status could not be changed.
• Heads-upSelf-hosted installations: review deadline reminders need a daily scheduled job. `scripts/review-reminders.sh` is now in the package and the installation guide has a scheduled-jobs section. If you skip it the product still works, those reminders simply are not sent.
• ImprovedThe document editor toolbar was simplified: less-used actions (watch, duplicate, permissions, Word import, PDF/Word download) are now grouped in a single menu.

File size limit raised to 25 MB, and now configurable

• NewUploads were capped at 4 MB, a number inherited from the product’s former hosting environment that made no sense once you run it on your own server. The default is now 25 MB, and you can raise it up to 500 MB in your own installation. The limit is the same everywhere: task attachments, page attachments, comment attachments and images pasted into the editor. Accepted file types are unchanged (images, PDF, Word, Excel, TXT, CSV, ZIP).
• ImprovedThe board list loads a little faster.

Every warning message is now in your own language

• ImprovedThe previous release translated the most common warnings; this one completes the rest. Permission warnings, sign-in errors, "invitation not found" and "filter not found" messages, GitLab connection states, and license and update warnings now all appear in your interface language, including the notice shown when your session expires.

The login screen now opens in your browser’s language

• FixedAnyone visiting for the first time saw the login, sign-up, password reset and invitation screens in Turkish, even with an English browser. These screens come before sign-in, so the account preference is not known yet; the browser’s language setting is now taken into account. If you picked a language yourself, your choice always wins.
• ImprovedThe language stored on your account is now applied to the interface when you sign in from a new browser, so the interface and your emails stay in the same language. Common warnings ("that email is already in use", "you cannot remove the last administrator") are also shown in your language now.
• FixedThe saved-filter card on the dashboard was rendered with too much padding on every side; it now matches the other cards.

Emails and interface text now use the right language everywhere

• FixedNotification emails were sent in Turkish even when the recipient used the interface in English. The reason: language was only read from the browser, and because notifications are triggered by someone else’s action, the recipient’s preference was never visible. Language is now stored with the account and emails follow the recipient.
• FixedBoard invitations went out in the inviter’s language. If the address belongs to an existing user, their language is now used, so an admin working in Turkish sends an English invitation to a colleague working in English.
• FixedIn Filter Management, field names (Status, Assignee, Due Date...) stayed in Turkish even in the English interface. Workflow categories in board settings had the same problem in the opposite direction. Both are fixed.
• Heads-upYour language preference is written to your account when you use the language switcher. If you have never changed it, your current interface language is saved the next time you open the app; nothing else is needed from you.

Status and due-date notifications, and every notification can now be switched off

• NewWhen a task changes status, the people watching it, its assignees and its reporter are notified. Whoever made the change is not notified about their own action.
• NewTasks due tomorrow get a reminder, and tasks past their due date that are still open get a warning. Each task triggers these once; the same reminder does not repeat every morning.
• ImprovedSettings → Notifications now has separate email and in-app (bell) switches for every type. Bell notifications could not be turned off at all until now: even someone who disabled email still saw an entry in the bell for every event.
• Heads-upDue-date warnings need a daily scheduled job. Schedule scripts/due-date-notifications.sh from the installation package to run once a day; the steps are on the Installation page. Without it, status notifications still work but due-date warnings are never sent.

New boards can be set up from an existing board’s configuration

• NewWhile creating a board, choose "Take settings from another board" and pick one: its workflow (columns, colours, work limits, transitions and the role required for each), custom fields, issue types and roles are set up on the new board. Configure how your team works once instead of rebuilding it for every new project.
• Heads-upTask templates come along by default, members do not; both are checkboxes. Bringing members over unintentionally would silently grant access to the board. Tasks, sprints, releases, comments and the GitLab connection are never copied, and the new board gets its own key so task numbers stay separate.
• NewPick a document space as the source and its page templates and roles are copied instead.

Saved filters can now be shared with people and groups

• NewPick people or groups from the menu next to a filter and they will see it under "Shared with You", ready to run. Your team no longer has to rebuild the same view one by one. Only the owner can edit or delete the filter.
• Heads-upSharing never exposes new data. Someone running a shared filter only sees work from the boards they can already access, so a filter spanning several boards shows each person their own slice. When you share with a group, access follows group membership: joining the group grants it, leaving takes it away.

The last few board emoji are now badges too

• FixedThree places still showed the old board emoji after the previous release: the start of each row in the My Issues widget, the invite acceptance screen, and the "you were added to a board" email. All three now use the board badge, so boards look the same everywhere in the product.

One icon language across the interface, and boards now show a key badge

• ImprovedEmpty states, warnings, quick filters, board type options and document templates now use a single icon family instead of emoji. Emoji is drawn differently on every operating system and ignores your theme colour, so the interface looked different from device to device.
• Heads-upBoards now appear with a key badge: the initials of the board name, in the board’s own colour. Creating or editing a board no longer asks for an emoji, and because the badge is derived from the name it updates itself when you rename a board. Your boards’ previous emoji was not deleted, it is simply no longer shown.
• NewThe role requirement on a workflow transition can now be edited. Previously, changing who is allowed to make a transition meant deleting it and creating it again.
• FixedA sprint’s completion time is now recorded correctly. When a sprint was closed earlier or later than its planned end date, the velocity chart could place it on the wrong date.

Task numbers now follow each board’s own key

• FixedOn boards without a defined key, a new task could take its number from another board’s pool: on a board whose tasks ran WEB-1, WEB-2, a newly created task was numbered with an unexpected key. Each board now uses its own key.
• Heads-upThe update assigns a key to boards that had none: the key already used by that board’s tasks, or one derived from the board name when it has no tasks yet. Existing task numbers are unchanged, and you can edit a board’s key at any time in Board Settings.
• ImprovedThe product name is now written consistently throughout the interface and documentation: MyWay.

Workflow templates now match the board type you pick

• FixedWhen creating a board, workflow templates are filtered by the board type you choose: a Scrum board can no longer be given a kanban flow, or a Kanban board a scrum flow. Changing the type switches the template to a compatible default, and keeps your choice when it is already compatible.
• ImprovedThe document space description now says what it offers: page hierarchy, version history, comments and approval flow.

User groups can be added to boards and mentioned in comments

• NewYou can add a user group to a board with a role, and every member of the group gains access. Adding someone to the group later grants board access automatically, and removing them revokes it. You no longer edit boards one by one. If a person is both a direct member and a member through a group, the broader permission applies. (Board Settings → Members → Groups.)
• NewYou can mention groups in comments: typing “@team-name” notifies the group members who have access to that board. Each group gets a mention name derived from its title (“Product Team” → @product-team), and typing “@” in the comment box suggests groups alongside people. For large groups everyone gets an in-app notification, while emails are capped.
• ImprovedA collapsed board column is now a full-height vertical strip; previously it shrank to the header and looked unfinished in the middle of the board.

Email notifications, password reset, and task notifications in the bell

• NewYou can enable email notifications by connecting your own mail server (Exchange, Postfix, Google Workspace, AWS SES; all over SMTP). You get an email when you are added to a board, assigned a task, or mentioned in a comment; choose which events you want under Settings → Notifications. If no mail server is configured the product works exactly as before: invite links are shared from the screen.
• NewUsers who forget their password can now reset it themselves. The link is valid for 60 minutes and single-use; changing the password ends all open sessions for that account. (If email sending is not configured this flow is hidden and an administrator resets the password.)
• NewTask events now also appear in the notification bell: being added to a board, being assigned a task, and being mentioned in a task comment. Clicking a notification takes you straight to the task, and the row shows which task it is. (Previously the bell only showed document page events.)
• NewBoard invites can be sent to an email address. If an invite was sent to a specific address and the link is opened with a different account, a warning is shown and you can switch accounts. The link is still shown on screen as well.
• ImprovedEmail address verification was added after sign-up. Verification does not block sign-in. A dismissible reminder appears at the top and you can resend the link. In installations without email sending this step never appears.
• FixedWhen a session expires you now return to the page you were on after signing in; previously you landed on the home page.
• FixedA user who arrives via an invite link and signs up is now routed back to the invite screen and their board membership is created without interruption.

Document permissions now enforce roles, and mobile use was overhauled

• Heads-upPage permissions in the document space now enforce roles: Editor edits, Commenter only comments, Viewer only reads. After upgrading, people in Commenter and Viewer roles who could previously edit pages lose that ability. Custom roles you defined yourself receive the new permissions unchecked. Review “Edit pages” and “Comment on pages” under Space Settings → Roles, otherwise people in those roles will have read-only access.
• SecuritySecurity updates were applied to access control, session termination and request rate limits, and a dependency advisory was resolved. Upgrading is recommended.
• ImprovedPhone and tablet use was overhauled end to end: the “New task” button and view tabs no longer disappear on narrow screens, the document page list can be collapsed, panels open full-screen and close with ESC, and list rows no longer break when scrolled sideways.
• ImprovedAnimations are disabled when “reduce motion” is enabled in the operating system.
• FixedIn saved filters, “Apply” led to the wrong screen for filters not tied to a single board; results are now listed on the Filters page.
• FixedThe notification bell overlapped buttons on some pages.

Dates and relative times now follow the interface language

• ImprovedCalendar headers, timeline labels, the audit log, attachment dates, membership dates and PDF export were formatted in a fixed language; all of them now follow the selected language.
• ImprovedRelative times such as “5 minutes ago” are translated too. Previously they appeared in English in every language.

Label management

• NewLabels can be created, renamed, recoloured and deleted from Settings → Labels. Labels are workspace-wide; all boards share the same pool.
• FixedOn a clean installation the label list stayed empty with no way to add one.

Custom fields, priority and translation consistency

• NewNew boards now also get a default “Priority” field; previously only “Estimation” was added, which left the priority badge, priority board and filters empty.
• NewURL and Email custom field types can now be picked when adding a field.
• FixedClicking the custom field colour palette could crash the page; it now opens reliably and closes on outside click or Escape.
• FixedThe timeline PDF report and the dashboard “By assignee” chart were rendered in a single language regardless of the interface; both now follow the selected language, including date and percentage formats.

The license screen reports the correct state

• FixedWhen license information could not be read (e.g. viewed by a non-admin account) the screen said “license not enforced”. The exact opposite for a licensed installation. Missing permission, connection errors and the actual state are now reported separately.

Seat limits: the foundation of the free plan

• NewLicense keys can now carry an active-user limit; the 10-user free plan is built on it. Settings → License shows an “N / 10 users” indicator.
• ImprovedExisting keys are unaffected. Any key without a limit counts as unlimited. When the limit is reached only adding new users stops; existing users keep working and nobody is locked out.

Download packages from inside the app

• NewA “Download package” action was added to the Updates tab: you can fetch a new version from inside the app with your stored license, without digging up the purchase email.
• ImprovedInstallations on the default accent colour were migrated to the new brand colour automatically; installations with a deliberately chosen colour were left untouched.

Visual refresh

• ImprovedA calmer, more professional theme: a softer accent colour, more restrained shadows and cleaner icons. Layout and density are unchanged: a reskin, not a re-layout. The accent colour remains customisable in Settings.
• SecuritySecurity updates were applied to dependencies.
• FixedBuilt-in page templates (Meeting Notes / PRD / Retro) did not appear in document spaces; the “New page” menu was clipped by the sidebar.

License traceability

• ImprovedEvery license key now carries a unique identifier, and a key-confidentiality clause was added to the licence agreement.
• SecurityA security update was applied to the image-processing dependency.
• FixedAlignment fixes in the sidebar user menu and the workspace “Members” section.

License validation and update checks

• NewA valid license key is required to run; when a key expires the installation does not stop immediately. A grace period applies.
• NewSettings → Updates can check whether a newer version is available.
• ImprovedThe installer and all customer-facing text were translated into English.

First self-hosted release

• NewThe first package you install on your own server. Extract it, run the installer, and the first user to sign up becomes the administrator.