Feature requests

We value the input of our users in shaping the future of our software. Feature requests allow us to understand your needs better and help prioritize development. This document describes how we handle feature requests for the Timefold Models and Platform and how you can participate in this process.

If you have a feature request for the open source Timefold Solver, please submit it via our Github Issue Tracker.

Submitting a feature request

If you have a feature idea or a need that isn’t currently met by our platform or models, you can submit a feature request by visiting our feedback requests board.

From there you can create a new feature request or browse and upvote existing feature requests.

If you can’t find the idea already posted, create a new post. We encourage you to provide as much detail as possible in your request, including: - The problem or challenge you’re currently having. - Your idea for a feature or improvement that could address this problem. - Any specific examples of how it would benefit your business.

It helps us if you choose the most fitting category for your feature request, but don’t worry too much about this.

Categories

We distinguish between the following categories on our feature requests board:

Employee Shift Scheduling

Any requests specifically for the Employee Shift Scheduling model, e.g. new constraints, KPIs, updates to its visualization, or other requests.

Field Service Routing

Any requests specifically for the Field Service Routing model, e.g. new constraints, KPIs, updates to its visualization, or other requests.

Machine Job Scheduling

Any requests specifically for the Machine Job Scheduling model, e.g. new constraints, KPIs, updates to its visualization, or other requests.

New Models

Any requests related to models that aren’t publicly available yet on the Timefold Platform.

Timefold Cloud Platform

Any requests related to Platform features and not model-specific, e.g. the insights and comparison tools, the scaling features, the administration backend, or other requests.

Uncategorized

Anything that doesn’t fit any of the above categories. (If you’re unsure what to use, post your idea here, and we’ll categorize it when triaging new requests.)

Themes

To bring more structure and overview into the different feature requests, we use labels to group them in the following themes:

Solution Quality

Improving the inherent quality of a planning solution.

Getting Started Experience

Making it easier to understand and get started with using a Timefold model.

Platform for Integration Developer

Developer tooling to make integrating the Timefold Platform in your own software easier.

Platform Integrations

Integrations with other types of business software.

Strategic Decision Making

Receiving strategic insights and recommendations from your operational planning (comparison tools, simulations, stakeholder management).

BYO Model

Making developing planning models easier.

Model Feature

Any model specific features (e.g. new constraints), relevant for a single Timefold Model.

Evaluation & prioritization

Our Product team reviews every feature request we receive. We focus first on understanding the problem or challenge you’re encountering and possible solutions to that problem. Prioritization will take into account alignment with the product vision, technical feasibility, business impact, and customer demand.

While not every request can be added to the product, we do keep all requests on record, and they’re regularly reviewed as our products evolve.

Make sure to upvote existing ideas on the feature requests board that would also help you.

Statuses

The following statuses are used on the feature requests board:

Under Review

We’re evaluating the request for potential inclusion in our roadmap. (We also keep ideas in this status if they need more customer demand first.)

Planned

The feature has been accepted and we plan to build the feature.

In Progress

We’re actively working on this feature.

Complete

The feature has been launched and is available for use. More details about the version from which it is available, or how to use it will be posted as a comment on the post.

Closed

Unfortunately, this feature may not align with our roadmap or has been declined for other reasons. More details about why it wasn’t accepted will be posted as a comment on the post.

Each time the status of an idea you posted or upvoted changes, you’ll be notified via email.

FAQs

What if my feature request is not accepted?

While we strive to meet user needs, not all feature requests are possible or feasible to implement. However, we keep a record of every request for future consideration, and in some cases, alternative solutions may be recommended.

How can I get updates on a feature I requested?

For all posts you created or upvoted via the feedback requests forum you’ll receive an email notification if your requested feature changes status. Alternatively, you can check the status by going to feedback requests forum and using the "My Own" filter.