2025.09 (Servoy Cloud)

Epic Support

In this release, you can now create epics and link them to tickets. Each ticket can be associated with a single epic at a time. Once linked, epics are displayed in the ticket detail sidebar and as badges in backlog and ticket lists.

Epics help teams break down complex projects into manageable pieces, providing a structured way to organize related tickets. By grouping tickets under epics, teams gain a clear overview of major initiatives, can prioritize work more effectively, and monitor progress across multiple tickets at a glance.

How to use Epics:

• Create or edit Epics: Navigate to Project Management → Epics

• Link tickets to an Epic: Open the Ticket Detail View → Link Ticket

• Once linked, the Epic appears as a badge in the ticket’s side panel on the right.

Creating Epic and linking Ticket to Epic

Connected Work (Ticket Linking)

A new Connected Work tab in the ticket details allows tickets to be linked through defined relationships, including:

• Blocks / Is blocked by

• Duplicates / Is duplicated by

Once tickets are linked, both tickets automatically display the relationship, providing greater visibility into dependencies and duplicate issues. This helps teams coordinate work more effectively, identify blockers quickly, and manage related tasks with clarity.

To see and manage Connected work, open the Ticket Detail View → Connected Work tab

Ticket Connected work - Linking tickets to each other

Project Overview Dashboard

A new Project Overview Dashboard provides a comprehensive view of your project through three key charts:

• Sprint Velocity — tracks completed story points over time, helping teams monitor progress and predict future capacity.

• Epic Overview — displays story points grouped by epic, giving a clear picture of how work is distributed across major initiatives.

• Story Points Overview — shows the overall workload distribution across all tickets in the project, displaying total story points versus remaining story points.

These charts give teams actionable insights into performance, workload, and progress. By visualizing sprint output, epic distribution, and total versus remaining story points, teams can plan sprints more effectively, prioritize work, and make informed decisions to keep projects on track.

Database Structure View

A new Database Structure view allows you to explore your database’s structure in the cloud environment. The view provides detailed information about:

• Tables — name, size, number of rows

• Columns — name, type, length, primary key flag, tenant flag

• Indexes — name, columns, size, usage

This feature helps verify that the deployed database matches your local environment, understand the schema without needing direct database access, and gain visibility into table and index usage, helping diagnose performance or design issues in production

Fixes and Improvements

This release includes several fixes and improvements designed to enhance reliability, usability and efficiency of the project management experience:

Personalization and Settings

• Default Ticket Placement: A new namespace-level setting allows administrators to define whether new tickets are placed at the top or bottom of the backlog. This setting applies to all users within the namespace. To configure Default ticket placement:

  1. Navigate to Administration → Settings → Project Management

  2. Change the default value to desired behavior (Note: Default placement is at the bottom of the backlog)

• User Filter Preferences: Individual users’ filter selections are now stored in a cookie and automatically restored when they return to the previous screens.

• Permissions: Certain project management actions now require updated roles, ensuring permissions align correctly with user responsibilities.

Breaking change

Users who previously had access to these actions may require a role change in order to continue performing them and fully benefit from the given functionality.

AI Spellcheck

An AI-powered spellcheck is now available for ticket descriptions and comments. This feature helps improve content quality by making corrections for spelling errors.

Consent Requirement: The AI Spellcheck feature requires user consent before it can process any data. Upon first use, users are presented with a Data Processing Consent dialog that explains:

• Data may be shared with external platforms or services to enhance application performance.

• Full details are available in the ServoyAI Privacy Policy.

• Once accepted, the notification will not appear again.

• Users are responsible for keeping themselves updated with the privacy policy.

Users who decline will not be able to use AI spellcheck, ensuring compliance with data protection standards.

AI Spellcheck feature in the "Create New ticket" view

Cloud plan widget

A new Cloud Plan Widget is now available for users with the Developer role or higher. The widget provides a clear view of your namespace cloud plan, including:

• Builds per day

• Satellites (on-premises deployments)

• Prints per day

• Current number of users in production

This widget helps teams monitor resource usage against plan limits, ensuring that builds, deployments, and usage stay within allowed thresholds. By tracking these metrics proactively, you can avoid exceeding quotas, prevent disruptions, and make informed decisions—such as updating the plan—if additional capacity is needed.

Cloud plan example with limits or unavailable features

Cloud plan example with unlimited builds/prints

Create Ticket from Log Activity

Tickets in the Ticket System can now be created directly from log activity, with the title, reporter, and description automatically prefilled.

To create a ticket from Log Activity:

1. Navigate to Environment → Log Activity

2. Click [show more] on a log entry in the table

3. In the Log Detail Dialog, click Create Ticket to open the ticket creation dialog

Tickets created this way can be viewed under Project Management → Tickets.

Project Management | Create ticket from Log Activity

Log Export Enhancements

Exported log details now include the username along with the previously included information, providing better traceability and context for auditing or troubleshooting.

Other fixes and improvements

• New ticket status "REOPENED": A new ticket status, “Reopened”, has been introduced. Tickets with the status “Done” can now only be changed to Reopened, thus allowing you to modify ticket details. Reopened tickets function similarly to Open tickets.

• Expanded Filters: Filters now include issue type, epic, and priority.

• File manager: Added a file count to improve visibility of stored files

• Database List

  • Databases in the list now display the currently deployed SQL version. This applies to environments using versioning via SQL migration files and svyCloudUtils.

  • Fixed an issue where databases were not displayed correctly when there was a large number of entries.

• Email Notifications: Correct user is now displayed in email notifications for comments.

• Comment Saving: Saving comments has become more reliable.

• UI Refresh: The user interface now refreshes according to user activity

• Active Board Filters: Moving tickets in the active board now takes into account active filters

• Ticket Sorting: Drag-and-drop ticket sorting is now consistently reflected in the UI.

• User Lists: Assignee and reporter lists now show only active users.

• Auto-build of outdated environment: Resolved cases where outdated environments were not automatically scheduled for a build.

• Updated Android SDK to version 36 and Android API to version 35.

• Fixed login issues with users using case-sensitive email addresses

• Mirrored Repositories now ignore LFS files during initial sync to improve performance.

• Starting a build which uses a mirrored repository, now triggers a force-sync to include the latest changes

• Fixed an issue that occurred when a namespace had only one contact configured.