MyWayv1.92.0

What's new

MyWay is under active development. Every released version and what it brought is listed below. Newest first.

Which version are you on?

Pick the version you have installed: the list narrows to the changes since then, and anything you need to do after upgrading is collected here.

v1.92.0

Document attachments carry the version they belong to, so the old and the corrected file no longer get mixed up

  • NewPage attachments now carry the document version they belong to. Files on the page when a review starts take the reviewed version (e.g. 0.1 or 1.1), and a corrected file added after the review takes the version it was published in (e.g. 1.0). The version shows next to the file name and in the downloaded file name (Report (v0.1).docx); a file that has not been part of any version yet is marked "working". Before, every file on the page at publication got the publication number.
  • Heads-upExisting attachments are stamped once by the upgrade, from the first review or publication after they were added. This release includes a database change; the install script takes a backup first and applies the change itself.
  • FixedIn the PDF and Word export of the specification, the requirement sentence was set in bold like a heading; now only the section number and the key are bold.
  • FixedIn the command-line tool, myway version create printed the tool’s own version number instead of creating a release version; fixed.

v1.91.0

Confirmation before deleting, time on attachments and versioned download names, collapse all in the specification navigation pane

  • ImprovedDeleting a task or page comment, removing a subtask or parent link, and removing a link between two items now ask for confirmation, so a stray click no longer loses a record.
  • ImprovedPage attachments (including documents under review) and the attachment list of published versions show the date added with hours and minutes. When picking a Word file as the heading source of a review, files with the same name are told apart by the time they were added.
  • NewA file downloaded from a published version gets that version in its name (Report (v1.2).docx), so versions of the same document do not get mixed up on your computer. The stored file name does not change.
  • NewIn the Moors list view, with a single item selected, the More menu offers Add above, Add below and Add inside, as in the specification, to add a heading, requirement or information item.
  • ImprovedThe specification navigation pane got collapse all and expand all buttons; when a heading is collapsed, a note in the pane says so with a one-click link to open it. Filters were rearranged: the number of active filters is in the heading, and kind and status are in separate groups.
  • FixedThe content of the automatic update box on the Updates tab sat flush against its edge; fixed.
  • Heads-upThis release includes a database change; the install script takes a backup first and applies the change itself.

v1.90.1

covers v1.90.0 - v1.90.1

Updating from inside the app, signed update packages and a maintenance page

  • NewUpdating from inside the app (optional). When turned on at install (./scripts/install.sh --auto-update), a super administrator can install a new version from Settings > Updates right away or schedule it for a later date and time. A small agent on the server does the work: it checks for a request every minute, verifies the package signature, takes a backup and installs; the result, with details if something fails, shows on screen. Fifteen minutes before a scheduled update, a warning banner appears for every user. Off by default; --no-auto-update removes the agent.
  • NewDuring an update or restart, users see a maintenance page that refreshes itself instead of the browser’s error page, and return to where they were once the system is back.
  • SecurityUpdate packages are now signed by MyWay. ./scripts/update.sh verifies the signature and every file in the package before installing, and does not install a package it cannot verify.
  • Heads-upv1.90.0 was not published as an installation package; v1.90.1 contains all of its changes. This release includes a database change; the install script takes a backup first and applies the change itself.

v1.89.0

Choose what goes into the document when you export the specification; a resizable navigation pane and drag and drop into descriptions

  • NewWhen exporting the specification you can choose where section numbers appear (everywhere, only on headings, only on requirements, nowhere), which item types go into the document, whether item keys are written, whether requirements link back to their record in MyWay, and whether descriptions, type and status, and attributes are shown. The choices are remembered for the next export.
  • ImprovedThe specification navigation pane can be widened or narrowed by dragging its edge, like the side menu; a double-click restores the default width. Headings collapsed in the pane stay collapsed when you leave the page and come back.
  • NewFiles and images can be dragged into a task description even while it is closed; the editor opens and the file is added at the end.
  • FixedAn image picked with the toolbar upload button was not added to the description; on mobile, opening New board or search from the menu left the menu open and closed the dialog; an item reached from the navigation pane ended up under the top toolbar. All three are fixed.

v1.88.0

covers v1.87.0 - v1.88.0

A navigation pane in the specification and a document with a cover page and contents; System limits setting, search when picking a board

  • NewThe Specification screen has a navigation pane on its left that opens and closes: the Headings tab shows the document tree (a click scrolls the document to that item; with permission, a menu adds and moves items), and the Results tab lists search matches with a highlighted snippet. It filters by item type and status; search marks the matches in the document and can show only the matching items.
  • NewThe PDF and Word export of the specification has a cover page (version and version name, status, date), a revision history table and a table of contents; in the PDF the contents are numbered by page and clickable. Every page shows the document name, version and page number. The font is Arial (in the PDF, Arimo, which has the same metrics).
  • ImprovedA calmer specification screen: the toolbar stays pinned at the top at full width, buttons no longer disappear while you type a search or apply a filter but are only disabled, and the match count sits inside the search box. Notices about the version shown, collapsing and truncation share one fixed-height status line, and the document is shown as a page set apart from the background.
  • NewIn the Moors list view, several selected items can be moved up or down together and indented or outdented from the More menu. The selection keeps its order; if some items cannot be moved, you are told how many were skipped.
  • NewA super administrator can change the largest file size, the number of tasks selectable in a bulk action, the number of rows taken by an import, the size of a board that can be copied with its items and the per-user write limits per minute in Settings > System limits. Each field shows its default and allowed range, and changes go to the audit log. Sign-in attempt limits cannot be changed.
  • ImprovedEvery dropdown that picks a board (new board source, dashboard widgets, filters, group board sources, board code assignment, page move) is now searchable, and long board lists get a search box on top.
  • ImprovedIn the list view, every row with subtasks can be collapsed or expanded with one click. When rows are collapsed, a note above the list says so with a one-click button to undo it.
  • FixedA baseline created by Publish and the draft it came from can no longer be deleted, so the evidence of the publication is kept. The help text in the new board dialog now matches the Copy items with their relations option. Clicking the search box of a searchable list inside a dialog closed the whole dialog; fixed, and Escape now closes only the list.
  • Heads-upThis release includes a database change; the install script takes a backup first and applies the change itself.

v1.86.2

Security update

  • SecurityThe library used to send email was updated following published security advisories. Updating is recommended.

Earlier versions

Click a version to see its details.

v1.86.1

covers v1.86.0 - v1.86.1

Moors: one-click review of the current state, baseline selection, search and collapsing in the specification

3 new · 2 fixed

  • NewThe Review the current state button on the Baselines screen freezes the board’s current state as a new draft baseline and opens the review for it. If the latest draft already matches the current state, no new copy is taken.
  • NewThe Specification screen can show the current state or any baseline (baselines are read-only), and export downloads whichever source is selected. You can search titles, keys and descriptions; matches are shown together with their parent headings.
  • NewRows with items beneath them can be collapsed in the Specification and List screens, and the specification has collapse all and expand all; the choice is remembered in the browser. In the List screen, a single selected item can be moved up or down and indented or outdented from the More menu.
  • FixedReviews and approvals can only be opened on the latest draft baseline. Before, they could also be opened on a published version or on a draft that a newer one had replaced, and once complete they said "Ready to publish" but could not be published. A published draft is now marked "Published as 1.0", and its review and approval show the published version; earlier publications are marked by the upgrade too.
  • FixedA baseline can no longer be taken on a board with no items; an empty baseline opened its review without a title. If the board has changed since the selected baseline, the review panel shows a warning. Option fields are exported with their display name instead of the stored code.

v1.85.0

Template boards, copying a board with its items, drafts and publishing in Moors, specification export to Excel, PDF and Word

1 heads-up · 4 new · 4 improved · 1 fixed

  • Heads-upMoors baselines start as drafts. The first baseline is now 0.1, and a board with no baselines shows as draft 0.0. A new baseline always takes the next draft code (0.1, 0.2, 1.1); a major version (1.0, 2.0) is only created, with the same content, by Publish on the latest draft. Whether a completed review and a granted approval are required before publishing is set in the new Publishing rule section of the Moors settings; the default matches documents: review required, approval not required. Existing baselines with x.0 codes count as published and the others as drafts. If your team has been publishing without a review, turn the rule off in the settings.
  • NewA workspace admin can turn a board into a template from the Boards page. Template boards do not appear in the sidebar; they are listed in the new Templates tab on the Boards page and open read-only for every user. Their items do not show up in search, the inbox or dashboards.
  • NewWhen creating a board from another board or a template, checking Copy items with their relations brings over the item tree, order, parent-child structure, descriptions, custom fields and links between items. Numbering restarts at 1 with the new board’s key. Comments, attachments, baselines, assignees and sprints are not copied.
  • NewThe Moors Specification page downloads as Excel, PDF and Word. The document opens with the board name, the version (e.g. 1.0 · Published) and the source; section numbers, requirement keys, descriptions and attributes follow in reading order.
  • NewThe task screen has a new Parent task section: the parent is picked, changed or removed from the same place, both when creating a task and later. Like the other sections it can be hidden or reordered under Board Settings > Task Screen > Task sections; it is off by default on Moors boards.
  • ImprovedWith Keep open after creating on the new task screen, the screen stays open and the fields clear so the next task can be typed right away; status, type, sprint and label choices are kept.
  • ImprovedLabels can have a description, shown when picking a label and on hover. Label colors can be chosen outside the preset palette with a color picker or a hex code, and issue type colors accept hex codes too.
  • ImprovedWhen creating a GitLab branch, Add the task title suggests a name like issue/MYW-12-login-screen; long titles are shortened to fit the branch name limit.
  • ImprovedSearching the dashboard list matches the owner’s name as well as the dashboard name. The online indicator now follows real activity, so a tab left open in the background no longer shows someone as online for hours.
  • FixedMP3 and OGG audio attachments could not be uploaded; they can now be attached to tasks and played in the attachment list.

v1.84.1

covers v1.84.0 - v1.84.1

Uploaded files live on the server’s disk in every installation, video attachments play in the browser, myway attach fixed

1 improved · 2 fixed

  • ImprovedFile storage is simpler: attachments and images embedded in text are stored on the server’s own disk in every installation, with no external storage service needed. Installations on your own server already use the disk, so there is nothing to do; the backup script picks up the uploaded files as before.
  • FixedMP4 and WebM video attachments were served with the wrong file type, so they could only be downloaded, not played; they now play in place on the task screen. Markdown and draw.io attachments get the right type too.
  • Fixedmyway attach sent files without a type, so the server rejected the upload as an "unsupported file type". The type now comes from the file extension; run myway self-update to get the fixed CLI.

v1.83.0

A tidier backlog: completed sprints sit in a collapsed group below the list

1 improved · 2 fixed · 1 security

  • ImprovedCompleted sprints no longer pile up above the product backlog; they sit below it in a "Completed sprints" group that starts collapsed, most recently completed first. The backlog is no longer pushed to the bottom of the page as sprints accumulate. Which sprints are expanded or collapsed is remembered per board.
  • FixedAttachment, subtask and link sections hidden or set to start collapsed under Board Settings > Task Screen > Task sections still showed up open on the new task screen; the setting now applies when creating a task too.
  • FixedWhen renaming a saved filter, the name box reselected the whole name after every keystroke, so the second letter wiped out the old name. The name is now selected only when editing opens, and a single-letter fix works.
  • SecurityFollowing published security advisories, the HTML processing library used for document import and one dependency were updated. Updating is recommended.

v1.82.1

covers v1.82.0 - v1.82.1

Personal access tokens, the MyWay CLI, a connection to Claude Code and other AI assistants, and a security update

3 new · 1 security

  • NewPersonal access tokens: Settings > Access tokens creates a token for the command line, scripts and AI assistants. The scope is read only or read and write, and the expiration is 30, 90 or 365 days or none. A token is shown only once, when it is created, and acts with its owner’s permissions: it cannot do anything the owner’s board roles do not allow. The list shows when each token was last used, a token is revoked in one click, and creating and revoking are written to the audit log.
  • NewThe MyWay CLI: the myway command lists, opens, creates, updates, moves and assigns tasks, and handles comments, links, watching, attachments, bulk changes, sprints, versions, search, notifications, document pages (Markdown), reviews and approvals from the terminal. myway start MYW-12 takes the task, moves it to "in progress" and creates the git branch. Anything without its own command can be called with myway api. Every installation serves the CLI of its own version; the install steps for macOS, Linux and Windows (PowerShell) are in the settings tab.
  • NewAI assistants: myway claude-setup introduces MyWay to Claude Code, so Claude opens tasks, changes statuses, writes comments and checks reviews without a browser. For Codex, Cursor, Gemini CLI and GitHub Copilot, myway agent-guide adds the same instructions to the project’s AGENTS.md. CI jobs and scripts need no config file; the address and token are passed as environment variables.
  • SecurityFollowing a published security advisory, a size limit was added to requests reaching the server (file uploads are not affected, and the limit is generous for document and diagram saves), and the HTML sanitizing library was updated. Updating is recommended. This release includes a database change; the install script takes a backup first and applies the change itself.

v1.81.0

Board type in the sidebar, the parent task in the list and in exports, subtasks counted separately in list groups

1 new · 1 improved · 1 fixed

  • NewA small icon on the corner of the board badge in the sidebar shows the board’s type (Kanban, Scrum, Moors, document space, group); hovering shows the type’s name. A "Parent" column can be added to the list; CSV and Excel exports now include the parent task’s key, and importing an exported file keeps the hierarchy.
  • ImprovedIn list groups, the status header counts the top-level items in that status; subtasks shown under the group are listed separately, as in "+7 subtasks".
  • FixedSection settings in Board Settings > Task Screen, the subtask rules and the single-assignee setting did not reach the task screen until the page was reloaded. When advanced search or a filter matched a subtask but not its parent, the subtask appeared in no Kanban column; it now shows as a card in its own status. Searching by a middle or last name when adding members or picking people returned nothing; search now matches anywhere in the name and ignores accents. The type filter on the Boards page was missing Moors.

v1.80.0

covers v1.79.0 - v1.80.0

A critical security update, an editable Moors specification, heading numbering, document folders and assignment settings

3 new · 1 improved · 1 fixed · 1 security

  • SecurityThe application framework (Next.js) and an HTML sanitizing library used for PDF export were updated following published critical security advisories. Updating is recommended. This release includes a database change; the install script takes a backup first and applies the change itself.
  • NewThe Moors specification is edited in place: in the Specification tab each item’s menu adds a Heading, Requirement or Information above, below or inside it; items move up and down and are indented or outdented. Information needs no separate link; it belongs where it sits. Section numbers are recalculated on every change, and baselines keep the numbers from the time they were taken.
  • NewHeading numbering: in Board Settings > General > Numbering you can give section numbers to headings only; headings get 1 and 1.2, requirements are numbered after their heading as 1.2-1 and 1.2-2, and adding a requirement no longer shifts sub-heading numbers. New Moors boards start with this format and existing boards keep theirs. A Moors board can be given the "Verification / test definitions" level; on it, Coverage shows whether each test definition verifies a requirement through a "verifies" link.
  • NewFolders in the document tree: on a document board, "New folder" creates a folder that groups pages; a folder has no content, document code, publishing, review or approval. Selecting a folder lists its contents, and new pages or sub-folders can be added from there.
  • ImprovedTasks assigned to you are shown in the accent color on Kanban, the list, the backlog, filter results, group boards and dashboard tables. Automatic assignment from a person field on entering a status now assigns everyone in the field, and the rule can be set to "first person only". With "A task is assigned to one person" on in Board Settings > Task Screen, the assignee picker allows a single person. "Show more" in the inbox and "Load more" in the notification bell reach older entries; the newest 500 notifications are kept per person.
  • FixedOpening a task from a list filtered by search or label reset the filter and brought back the whole list. Sorting on Moors arranged only top-level rows; every level is now sorted, and with no sort chosen or when sorted by "Section" the list follows the order of the specification. Number field columns sort numerically (9 before 10).

v1.78.0

Tables and lists in descriptions and comments, task keys as links everywhere, branch lists for branches and merge requests, shareable board codes

2 new · 1 fixed

  • NewA task key such as NMD-228 written in a comment or description becomes a link to the task; only the keys of boards you can see are recognized. On Kanban cards, the backlog, the list, filter results, Coverage, Matrix, Specification and Baselines, linked items, subtasks and global search, right-clicking a task key and choosing "Open in new tab", or Ctrl/Cmd-clicking it, opens the task in a new tab.
  • NewWhen creating a GitLab branch the base branch, and when opening a merge request the source and target branches, are picked from a list of the selected project’s branches; typing a name still works. In Settings > Board Codes, a code marked "Shareable" can be given to several boards (for example a department code); the list shows the boards using it and each can be released separately.
  • FixedMarkdown tables in descriptions and comments were not drawn and showed as misaligned lines of | characters; lists starting with *, numbered and nested lists, checklists, quotes and horizontal rules also stayed plain text. They now look as on GitHub and GitLab, and wide tables scroll sideways. Document move arrows did nothing for documents with equal or gapped order numbers. When a list group is split across two pages, the header now reads "on this page / total". Comment results in global search went to the wrong address. A Markdown library used for document import was updated for security. This release includes a database change.

v1.77.1

covers v1.77.0 - v1.77.1

A separate permission for the GitLab integration, full rights for the superadmin on every board, and switching a board to Moors now sets it up

1 new · 1 improved · 1 fixed

  • FixedOn a board linked to several GitLab projects, when two projects had an issue with the same number (for example #21), import and webhooks wrote the second project’s issue into the first project’s task; matching now uses the project and the number. A task mixed up earlier has to be corrected by hand. Copying a Moors board made Heading and Information count as requirements and become deletable; they now work as on the source board. The list showed empty group headers with no rows. Typing "istanbul" in global search did not find titles starting with "İstanbul"; İ, I, ı and i now count as the same letter.
  • NewThe new "GitLab integration" permission opens the connection, projects, settings, import and the webhook URL and secret; a board admin can give it to specific people in role settings, and a workspace admin is no longer needed for the webhook details. On update, roles that can manage members also got this permission. The superadmin works with full rights on every board, even one they were added to with a lower role. When a Kanban or Scrum board is turned into Moors, the Requirement, Heading and Information types, the requirement fields and the level are added automatically; existing types and the workflow are kept. This release includes a database change.
  • ImprovedMiddle-clicking a task row in the list, or right-clicking the title and choosing "Open in new tab", opens the task in a new tab (v1.77.1 also fixed a normal click not opening the side panel). Review participants have "Select all", and an optional note can be added when accepting a comment. Saved filters show 20 per page. In Settings > Board Codes, a free code can be assigned to a board or released from it.

v1.76.0

covers v1.75.0 - v1.76.0

Moors: a Specification view, section numbers, a board level, baseline codes and reviews; sortable list columns and link conditions in search

1 heads-up · 4 new · 2 improved · 1 fixed

  • Heads-upThis release includes a database change. The install script takes a backup before updating and applies the change itself; on v1.67.2 and later ./scripts/update.sh is enough.
  • NewSpecification tab: the items on a Moors board flow in reading order like a document. Headings with their section number, requirements with their key, text, status and attributes, and unnumbered information paragraphs. Two new types build the document structure: Heading and Information; neither counts as a requirement or appears in coverage and the matrix. Section numbers (1, 1.1, 3.2.1) are calculated from the hierarchy and the permanent key (REQ-12) does not change. The Section column comes first in the list; it sorts and filters by prefix ("2" brings section 2 and everything under it).
  • NewThe level is now a board setting: you pick it when you create a Moors board (stakeholder needs, system, subsystem, software, hardware, interface or other). One board is one specification; a lower-level requirement links to the board above with "derived from" or "refines". On a stakeholder needs board Coverage does not look for a source. New boards have the types Requirement, Heading and Information; the kind of requirement goes in the new Requirement Class field (functional, performance, interface, safety, security, design constraint, environmental, usability, regulatory). Rationale and Acceptance Criteria fields come ready too; Priority and Story Point are set up switched off. Existing Moors boards keep working with the types they were set up with.
  • NewBaseline codes and reviews: every baseline gets a version code; the first is 1.0, a minor change makes 1.1 and a major change 2.0. A baseline can be sent to a multi-round formal review like documents, and a comment can be tied to a single requirement. The order of review and approval is chosen in board settings: parallel, review first or approval first. A baseline with a review cannot be deleted.
  • ImprovedOn Moors, Coverage and the Matrix now narrow with the top-bar search and filters too; Coverage columns sort, filter and resize, and hovering the source icon explains what it means. The tabs are grouped: List, Specification and Coverage in the top bar; Baselines, Kanban, Matrix and Releases under "More". The "parent of / child of" link cannot be picked on Moors, where the hierarchy is the document structure; existing links of that kind are kept.
  • NewLink conditions in search: search by link type and direction, no links at all, linked to a given item, suspect links and having subtasks; in the token search bar, the advanced editor and saved filters. While creating a task you can add linked items and pick existing tasks as subtasks, and the bulk action bar has "Set parent" and "Add link".
  • ImprovedIn the board list every column can be resized, No and Labels included, and the No column sorts numerically (REQ-9 before REQ-10). In filter results columns sort across all results, and results export as Excel, CSV or PDF (up to 2000 rows). Issue types are managed under Board Settings > Custom Fields: name, icon, color, order and new types; system types with behavior attached cannot be deleted. A board key can contain digits and dashes, like SYS-REQ or A400, and dashed task keys in GitLab commit and branch names are recognized. "What’s new" shows the notes of every release in between when an installation skips several releases.
  • FixedImporting from Excel (.xlsx): choosing a file did nothing; it is now read, and an unreadable file shows a warning. In a baseline review the screen got squeezed as comments were added and could not be scrolled. The label of the "has any link" option in search was corrected.

v1.74.1

covers v1.74.0 - v1.74.1

Moors: a requirements management board with traceability links, coverage, a matrix, suspect links and baselines

5 new · 1 improved

  • NewMoors, a new board type: requirements keep a permanent ID (e.g. REQ-42) and work with what the task screen offers: workflow and an approval lock, hierarchy, fields, history and Excel/CSV exchange; the approval chain is for baselines. The board opens ready to use: Draft, In Review, Approved, Implemented, Verified and Rejected statuses (an approved requirement is locked for editing), Stakeholder Need, System, Subsystem, Software and Interface Requirement levels, and Source, Verification Method and Criticality attributes. The names come in the language of whoever creates the board and can be changed in Board Settings. List is the main view; Kanban and Releases are there too, and there are no sprints. An existing board can be switched to Moors under Board Settings > General.
  • NewTraceability links: four new link types connect tasks and requirements: derives, satisfies, verifies, refines. Each can be picked in either direction; a test task "verifies" a requirement and the requirement shows it as "verified by". When adding a link, the chosen direction is spelled out in a sentence, and the linked items list shows the task’s short code before its title.
  • NewCoverage and matrix: a Moors board has two new tabs. Coverage gives the share of requirements that have a source, are implemented and are verified; requirements without a source, unimplemented, unverified or with a suspect link are filtered in one click. Matrix shows requirements in rows, the items of a chosen board (e.g. a test board) in columns and the link type in each cell; "Unlinked items" lists tests that are linked to no requirement. A "Traceability coverage" widget can be added to dashboards.
  • NewSuspect links: when a requirement’s title, description or attributes change, the traceability links touching it (derives, satisfies, verifies, refines) are marked "suspect"; subtask and parent/child links are not. A badge appears on both ends of the link, and its hint shows which requirement changed and which fields; someone with permission reviews the link and closes it with "Reviewed", which is written to the task history. Which fields are tracked is chosen under Board Settings > General.
  • NewBaselines: the state of the requirements and their traceability links at a given moment (e.g. "SRR approval") is stored unchangeably and compared with today or with another baseline: added, removed and changed requirements, which field changed from what to what, and link changes on one screen. A baseline can be sent through an approval chain; a baseline that is pending or approved cannot be deleted. Its contents and the comparison download as Excel or CSV. Creating and deleting one needs the board configuration permission, and both are written to the audit log.
  • ImprovedClicking a task on another board from the coverage, the matrix, a link or a subtask opens it in a side panel on the same screen, with its own board’s fields and rules. The new board dialog was redesigned: board type cards on the left, a live preview on the right that follows the chosen type. The "What’s new" dialog shows each change on its own line.

v1.73.0

Large boards open much faster, and the last opened task stays highlighted in every view

3 improved

  • ImprovedOpening a board no longer loads every task at once. On Kanban and sprint boards each column opens with its first 30 cards and the rest arrives as you scroll; the column count and WIP limit always reflect the whole column. Backlog sections load 50 rows at a time, the calendar loads only the visible month and the timeline loads the chosen date range (by default 30 days back to 90 days ahead). Planning, sprint close and retro fetch only the tasks of that sprint.
  • ImprovedThe search, label and custom field filters in the top bar now also apply to List, the calendar and the timeline. On boards that roll subtask points up, Story Points are calculated including subtasks that are not loaded on screen.
  • ImprovedAfter the task screen closes, the last opened task stays highlighted in List, Backlog, saved filter results and group boards, just as on Kanban. On a group board a double click on a column header collapses the column, and columns now reach the bottom of the screen.

v1.72.1

covers v1.72.0 - v1.72.1

Group boards: tasks from several boards on one screen

1 new · 2 improved

  • NewGroup board, a new board type: it shows the tasks of several boards on one screen with the group board’s own statuses, while the tasks stay on their own boards. Source board statuses map to the columns automatically (same name first, otherwise same category); the mapping can be changed by hand under Board Settings > Source boards, and tasks with no match sit in an "Unmatched" column. Moving a card to another column moves it to the matching status on its own board; if several statuses fit, you are asked which one.
  • ImprovedOn a group board a click on a card opens the task in a side panel on the same screen; "New task" first asks for the board and opens the task with that board’s fields, templates and rules. Kanban columns open with their first cards and fill as you scroll, and the list view is paged (25, 50 or 100 rows); tasks of boards you cannot access are not shown.
  • ImprovedIn List view the counts on status headers and the export (Excel, CSV, PDF) come from the server, and the export writes every row that matches the filter. The Viewer role now sees linked items on tasks and documents; the add and remove link buttons are hidden from anyone without the permission.

v1.71.0

Link map widget, parent/child and cause links, due date tracking that stops in a status

3 new · 1 improved

  • NewLink map: this dashboard widget starts from the tasks of a chosen root board and draws subtasks and cross-board links as a live hierarchy; work on other boards appears in the same tree in its board’s colour. Branches expand and collapse, the map can be dragged and zoomed, hovering a task highlights its chain, a searched task is centred, link types and completed tasks can be hidden, and the map opens full screen. Tasks on boards you cannot access appear only as a count.
  • NewNew link types: "parent of / child of" and "causes / is caused by". The parent/child link works across boards; a task can have only one parent through a link, and cycles are refused.
  • NewDue date tracking can stop in a status: with "Due date tracking stops in this status" switched on for a workflow status, a task in that status is not shown in red and no overdue notification goes out even after its due date (e.g. Done in a Done → Released flow). Metrics are not affected. Overdue due dates are now red in List view too.
  • ImprovedThe application log on the Health tab shows the user behind each entry. If a board only lets new tasks start in certain statuses, the column "+" and quick add appear only on those columns. The group edit screen is wider: every user is listed, sortable by name and filterable by selected/unselected and by title, and all visible people can be selected in one click. Required priority and Story Point fields show a *.

v1.70.0

Entry kinds in the log, email retries, date rules and a resizable sidebar

2 new · 2 improved · 1 fixed

  • NewEvery entry in the application log on the Health tab now shows its kind: possible bug, external service, configuration or user input. It can be filtered by kind, and clicking an entry explains the reason and what can be done; anything unrecognised counts as a possible bug. Requests GitLab refuses on a business rule (branch missing, MR already open) are now logged as warnings rather than errors.
  • NewDate rules: due date, start date and custom date fields can carry a "Cannot be before today" or "Cannot be after today" rule (Board Settings > Task Screen and the custom field settings). The rule applies only when a value is entered or changed; existing dates are not affected.
  • ImprovedWhen the mail server refuses temporarily or the connection drops, sending is retried once; previously that email was lost. The Settings > Board Codes list can be reordered by dragging and viewed by code, name, type or state; "Save this order" turns a view into the stored order, and codes appear in that order when creating a board.
  • ImprovedThe edge of the sidebar and of the page tree on a docs board can be dragged wider; a double click restores the default. On the task screen, priority can be cleared by picking "No priority". The board name at the top of the task screen leads to the board’s List view. In the GitLab project by field mapping, leaving the project untouched and clearing the task’s project are now separate choices for an option.
  • FixedOn boards where the template requirement was switched on later, tasks created before that can have their description edited without a template, and text typed into a refused save is no longer lost. The board order in the sidebar no longer breaks with several tabs open or while the search filter is in use. The notification for a document moved to another board now opens its new board.

v1.69.0

GitLab project by field, base branch picker, webhook warning and a date filter in the log

1 new · 4 improved

  • NewGitLab project by field: under Board Settings > Integrations > GitLab, the options of a select field can be mapped to GitLab projects (e.g. Platform = Mobile → the mobile repository). When a task is created or the field changes, the task’s GitLab project is filled in accordingly; a project picked by hand in the same edit wins. Automatically created issues also open in the task’s project.
  • ImprovedOn boards with several projects the default project can be removed; new tasks then start with no GitLab project and whoever creates the branch picks it. When creating a branch, the base branch can be picked from the branches of the task’s project; the default branch is preselected and typing a name is still allowed.
  • ImprovedWebhook warning: the GitLab settings show, next to each project, when its last webhook event arrived or that none has arrived; creating a branch in a project without a webhook warns that commits and MRs will not show up in MyWay.
  • ImprovedWhen someone who has not connected a GitLab account comments on a task linked to GitLab, they are told beforehand that the comment will appear in GitLab under the name of the user who set up the integration; if they send it, the author’s name is prefixed to the comment in GitLab.
  • ImprovedBoards in the sidebar and on the Boards page can be opened in a new tab with a right click; clicking the board name in the top bar switches to List view. The application log on the Health tab can be filtered by start and end date and time; "Export filtered" downloads only the filtered entries.

v1.68.0

Document history and HTML attachments

1 new · 1 improved

  • NewDocument history: like on tasks, the bottom of the document screen has "Comments" and "History" tabs. History shows who created the document, who changed the title, content and tags and when, version restores, publications, document code changes, moves, and the review and approval steps. Anyone who can see the document can see it; records from before this release are included.
  • ImprovedHTML files can be uploaded as document and task attachments; for safety they are always served as a download and never opened in the browser.

v1.67.2

covers v1.67.0 - v1.67.2

One-command upgrades, a final approval deadline, "my comments are done" and tighter permissions

2 heads-up · 3 new · 2 improved · 1 security

  • NewOne-command upgrades: ./scripts/update.sh downloads the latest package with your license key, compares it with the installed version, takes a backup first, applies the upgrade and waits until the app is up on the new version. If you are already up to date it changes nothing. The script ships with this package; the move to this release itself is done once the way the installation guide describes.
  • Heads-upCommenting on documents now requires the "Comment on documents" permission; edit rights alone no longer allow it. Previously, anyone who could edit could comment even if the permission was removed from their role. If editors in your custom roles should also comment, tick this permission.
  • Heads-upAdding a task to a sprint or removing it (from the task screen, by dragging in the backlog, through bulk actions or the /sprint command) now requires the "Manage sprints (create, start, complete, delete)" permission. If roles that do this lack the permission, grant it after upgrading.
  • New"My comments are done" in reviews: during comment collection each participant can mark that they have finished commenting and undo it; the mark shows in the participant list and is cleared when a new round starts.
  • NewDeadline for final approval: when starting or editing a review, an optional deadline (in days) can be set along with what happens when it passes: treat non-responders as approved, or stop waiting for them. The clock starts with the final approval stage; when it runs out the review completes on its own. The publish rule can hold a default for new reviews.
  • ImprovedDuring a review and while an approved document awaits publishing, its labels are locked too. SVG files can be uploaded as document and task attachments and are always served as a download. Documents created from a template open in the rich editor; reloading the page returns to the document you were on, and document URLs can be shared.
  • ImprovedThe link picker shows which board each document result belongs to. After @ in comments and quick actions, people can be found by full name and with Turkish letters. The add member or group dialog stays open for adding several in a row; the review screen no longer overflows on mobile.
  • SecurityPermission checks were tightened.

v1.66.0

Quick actions in the description and per-person roles inside groups

2 new · 1 improved · 1 fixed

  • NewQuick actions in the description: lines such as /label ~frontend, /type ~Bug, /story-point 8, /assignee @ali-veli or /status ~"In Progress" at the start of a line in the task description set fields. Title, labels, issue type, Story Points, priority, assignee, status, dates, fix version, sprint and custom fields are supported. Before saving, a preview shows what each line will change; if any line is invalid, none are applied. Commands follow the same permissions and transition rules as normal editing and appear in the task history as "used quick actions".
  • NewPer-person role inside a group: for a group added to a board, a person in that group can be given a separate role that replaces the group’s role, widening or narrowing their access. Expanding the group row under Board Settings > Members > Groups shows a role picker next to each person.
  • ImprovedOn Kanban, closing a task’s details keeps the last opened card highlighted and scrolls it into view if needed. Dashboards owned by others show their owner’s name in the list. Application log lines now include the path of the screen that made the request, and unexpected database errors include their error code.
  • FixedGitLab: a webhook no longer fails when a commit or branch name mentions a task key that is not on the board. Importing issues from GitLab now also works on boards with a description template or required field rules turned on. Trying to create a branch or MR in a project you cannot access now explains why in your own language.

v1.65.0

Pre-publish order, moving documents in the tree, richer task history and user list filters

2 new · 2 improved · 2 fixed

  • NewPre-publish order: when the publish rule requires both a review and an approval, the order between them can be chosen: parallel (the previous behaviour), review first then approval, or approval first then review. With approval first, the document can be edited during the review’s revision round.
  • NewMove under another document: from its row in the document tree or from the page menu, a document can be moved, with its sub-documents, under another document in the same space or to the top level. When copying or moving to another space, the target parent document can be chosen.
  • ImprovedRicher task history: adding and removing links (on the tasks at both ends), adding and deleting attachments, adding, detaching and deleting sub-tasks, and changes to the issue type, fix version and affected version now appear in the history.
  • ImprovedThe workspace user list is sorted alphabetically by name, with filters for group, role and activity (online now, active in the last 7 days, not seen for 30+ days, never signed in) and sorting by last seen; role, activity and sorting are admin-only.
  • FixedBulk selection: in list view "select all" selects only the visible page and a selection can hold at most 100 tasks, with a warning at the limit. Previously the whole filtered list was selected and bulk delete failed.
  • FixedIn a document moved to another space, people who are not members of the new space show by name instead of by ID in the approval and permission panels. The Health tab lists every online user.

v1.64.2

covers v1.63.1 - v1.64.2

Publish rule, review submitter and Word comments, moving documents and Markdown

2 heads-up · 6 new · 4 improved · 1 fixed · 1 security

  • Heads-upPublish rule: in docs spaces a document is now published, by default, only through a completed review. The upgrade switches the rule on in existing spaces too. Spaces that publish through approvals only should untick the review box and tick the approval box under Space Settings > General > Publish rule; spaces that want to keep publishing directly can untick both.
  • Heads-upA published document can no longer be unpublished; the publication record does not change. If it needs changes, edit it and publish the new version.
  • NewReview submitter: the person running the process is chosen when the review is opened (by default whoever opens it). An open review’s participants, required approvers, due date, description and submitter can be changed; a participant who has already decided cannot be removed. The submitter can also add findings during disposition.
  • NewDue time and automatic close: a review’s due date can include a time, and comment collection can close by itself when the due date arrives.
  • NewImporting Word comments: margin comments in a Word document are previewed with their marked text and author and turned into findings in bulk. The "which part of the document" field suggests the section headings of the page or of a chosen Word attachment.
  • NewCopy / move to another space: a page, with its subpages, can be copied or moved to another docs space, embedded diagrams included. It is a separate permission ("Copy / move to another document space"), held by default only by the Admin role.
  • NewCodes for existing documents: a document without a code can take the next code from a document series or have one entered by hand, and an existing code can be changed.
  • NewMarkdown: documents can be imported from .md files, and .md files can be uploaded as attachments.
  • ImprovedDashboards: a "Current user" option on the Calendar card, and sprint selection on the Workload Distribution card (all tasks, the active sprint or a specific sprint). The Saved Filter card offers custom field columns for filters that look at several boards too.
  • ImprovedText in reviews, approvals and page comments can be selected and copied, and the document page makes better use of wide screens. In the board search bar, the value list of person fields is searchable.
  • ImprovedWhen copying a board without its members, the person-specific rules that would be dropped are shown in advance.
  • ImprovedApplication log: entry details show the person’s name next to user IDs, and database errors show the error code, the constraint involved and masked query values. The support bundle does not include them.
  • FixedGitLab event content older than 90 days is no longer deleted; commit and merge request history on tasks is permanent. The nightly job and GitLab issue linking failed to write audit records; they are now written with "System" as the actor. The "Current user" filter on the board view returned nothing, now fixed.
  • SecuritySecurity updates to dependencies.

v1.63.0

Application log, reference codes and a support bundle

1 heads-up · 3 new · 1 improved

  • NewReference code: an unexpected error now ends with a reference code. An administrator finds the matching record with it, and quoting the code is enough for a support request.
  • NewApplication log: the Settings > Health screen lists warning and error records, filtered by level and searchable by message or reference code. Records are kept for 30 days and survive upgrades.
  • NewSupport bundle: a diagnostics file for support, one click on the Health screen or ./scripts/support-bundle.sh on an installation. It contains no passwords, keys or personal names.
  • ImprovedAccess log and log settings: the reverse proxy records every request, with keys in one-time links masked. Container logs rotate with a size limit so they do not fill the disk, and LOG_LEVEL sets the level of detail. To send logs to your own SIEM, use docker-compose.override.yml; the installer and backup scripts keep that file across upgrades.
  • Heads-upThis release includes a database change; the installer offers a backup before upgrading (yes by default) and applies the change on its own.

v1.62.0

Published versions, the Status aging card, relative date and list filters, an expanded Health screen

1 heads-up · 5 new · 1 improved · 1 fixed

  • NewPublished versions: every published version of a document appears in its own list. Click an older one to open it read-only with its content and the attachments it had at the time, and download it as PDF or Word. An attachment used in a published version is kept even if it is deleted later. Past publications were restored from the records; very old ones with no record are not listed.
  • NewStatus aging card: shows how long tasks have been waiting in their current status, with a target per status and the tasks over it.
  • NewRelative date filter: filters such as "Last 7 days", "This week", "Next 1 month" or "More than 3 days ago"; saved filters work against the current date every day.
  • NewColumn filters in the list view: reporter, watchers, versions, comment count and every date column can be filtered from the header; custom date and number fields filter by range, and tasks without a sprint can be selected.
  • NewThe Health screen grew (Settings, superadmin only): totals for tasks, boards, users, pages, comments and attachments; when each scheduled job runs, its last and next run and any delay. On installations the result of the nightly backup shows here too.
  • ImprovedBulk version assignment uses the same picker as the task screen, with add, remove or replace. Board cards fit on one row with shortened durations, and a task with a branch or commit shows a branch marker.
  • FixedFixed: the document version history showed the previous version instead of the published one; bulk version assignment wiped the tasks’ existing versions; the "Overdue" ready filter could lag a day behind after midnight; issue type could not be picked in the advanced filter and checkbox field options came up empty; the status icon menu on the planning screen did not close on an outside click.
  • Heads-upThis release includes a database change; the installer offers a backup before upgrading (yes by default) and applies the change on its own.

v1.61.1

covers v1.61.0 - v1.61.1

New dashboard cards: calendar, sprint goal and cycle time; subtask rules; one-command backup

1 heads-up · 5 new · 2 improved · 1 fixed

  • NewCalendar card: tasks in month, week or day view, across several boards. Filter by status, person and label; use the built-in dates or date-type custom fields for start and end. An "Upcoming" list sits beside it, with total, in progress, planned and done counts below.
  • NewSprint goal card: the sprint goal, completion by tasks and story points, working days left according to the board calendar, scope added or removed after the start, work carried over from the previous sprint and a status at a glance (on track, at risk, late, done).
  • NewCycle time card: average, median, shortest and longest time, tasks over target, change against the previous period, a trend chart (by day, week, month or sprint), time spent per status and the slowest tasks. The average cycle time in the board header now uses the same calculation, so its value may shift slightly.
  • NewSubtask rules (Board Settings): completing a parent task with open subtasks now shows a warning, and can be blocked or switched off. Choose how story points count: each task its own points, the parent only, or the sum of its subtasks. When the last subtask is done, completing the parent is suggested. Metrics on existing boards stay the same.
  • NewOne-command backup and restore: the backup script takes the database, uploaded files and settings, verifies them and keeps the last 7 backups; the restore script verifies the backup and asks for confirmation first. The installer offers a backup before upgrading (the upgrade does not run if the backup fails) and offers to set up a daily automatic backup. Upgrades no longer show the "first user to sign up becomes admin" notice.
  • ImprovedReview comments: the table filters now work in the list view too, so you can narrow to one person's comments and resolve them on the same screen. Resolution progress and quick filters were added.
  • ImprovedReminder notifications now carry a "Reminder" label instead of a person's name, so a system notification no longer reads as if someone sent it.
  • FixedFixed searching the member list, the date of a task dragged onto a custom date-time field, and the planning page when opened from a direct link.
  • Heads-upThis release includes a database change, which the installer applies on its own; it offers to take a backup before upgrading.

v1.60.2

covers v1.60.0 - v1.60.2

Approval lock for documents, a table view for reviews, custom date fields in planning

2 heads-up · 1 new · 3 improved · 1 fixed

  • Heads-upApproved documents are locked until published: once approval is complete, the content, title, attachments and version restore are locked until the document is formally published. An approval given by mistake can be withdrawn. The lock applies only to approvals given after the upgrade; documents approved or published earlier are not affected.
  • ImprovedApprove and reject buttons are shown only to the approver of that step. In the final approval of a review, "Approve" is open only to required approvers; optional participants can add comments with "I Have Comments".
  • ImprovedReviews: the reviewer picker is alphabetical and searchable; comments can also be viewed as a filterable table; once the due date passes, participants who have not responded get a single reminder.
  • Newdraw.io files can be uploaded as attachments.
  • ImprovedThe planning screen uses the custom start and end date fields the board selected, and dragging updates them. Workflow transitions can be reordered by dragging. Role permissions are saved with a single "Save" button. Dashboard card titles show the selected board name.
  • FixedFixed role columns changing order after saving several roles, the GitLab "Issue on new task" option not being saved, and version restore being possible while a review was in progress.
  • Heads-upThis release includes a database change, which the installer applies on its own. Taking a backup before upgrading is recommended.

v1.59.0

Security hardening: files and reviews open only to people who can see them

2 heads-up · 1 fixed · 2 security

  • Heads-upFile access was tightened: files and images in tasks, pages and comments now open only for people who can see that task, page or board. Behaviour change: file links from a board you are not a member of, or from a page you cannot see, no longer open, and users in the "Viewer" role can no longer paste and upload images. Tabs left open during the upgrade may need a refresh before pasting images works again.
  • SecurityPermission checks on document reviews were tightened: reviews of restricted pages and their notifications are open only to people who can see the page, and someone who cannot see it can no longer be added as a participant.
  • SecurityThe document editor, email sending and content sanitising components were moved to versions that carry security fixes. Existing documents open unchanged.
  • FixedA diagram copied from one page and pasted into another turned into a flat image; it now stays a diagram and can be edited.
  • Heads-upThis release includes a database change, which the installer applies on its own. Back up the database and the uploaded files before upgrading.

v1.58.1

covers v1.58.0 - v1.58.1

Board permissions are now decided by the board role, plus customer feedback on document management

1 heads-up · 4 improved · 3 fixed · 1 security

  • Heads-upBoard permissions are now decided by the board role. A workspace admin works with the permissions of their role on each board they belong to: an admin added to a board as "Viewer" can no longer edit tasks there. The super admin exception stays, so boards with no membership can still be managed. After upgrading, we recommend reviewing the board roles of your admins; until now they worked with full rights whatever their role was.
  • ImprovedCreating tasks and document pages is now tied to permissions. A user without the create-task permission no longer sees the "+" button on board columns, the quick-add row, task import or the "New subtask" button. Opening a new page (blank, from a template or from Word) requires the edit-pages permission; adding a page under another page or duplicating one requires edit rights on that page.
  • ImprovedAttaching a file to a published document now opens a new draft version (for example 1.0 → 1.1) and requires publishing again, so the content of a published version never changes silently. Attachments cannot be added or removed while a review is open.
  • ImprovedThe final approval step of a review is clearer: choosing "I Have Comments" lets you add as many comments as you need and the process only moves on when you submit; that option cannot be submitted without a comment; and approval cannot be given while any comment is still without a decision. A review completed by approval now records the approved document version correctly.
  • ImprovedAn edit attempt without permission now says "You don’t have permission to edit this page" instead of "Page not found", and a user without edit rights sees the page read-only. On a docs board the role matrix and the add-member screen show the same role names (Editor, Commenter), and no Turkish role names appear in the English interface.
  • FixedPages with large diagrams could not be saved and failed with a "character limit" error; the limit was raised and a clear message appears if it is exceeded. The same root cause made attachments over 10 MB fail, which is fixed too.
  • FixedWord import: images the browser cannot display (EMF/WMF) no longer stop the import; they are skipped and their count is reported, and a failed import no longer leaves a half-created empty page behind. Import, broken by a component upgraded in an earlier security update, works again in 1.58.1.
  • FixedMembers added to a board only through a group could not load the board’s data; fixed.
  • SecurityPermission checks were tightened on several screens that deal with restricted document pages; restricted pages you cannot open no longer appear in lists or search.

v1.57.2

covers v1.57.0 - v1.57.2

Sprint capacity plan: team, per-person capacity and leave are saved, and work is planned by dragging on the calendar

4 new · 2 improved · 2 fixed

  • NewSprint capacity plan. Who works in the sprint, each person’s daily capacity and their days off are now saved; before, these only lived while the capacity window was open and were gone once it closed. The team is picked under Sprint > Capacity, capacity can be set per person, and days off are marked on the sprint calendar. Leave that falls on a weekend or a public holiday is not deducted twice.
  • NewThe planning calendar shows capacity: rows come from the sprint team, days off are hatched on each person’s own row, and cards at the top show capacity lost, normalized capacity and remaining work. When more work is planned than the team can carry, remaining work is highlighted in red.
  • NewPlanning by dragging on the calendar: dragging a task’s bar sideways shifts its dates, dropping it on another person’s row reassigns it. Changing dates and reassigning are separate permissions; for a user without them the bar does not move. Until the change is saved the task is dimmed with a busy cursor.
  • NewThe Workload Distribution card can show capacity utilization too, with capacity, remaining work and the number of people over capacity at the top. Team members with nothing assigned are included in the chart, so idle capacity stays visible.
  • ImprovedThe board top bar was reorganized. As view tabs grew, buttons that did not fit were cut off; the everyday tabs stay in place, rarely used views (such as Calendar, Timeline and Planning) moved into a "More" menu, and the view you are in is shown separately when it lives in that menu. Tab icons are now distinct from each other as well.
  • ImprovedThe backlog uses the same column definitions as the list view: it has column headers and a column picker, and custom fields can be added as columns; the backlog’s column choice is stored separately. The column picker and "New sprint" moved to the top of the view, since they affect every section. The sprint calendar got a visual refresh as well: summary cards, two-line day headers, a clearly marked public holiday column, task status icons and a legend at the bottom.
  • FixedWith no versions defined on the board, the "Fix version" and "Affects version" fields were hidden even when marked required, so no task could be created at all. A required field is now shown and says that a version has to be defined first.
  • FixedFound in staging: the "More" menu, the info message in the version picker and the advanced filter button were clipped at the edge of their container; the permission picker did not close on an outside click; the Workload card gave the wrong advice with no active sprint or on a Kanban board that does not use sprints; a team member with no assigned work appeared without a name in the chart; and the donut chart, selectable but never applied for the capacity measure, was disabled.

v1.56.0

A Workload Distribution card and a per-person sprint calendar

2 new · 1 improved · 2 fixed

  • NewWorkload Distribution dashboard card: how the board’s work is spread across people can be shown by task count or by Story Points. Two people with the same number of tasks can carry very different loads, and a count alone did not show it. The card is drawn as a donut or horizontal bars, and clicking a slice opens the matching tasks as a filtered list. The top row shows total tasks, total points, unassigned work and the number of tasks without an estimate; without that last number the points chart would understate the load. The existing "Assignee Distribution" card stays as it is.
  • NewPer-person sprint calendar: boards that use sprints get a "Planning" tab, with the team down the side and the sprint days across. Team members with no assigned work still get a row, and unassigned tasks are gathered in a row of their own. Weekends are hidden by default and can be shown; public holidays come from the board’s work calendar. An optional "rolling sprint" can be picked to show work carried over from the previous sprint dimmed and in italics, and you can choose which critical statuses to flag on the calendar.
  • FixedOn a board with a required fixed field (for example "Affects version"), adding a subtask from the task detail was impossible because the inline box only asked for a title. Such a board now opens the full creation screen. The required-field warning also names the field, in the interface language.
  • ImprovedNew task screen: "Fix version" is no longer asked up front (that is not known when work is opened). The priority, label and sprint lists open when you click anywhere in the field. Esc closes an open list without closing the task screen; a second Esc closes the screen, and the same holds for every nested dialog. Version lists are sorted newest first again and get a search box when they grow long.
  • FixedStory Point values could not be read in certain setups and were counted as zero, so the capacity report showed everyone at 0 points. The upload size limit (MAX_UPLOAD_MB), fixed for self-hosted installs in 1.55.6, now applies to the other environments as well.

v1.55.6

An installation package fix: email settings, scheduled jobs and the port choice now reach the package correctly

1 heads-up · 1 improved · 3 fixed

  • FixedThe setup files inside the self-hosted package did not belong to the version being shipped. The package took the product’s built images from the right version but picked up the files beside them (the Docker Compose definition, the installer, the reverse proxy configuration, the sample settings file and the scheduled job scripts) from an older copy. Nothing changed in the product code; the package is the only thing affected.
  • FixedWhat that caused: the MAIL_* values written into .env.onprem never reached the app, so invite emails and password reset stayed silently off; the scheduled job scripts were missing from the package, so due-date notifications, review reminders and event cleanup could not be installed; non-standard ports and the internal-network TLS options were ignored; and a setting the GitLab connection needs was not passed through.
  • Heads-upUpgrading is recommended and the usual procedure is enough: unpack the new package over your existing directory and run ./scripts/install.sh. The setup files are repaired and your values in .env.onprem are kept. If you use email, after the upgrade you should see "mailConfigured": true in the output of https://your-address/api/health.
  • FixedThe upload size limit could not be configured: MAX_UPLOAD_MB was documented but never passed to the app in any environment, leaving the limit fixed at 25 MB. It can be set now.
  • ImprovedThe health endpoint now reports email status as well: mailConfigured was added to the /api/health response (cronConfigured for the scheduled jobs was already there), so a silent loss like this cannot go unnoticed again. The package builder also got a version anchor: if the version being packaged and the source of the setup files do not match, no package is produced.

v1.55.5

covers v1.55.0 - v1.55.5

A task now carries its GitLab project as a field, filters are saved from the advanced panel, and statuses can carry a description

1 heads-up · 5 new · 2 improved · 11 fixed

  • NewGitLab Project field: when a board is connected to several projects, the task screen states which one the task belongs to. Once a connection exists the field appears in Custom Fields like any other: it can be put in a field group and shows up in filters and list columns. When it is filled, the branch and merge request dialogs stop asking for the project. On a single-project board it is preselected, and on a board with no connection it does not appear at all.
  • NewSaving a filter from the advanced filter panel: the board’s saved filters and a "Save filter" button now sit at the top of the panel. Clicking a filter loads its criteria onto the screen, where they can be edited and saved again. If you already have a filter by that name, a second copy is not created silently: you are asked whether to overwrite it or save under another name. A saved filter in the sidebar opens the board in list view, and the name of the applied filter is shown in the top bar.
  • NewStatus descriptions: a status definition can carry an optional description saying when work moves into it and what the exit condition is. It is read from the status picker, from an info icon in the column header and from the task’s status badge, and it carries over when a board is copied. What similarly named statuses (Review / Test / QA) are actually for stops being tribal knowledge.
  • New"Blocked by" in links: added to the relation types. It is not a separate record but the reverse direction of a "blocks" link - if A blocks B, then B shows A as "blocked by", and deleting the link from either end removes both. Blocking cycles are now rejected: once the ring closes, no work can start.
  • NewThe description can be required to follow a task template: with the switch under Board Settings > General turned on, a new task must pick a template and the template’s required sections cannot be left empty. The check is structural: mentioning a heading in prose is not enough, the body under the section has to be filled. Missing sections are reported one by one, and existing tasks are unaffected.
  • ImprovedA branch opened from MyWay is named `issue/{task key}` by default and a description can be appended. The total length is capped at 50 characters, with a counter and a warning on screen. Turkish letters and unsupported characters are converted to a valid equivalent as you type rather than dropped.
  • ImprovedFixed fields (GitLab Project, Priority, Story Point) can be put in a field group as well, so the group’s "who fills this section" rule applies to them too. The rule only narrows: the permission needed to fill the field still applies.
  • FixedOn a board connected to GitLab, a task’s assignee and labels emptied themselves. The sync was missing a direction: MyWay never sent the assignee to GitLab, so the GitLab issue always looked unassigned and the event raised by an edit wrote that empty state back onto the task. The assignee is now sent to GitLab as well, and an incoming event only writes the fields GitLab reports as changed.
  • Heads-upLabel ids that were written onto tasks before this fix and do not belong to that board stay where they are and show up as raw ids in the list. Re-picking the labels once on the affected tasks is enough.
  • FixedLabel sync worked sometimes, did nothing at other times and occasionally wiped every label: an incoming sync looked label names up on the board the event arrived from, but since one GitLab project can be connected to several boards, the task may live on another board. The lookup now happens on the task’s own board, and outgoing labels are always sent as a complete list.
  • FixedAn assignment made in MyWay sometimes never reached GitLab: when the user-matching lookup came back empty once, that result was cached for a minute and every attempt within it failed. Only successful matches are cached now, and the lookup tries the exact username first. The assignee was also not sent when the issue was created.
  • FixedA new task’s assignee was cleared half a second later: the workflow rule "when it lands in this status, assign it to this person" ran, and then the event from creating the GitLab issue emptied the assignee again.
  • FixedLabels, statuses and sprints appeared as raw ids in a task’s history, and select fields showed their value rather than their name in list columns and exports (the GitLab Project column showing "2" or "5" instead of a project name). Id-to-name translation is now handled in one place.
  • FixedGitLab sync left no trace in the audit log. Creating the task in GitLab and applying an incoming GitLab change to a task are both recorded now, including which fields an incoming change updated.
  • FixedA saved filter picked from the advanced panel or the sidebar was not applied: the criteria were written into the address incorrectly and dropped silently. And once a filter was cleared, it came back on a page reload or a tab change.
  • FixedA field group’s status gate blocked everyone while creating a task: a section with an "editable only in these statuses" rule looked locked on the new task screen, admins included. The rule now sees which status the task will be created in. The "you cannot fill this section" warning also names the fields that are blocking.
  • FixedLabel names were unreadable in the light theme: the contrast between text and background was too low. The text colour is now derived from the background, and the colour you picked is kept as is.
  • FixedAuto-assignment from a person field did nothing: the workflow rule "when it moves into this status, assign it to the person in this field" silently did nothing when the field was set to multi-select. When an assignment cannot be made, the reason is written to the audit log.
  • FixedOther fixes: finished work stayed in the "My tasks" card; clicking a linked task on another board opened nothing; an auto-assignment made by a workflow only appeared after a reload; the "tasks in this status cannot be edited" mark was not applied when creating a status; the GitLab Project column is skipped on import and reported in the log; a template’s GitLab project carries over when a board is copied; the comment box can be dragged taller and remembers its height.

v1.54.2

covers v1.54.0 - v1.54.2

Start statuses for new tasks, a dedicated Story Point field and a thorough pass over GitLab automation

2 heads-up · 2 new · 4 fixed

  • NewStart statuses for new tasks: workflow settings define which statuses a new task may start in, with one marked as default. The task form lists only the allowed ones. With none selected, behaviour stays as it is today.
  • NewStory Point field: the built-in Estimation field is now Story Point. Sprint capacity, velocity and burndown already read it; its name made it look like a time estimate. Priority and Story Point are configured under Task Screen > Fixed fields and can be edited there.
  • Heads-upOn boards that used the "hours" unit this field now means points; teams tracking durations can add their own number field under Custom Fields. Existing values are not deleted.
  • Heads-upThe quick-add box under columns is now a board setting and off by default (including on existing boards). Enable it under Board Settings > General; on boards with required fields or a GitLab project choice it opens the full form.
  • FixedGitLab event automation silently did nothing: creating a branch or MR from MyWay did not trigger status automation, strict transition rules rejected it, and the reason appeared nowhere. It now runs immediately and writes the reason to the audit log when it cannot apply.
  • FixedWhen a GitLab project was linked to several boards, events were processed on only one of them. A single webhook on the project now serves every linked board, and each event is applied on the board that owns the task.
  • FixedThe task screen did not reflect GitLab changes without a reload: the new status now appears immediately after creating an MR, and returning to the tab refreshes the task, branch and MR lists. Branches deleted in GitLab also drop off the list.
  • FixedBoard copy no longer misses settings: status auto-assign rule, edit lock, transition enforcement, transition person conditions, start statuses, task screen layout and fixed field settings are copied, and a field group's role link and status gate are remapped to the new board.

v1.53.0

covers v1.51.0 - v1.53.0

GitLab actions under your own name: per-user GitLab account, full sync across several projects and more flexible rules

2 new · 2 improved · 3 fixed

  • NewPer-user GitLab account: every user connects their own GitLab account from Settings > Connected accounts (same OAuth app, no extra setup). Branches and MRs are created under your account; if it is not connected the action stops with a "connect your account" link. Issue creation, status/label sync and comment mirroring run as you when connected, otherwise via the board's shared connection. Credentials are stored encrypted and never shown in the UI.
  • NewIssue creation mode on new tasks: when a board is linked to several projects you can choose "Ask" (project picker on the task form), "Don't ask, open in the default project" or "Don't ask, open in all projects". Existing boards keep their behaviour.
  • ImprovedField-group status gate accepts several statuses: the section is editable while the task is in any of them. Existing settings migrate without loss.
  • ImprovedMultiple roles in transition rules: "Required role" is now multi-select (search, select all, clear); having any one of the roles is enough. Deleting a role used by a rule shows the affected transitions and, once confirmed, removes it from them too.
  • FixedSync was incomplete with several projects: comments now go to every linked issue, labels by name; changes and comments on any linked GitLab issue reach the task.
  • FixedColumn sort menu worked backwards: three explicit options (Newest first / Oldest first / Manual) with the active one marked, instead of one cycling button.
  • FixedStatus colour could not be picked from the palette: the custom colour picker and HEX field now always apply.

v1.50.2

Hotfix: tasks would not open on some boards

1 fixed

  • FixedOn boards without a GitLab connection, clicking a task crashed the screen with "something went wrong". The project-set code introduced in 1.50.0 assumed the board's project list always existed. Fixed; the task screen opens on every board.

v1.50.1

covers v1.50.0 - v1.50.1

GitLab: multiple repos from different groups on one board; changing the short code no longer renames tasks

1 heads-up · 3 new · 1 improved · 1 fixed

  • NewA board now connects to a set of projects you choose instead of a single repo or group; the projects can come from different GitLab groups. "Add projects" searches every project you can access and adds several at once, "Add whole group" takes all projects of a group. Existing connections migrate on their own; single-repo boards keep working. When creating a task you tick the projects the issue should be opened in (the default comes pre-ticked); merge requests open in the project the branch was created in.
  • Heads-upChanging a board's short code or digit count no longer renames existing tasks: YB-001 stays as it is, only new tasks get the new code and numbering continues where it left off (if the last task is 80, the next is YBS-081). Previously every task was renamed and old numbers in e-mails and commit messages went stale.
  • NewTyping "MYW-129" or just "129" into the board search or the global search (Ctrl+K) finds the task.
  • NewSettings > Updates gained a "Check now" button that checks for a new version without waiting for the 30-minute cache.
  • ImprovedIn workspace and board settings the open tab travels in the URL; a reload or a shared link opens the same tab, and back/forward work.
  • FixedThe "Current user" option of the advanced filter is also available in the board search bar. File pickers now list videos (MP4/WebM) and files can be dropped onto task and page attachment lists. The filter menu of right-hand list columns no longer overflows the screen. The boards page shows the board code in front of the name.

v1.49.1

Hotfix: a lone "-" at the start of a line froze the page

1 fixed

  • FixedOn screens that render comments, task descriptions or a preview, a line starting with a dash without a space ("-", "-foo", "--") or a hash without a space ("#tag") sent the text renderer into an infinite loop and the browser tab ran out of memory. Such lines are neither lists nor headings; they now render as plain text. Real lists ("- item") and headings ("# heading") are unchanged. The fix is effective as soon as you update.

v1.49.0

covers v1.47.0 - v1.49.0

Task permissions split up, "remember me", workspace health, and custom field fixes

2 heads-up · 6 new · 3 improved · 2 fixed · 1 security

  • Heads-upThe single "edit task" permission was split into three: assign task, edit built-in fields (labels, dates, sprint, issue type, versions) and edit task (title, description, custom fields). Priority and estimate count as built-in fields. Existing roles lose nothing: every role that could edit tasks receives the new permissions automatically; narrow them from the permission matrix in board settings if you want to. The same split applies to bulk actions.
  • NewComment moderation: roles you grant it to can delete other people's comments, on document pages too. Editing is deliberately out of scope, so a comment can be removed but never rewritten in someone else's name. No existing role receives this permission automatically.
  • ImprovedThe "manage custom fields" permission is now called "board configuration"; it already governed fields, field groups, issue types, versions, task templates and the work calendar, only the name now says so.
  • Heads-upThe sign-in screen gained a "remember me" box, off by default. Sessions used to stay open for 7 days for everyone; now, unless you tick the box, the session ends when you close the browser, and lasts 30 days if you do. Let teams on shared computers know.
  • NewA new "Workspace health" settings tab: who is online, how many people were active today and this week, seat usage, unverified e-mail count and system status on one screen. Scheduled jobs now record when they last ran and how they ended; a job that never ran shows up as a warning.
  • NewMembers who have not verified their e-mail are flagged in the member list; you can filter to just them and resend the verification e-mail on their behalf. Installations with e-mail delivery turned off do not see this section.
  • NewWhen a new version is out, a marker appears on the Updates tab in Settings, and the tab shows when it last checked. After an upgrade, a one-time "What's new" box shows the notes for the installed version.
  • ImprovedPermission denials and warnings such as "this name is already in use" now appear in your interface language; they could show up in a single language regardless of your setting before.
  • SecuritySign-in attempt limits were tightened and the thresholds became configurable from the installation file; in busy offices one person's mistakes no longer lock out others.
  • FixedTyping a digits-only value ("1", "007") into a text custom field left the field looking empty when the task was reopened. The value is now kept exactly as typed, and records affected earlier display correctly too.
  • NewIn saved and advanced filters a person field can be set to "current user"; the filter resolves to whoever runs it. One "assigned to me" filter shows everyone their own tasks.
  • NewVideos attached to a task now play in place on the task screen, no download needed.
  • ImprovedTask screen: person fields show names instead of identifiers; the description saves itself when you click outside it; priority options are listed in the order you defined; the list refreshes on its own after an edit; the pagination bar stays visible in long lists; admins can turn the version label and build number into links.
  • FixedSelecting several tasks in the list and opening one no longer clears the selection or jumps back to the first page. Fields you cannot edit no longer look editable (you used to find out on save). The workflow's auto-assign rule now runs when a task is created too.

v1.46.33

covers v1.46.25 - v1.46.33

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

1 heads-up · 4 new · 4 improved · 1 fixed

  • 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.

v1.46.24

covers v1.46.0 - v1.46.24

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

4 new · 2 improved · 1 fixed · 1 security

  • 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.

v1.45.1

covers v1.45.0 - v1.45.1

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

1 new · 1 improved · 2 fixed

  • 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.

v1.44.1

covers v1.44.0 - v1.44.1

Transition rights can now hang on a person field

1 new · 1 fixed

  • 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.

v1.43.3

covers v1.43.0 - v1.43.3

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

1 new · 1 improved

  • 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.

v1.42.2

covers v1.42.0 - v1.42.2

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

1 new · 1 improved

  • 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.

v1.41.1

covers v1.41.0 - v1.41.1

Half-day holidays and a lunch break

1 new

  • 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.

v1.40.6

covers v1.40.0 - v1.40.6

A work calendar per board and work-hour formulas

2 new · 1 improved · 1 fixed

  • 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.

v1.39.0

A new "Task screen" tab in board settings

1 improved

  • 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.

v1.38.2

covers v1.37.1 - v1.38.2

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

3 new · 1 improved · 1 fixed

  • 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.

v1.37.0

Board-scoped labels, workspace-wide dashboard management

2 new · 1 improved

  • 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.

v1.36.0

Editable built-in roles and a kanban column sort mode

2 new

  • 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.

v1.35.2

covers v1.35.0 - v1.35.2

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

1 new · 3 improved · 1 fixed

  • 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.

v1.34.0

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

4 new · 3 improved · 2 fixed

  • 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.

v1.33.1

One-click status steps and an installation fix

1 new · 2 fixed

  • 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.

v1.33.0

Subtask permissions, a leaner task screen and bulk editing

3 new · 2 improved · 1 fixed · 1 security

  • 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.

v1.32.6

covers v1.32.0 - v1.32.6

Form sections, fill-in permissions and the formula field

1 heads-up · 3 new · 2 fixed

  • 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.

v1.31.0

covers v1.29.1 - v1.31.0

Exports carry every field, and roles are the same everywhere

2 improved · 2 fixed

  • 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.

v1.29.0

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

1 new · 1 improved · 1 fixed

  • 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.

v1.28.0

Role permissions now describe what roles can actually do

1 heads-up · 3 new · 1 improved

  • 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.

v1.27.2

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

1 fixed

  • 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.

v1.27.1

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

1 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.

v1.27.0

People named in a person field can watch the task

1 new

  • 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.

v1.26.1

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

1 improved

  • 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.

v1.26.0

Custom fields on the task form were redesigned

1 improved · 2 fixed

  • 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.

v1.25.0

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

3 new · 1 improved · 2 fixed

  • 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.

v1.24.1

Field settings were not saved, row selection on import

1 new · 2 fixed

  • 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.

v1.24.0

Mentions, comment editing and field defaults

1 new · 2 fixed

  • 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.

v1.23.0

Person and date fields now notify

1 heads-up · 2 new · 1 fixed

  • 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.

v1.22.0

Excel support, WIP limits and approval permissions

2 heads-up · 1 new

  • 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.

v1.21.1

Accessibility fix for the task panel

1 fixed

  • 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.

v1.21.0

Export, bulk import and built-in fields

1 heads-up · 2 new · 1 improved · 1 fixed

  • 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.

v1.20.9

Release notes in your own language

2 improved

  • 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.

v1.20.8

One colour picker everywhere

2 improved · 1 fixed

  • 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.

v1.20.7

One screen for creating a task

2 new · 2 improved · 1 security

  • 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.

v1.20.6

Custom fields, admin permissions and dashboard visibility

1 heads-up · 2 new · 2 fixed

  • 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.

v1.20.5

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

2 fixed

  • 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.

v1.20.4

covers v1.20.3 - v1.20.4

Fixes to task assignment, the login screen and GitLab import

1 heads-up · 2 improved · 2 fixed

  • 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.

v1.20.2

The login lockout no longer blocks normal use

1 improved · 2 fixed

  • 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.

v1.20.1

Internal-network installs work in one step

1 heads-up · 1 improved · 1 fixed

  • 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.

v1.20.0

You choose the published port during setup

1 heads-up · 1 new · 1 fixed

  • 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.

v1.19.2

covers v1.18.1 - v1.19.2

Document permissions split apart, Turkish interface reworked

1 heads-up · 2 improved · 3 fixed

  • 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.

v1.18.0

covers v1.16.0 - v1.18.0

Diagrams in documents, real Word output, and approval notifications

2 heads-up · 2 new · 2 improved · 1 fixed

  • 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.

v1.15.0

Share a dashboard, and let everyone keep their own favorites

1 heads-up · 2 new · 1 improved

  • 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.

v1.14.0

Quality documents: codes, versions and a stricter review

2 new · 4 improved · 1 fixed

  • 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.

v1.13.6

Board settings now sit in the same place everywhere

2 improved

  • 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.

v1.13.5

Connecting GitLab now needs a single scope

1 improved · 1 fixed

  • 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.

v1.13.4

GitLab integration now fixes itself on update

1 heads-up · 1 improved · 1 fixed

  • 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.

v1.13.3

GitLab integration now works on your own server too

1 heads-up · 1 improved · 3 fixed · 1 security

  • 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.

v1.13.2

The PDF report is in your language too

1 fixed

  • 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.

v1.13.1

The review report is easier to read

1 improved · 1 fixed

  • 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.

v1.13.0

Formal document review

2 heads-up · 2 new · 1 improved

  • 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.

v1.12.0

File size limit raised to 25 MB, and now configurable

1 new · 1 improved

  • 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.

v1.11.2

Every warning message is now in your own language

1 improved

  • 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.

v1.11.1

The login screen now opens in your browser’s language

1 improved · 2 fixed

  • 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.

v1.11.0

Emails and interface text now use the right language everywhere

1 heads-up · 3 fixed

  • 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.

v1.10.0

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

1 heads-up · 2 new · 1 improved

  • 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.

v1.9.0

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

1 heads-up · 2 new

  • 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.

v1.8.0

Saved filters can now be shared with people and groups

1 heads-up · 1 new

  • 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.

v1.7.1

The last few board emoji are now badges too

1 fixed

  • 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.

v1.7.0

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

1 heads-up · 1 new · 1 improved · 1 fixed

  • 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.

v1.6.2

Task numbers now follow each board’s own key

1 heads-up · 1 improved · 1 fixed

  • 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.

v1.6.1

Workflow templates now match the board type you pick

1 improved · 1 fixed

  • 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.

v1.6.0

User groups can be added to boards and mentioned in comments

2 new · 1 improved

  • 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.

v1.5.0

covers v1.4.0 - v1.5.0

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

4 new · 1 improved · 2 fixed

  • 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.

v1.3.0

covers v1.2.9 - v1.3.0

Document permissions now enforce roles, and mobile use was overhauled

1 heads-up · 2 improved · 2 fixed · 1 security

  • 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.

v1.2.8

Dates and relative times now follow the interface language

2 improved

  • 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.

v1.2.7

Label management

1 new · 1 fixed

  • 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.

v1.2.6

covers v1.2.2 - v1.2.6

Custom fields, priority and translation consistency

2 new · 2 fixed

  • 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.

v1.2.1

The license screen reports the correct state

1 fixed

  • 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.

v1.2.0

Seat limits: the foundation of the free plan

1 new · 1 improved

  • 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.

v1.1.7

Download packages from inside the app

1 new · 1 improved

  • 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.

v1.1.6

Visual refresh

1 improved · 1 fixed · 1 security

  • 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.

v1.1.3

License traceability

1 improved · 1 fixed · 1 security

  • 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.

v1.1.0

License validation and update checks

2 new · 1 improved

  • 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.

v1.0.0

First self-hosted release

1 new

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

Security

Security updates are listed without details. The reason is simple: installations run on your own servers and not everyone updates on the same day. Publishing the anatomy of a patched issue would put not-yet-updated installations at risk. If you need specifics (e.g. for an internal compliance record), contact support.

How to upgrade your self-hosted installation →