“I’ll just make a quick change.” — Product maintenance at YoureCom, using Work Place as an example

There are a few things I should probably stop saying as a developer.

“I’ll just make a quick change” is pretty high on that list.

Since September 18, Work Place has accumulated 50 commits. They include new features, a revised interface, numerous bug fixes, and a substantial overhaul of the technical foundation.

Meanwhile, the version number is moving from 6.2.13 to the upcoming 6.2.14 update. Considering everything that has changed, it seems almost a little shy.

So this time, I want to take a closer look at what has happened. Work Place is a good example of just how far the ongoing development of an existing product can go.

Task management should help you get work done

Work Place can be used for personal tasks, team coordination, and handling requests. Those use cases place different demands on the same interface.

But they all share one question: What should I do next?

That is why the task overview has been substantially revised. The previous tabs are being replaced by a single list with filters. Your own tasks, unassigned requests, overdue work, and upcoming deadlines can be accessed directly through quick filters. Matching counts help you see how much work is involved.

An optional setting lets Work Place initially focus on tasks due today. Active default filters are made visible, so you can understand why certain tasks are currently missing from the list.

There is also a board view that groups tasks by their processing status. If you prefer cards, you can stay with the card view. Assignees and due dates are shown directly on each task.

At first glance, this might sound like an interface update. In everyday use, though, it determines whether you can immediately identify your next step or have to search through several views first.

And a task management application should generate as little extra administration as possible. Otherwise, we will eventually need a second Work Place to organise the first one.

Creating tasks takes fewer steps

Task creation has also been revised.

A quick dialog provides the essential fields: title, category, task type, due date, description, and the option to assign the task directly to yourself. For more detailed requests, a link takes you to the full form.

The full form has been reorganised as well. Additional settings are grouped into collapsible sections, and the permitted due-date range can be configured.

More importantly, form fields can now be adapted to each task type. Fields that are unnecessary for a particular use case can be hidden, while selected fields can be made required.

A personal reminder needs different information from a work assignment that must have a designated assignee. Administrators can now reflect those differences more precisely.

There is often half a working day between “open” and “done”

A task is open. Then someone starts working on it. Then a reply is needed. Then it is back in progress. Eventually, it is done.

A single open/closed setting can only tell a small part of that story.

That is why Work Place is getting custom processing statuses for each task type. Administrators can configure their order, colour, and initial status in the ACP. A workflow might include “New”, “In progress”, “Waiting for a reply”, and “Done”.

Each status still belongs to either the open or completed group. This allows Work Place’s existing functions to work alongside the more detailed workflows.

Statuses are visible in the overview, can be filtered, and can be changed directly through the action menus. Multiple selected tasks can also be moved to another status together.

Four priority levels, from low to urgent, have been added. Permissions control who can assign them, and the overview supports filtering and sorting by priority.

Open tasks without an assignee can be displayed as a queue, making it easier to spot work that nobody has picked up yet.

“I thought you were doing that” remains entirely possible, of course. It just becomes a little harder to blame the task management application. 😉

Larger projects get individual steps

“Update the website” is a task. A very large, very vague, and remarkably patient task.

Subtasks let you break a project down into specific steps. Progress is displayed both on the task page and in the overview.

A task type can also require all subtasks to be completed before the parent task can be marked as done. That keeps a project open while there is still work attached to it.

For planning, you can additionally record a start date relative to the due date, along with estimated and actual effort. For recurring tasks, the start date follows each occurrence’s due date.

This provides a clearer picture of when work is scheduled and how much effort has been planned or already spent.

Unfortunately, it still does not finish the website for you. That feature did not make it into this update either.

Collaboration stays with the task

When people work together, not every piece of information belongs in a public reply.

A separate area for internal notes has therefore been added. Reading and writing these notes is controlled by a dedicated permission. Discussions can stay with the task instead of being scattered across messages and other communication channels.

For recurring content, administrators can manage reusable text snippets that can be inserted into comments and internal notes.

Similar tasks can be duplicated. The form is prefilled with existing content, while authors and assignees are deliberately not copied automatically. A duplicated task should not accidentally land on a colleague’s desk simply because they handled the previous one.

Polls within tasks add another option for collaboration, allowing decisions to be made alongside the information relevant to the task.

Requests come with their own workflows

If you use Work Place to handle requests, you need more than a list of open tasks.

A request is waiting for its author. A reply arrives. The status needs to change. The people responsible need to know. And sometimes, the same question has been submitted twice.

Several features have been added to support these workflows.

Status changes can be linked to replies. When the requester responds, the task can move back into progress, for example. With the appropriate configuration, their reply can also reopen a completed task.

Notifications for status changes and replies have been expanded. Assignees are included more consistently, while notifications about internal notes only go to recipients with the appropriate permission.

Duplicate requests can be merged. Comments, internal notes, and requesters are transferred to the main task, and the closed duplicate links to it.

For guests, the regular task form can optionally collect an email address with explicit consent. This allows them to receive notifications about certain events. A configurable retention period for those addresses is included as well.

SLA time limits can also be configured by task type and priority. Breaches for open tasks can be displayed, filtered, and communicated through notifications.

None of this replaces good organisation. It does, however, reduce some of the repetitive follow-up work.

Then came the work under the bonnet

So far, much of this can be shown: new views, new fields, new possibilities.

A substantial share of the 50 commits, however, deals with things that do not look particularly exciting in a teaser image.

Recurring tasks have been revised around month and year transitions. The creator’s time zone and daylight saving time are also taken into account. Invalid recurrence intervals have been safeguarded against.

Filters, sorting, and unread counters have been corrected. Multilingual content, change logs, and notifications have been reviewed. Creating tasks in multiple categories and assigning attachments have also been revised.

Other fixes cover group assignments, claiming tasks, assigning labels, reporting tasks, and embedding tasks in content.

Settings that previously did not work as intended have been addressed too. One example is automatically emptying the recycle bin.

These are not extra features to add to a product page. They are existing functions that should reliably do the job they were designed for.

Permissions need to tell the same story everywhere

Task visibility received particular attention.

Private, moderated, and deleted tasks need to be handled according to the appropriate rules in lists, searches, individual views, embedded content, and counters. A task should not be hidden in one place while its title is exposed somewhere else.

These rules have been aligned and backed by additional checks. Comment posting and various task actions have also received more thorough validation.

Bugs were found and fixed in the process. Some affected existing functions; others surfaced during the current overhaul.

That belongs in an honest look behind the scenes. With a change of this size, looking at the new interface and nodding approvingly is not enough. You also need to ask the less comfortable questions: What happens without permission? With deleted tasks? With old data? With multiple languages?

Those are precisely the areas that reveal how much work can sit behind a seemingly small version change.

Technical maintenance also means keeping pace with WoltLab

Alongside this, integration with WoltLab Suite 6.2 has been modernised.

Lists, action menus, and bulk actions have been moved to the Suite’s current systems. Older action mechanisms have been replaced, and the quote system and other integration points have been adapted.

Core operations such as creating, editing, deleting, and restoring tasks are now more clearly separated internally. Additional events provide extension points for connected plugins.

Database queries and content loading have been batched, and caching behaviour has been revised. Integration with personal data exports, IP address pruning, and user-content removal has also been added.

There are improvements to keyboard operation, labels, contrast, and page structure. Collapsible categories, tasks in user profiles, and daily statistics in the ACP further extend integration with the Suite.

Much of this remains in the background during normal use. It still matters for maintainability and future development.

So the next overhaul does not break everything again

Quality assurance has also been significantly expanded.

Automated tests cover recurring dates, visibility, permissions, notifications, and task workflows. New features such as subtasks, status changes, and merging requests have their own checks.

Tests also examine how requests are processed through the relevant endpoints. Additional checks inspect PHP and TypeScript code, language variables, XML files, and package structure.

The PHP code has been brought up to PHPStan Level 9. If that means nothing to you: it is a strict form of static analysis that helps identify potential problems before they appear during use.

These checks do not replace practical testing. They do provide a much better safety net for development.

And yes, that safety net needed repairs along the way as well. Software development has a remarkable sense of humour.

A small version number with a lot behind it

The 50 commits do not represent 50 new features. They represent a combination of functional expansion, revised usability, bug fixes, and technical modernisation.

For users, that means new ways to organise their work. For administrators, more flexibility with forms, permissions, and workflows. And for future development, a better-structured foundation with more automated checks.

The development described here belongs to the upcoming Work Place update and is still in beta. Further checks of the update process and real-world workflows are required before the final release.

That combination is what product maintenance at YoureCom means to me: rethinking an existing product, improving its everyday workflows, and also working on the parts that are harder to sell with a screenshot.

This time, Work Place has received considerably more attention than the version number might suggest.

I would like to say that next time, I will be better at estimating how long “a quick change” takes.

But we did agree to keep this factual. 😉