Skip to main content

v5.14.2: Assignee-Based Notifications

Release date: 2026-08-05

Written by Kestutis Vansavicius

v5.14.2 highlights:

  • Subprocess notifications can now target whoever's assigned, not a fixed name

  • New 3-month range for dashboards

  • Upgraded Issues table with filters and custom views

  • Combined custom fields for tasks and processes

  • Custom field filtering on dashboards, reports, and scorecards

  • Team Approvers can review approval stages

  • Labeled file uploads for approval requests


Subprocess notifications: notify whoever's assigned, not a fixed name

Subprocess notifications can now target an assigned person (avatar) instead of a static user.

Previously, recipients had to be set one by one - a person, a team, or an external contact. If assignments changed over time, teams either kept updating names by hand or notified a whole team just to reach the one person who needed to act.

Four new recipient options fix this:

  • Assignee

  • Approver

  • Backup assignee

  • Backup approver

Each one automatically notifies whoever holds that role on the subprocess when the notification is sent. Reassign the subprocess, and the notification follows - no manual upkeep.

Naming change: "Maker" is now called "Assignee" throughout the app ("Backup maker" → "Backup assignee"). How assignment works is unchanged. The "Maker" notification option keeps its name and still notifies whoever completed the item.


Dashboards: New 3-month range for dashboards

The dashboard range now includes a 3 months option, between Month and Year.

The 3-month view shows three calendar months side by side, centred on the month selected in the date picker - choosing July shows June, July, and August. Unlike other ranges, the arrows move the view one month at a time, so each step overlaps with the last. Otherwise it behaves like the Year view: one column per month, showing processes.


Issues: Filter, sort, and customize the Issues table

The Issues table now supports preset tabs, a full filter set (including custom fields), configurable sorting, and show/hide columns.

Previously, the Issues table offered only a title search and page-size control - no filtering by status, team, owner, impact, process, dates, or custom fields, no configurable columns. Now you can slice and filter issues yourself - for example, "open issues assigned to me" or "high-impact issues in this process."


Combine several custom fields on tasks and processes

Custom fields on tasks and processes can now be grouped into a single combined field, the same way this already works for issues.

Instead of showing several related dynamic fields separately, you can present them as one tag option instead of filling in three separate fields.

💡Custom fields are currently configured by the Daymi team. If you're interested in setting up custom fields for your organization, please contact [email protected].

Example of an Issue Type field in Issues


Filter and save custom fields on dashboards, missed deadlines report, and scorecards

Custom fields can now be used to filter your work in more places.

  • Dashboards - filter subprocesses and tasks by dynamic fields on both the older dashboard version and any custom dashboards, and save those filters, including as quick filters. Filters on the older dashboard version now look and behave the same as the newer ones.

  • Missed deadlines report - set up the report using dynamic fields as filters.

  • Scorecards - add dynamic fields to scorecards.


Approvals: Team Approvers can now review approval stages

The team Approver role can now review approval stages, if that selection is chosen in the approval request type's workflow - without needing team-admin rights specifically.


Approvals: Add labeled file upload fields to request types

Approval request types can now define named file upload fields, instead of relying on a single generic attachment area.

Previously, every request had one built-in attachment box - no way to ask for specific documents separately, mark one mandatory.

Now, the request-type builder supports a File upload field type. Each field has its own name, an optional mandatory toggle, and accepts multiple files.


Bug Fixes

  • Fixed an issue where the process owners field overflowed and didn't fit within its bounds when many teams were added as owners.

  • Fixed a misleading message shown when opening an invite link for a user who was automatically added to an organization because they already had an active account - the invite incorrectly appeared as expired.

  • Fixed an issue where emailing a Subprocess performance or Main process performance report failed with a server error when no dynamic field filter was selected.

  • Fixed a silent save failure when a process template form had circular dependencies between subprocesses - a clear error message now explains the issue.


Other

Under-the-hood improvements

This release includes routine security and maintenance updates. No changes to how you use the app.

Did this answer your question?