This week, project boards got better at understanding what “done” actually means. You can now designate completion columns so finished tasks move to the right place automatically, removing a common source of duplicate work and inconsistent boards.
We also made dashboard deadlines directly actionable, expanded Settings to support every IANA time zone, and tightened the scope of these weekly updates to focus only on changes you can use in the app or through the API.
Your board now knows where completed tasks belong
You can now mark a project board column as a Done column. The option lives in the same column menu you already use to set the sprint column, so you can define where completed work belongs without changing your board’s structure.
Once your project has a Done column, changing a task’s status to Done automatically moves that task into the designated column. You no longer need to complete the task and then drag it across the board separately, and completed work is less likely to remain stranded in an active column.
This keeps two views of the same work aligned: the task’s status and its position on the board. When someone reviews the project, the board more accurately reflects which work is still underway and which work has reached a completed stage.
The new behavior also supports boards with more than one completion stage. For example, your workflow might include both Done and Released columns. In that setup, tasks advance through the Done columns one step at a time rather than skipping directly to the final column.
A task already sitting in a Done column will stay where it is. Updating its status will not unexpectedly push it farther along the board when it is already in an appropriate completion stage.
In practical terms, the updated board behavior gives you:
A project-level choice of which columns represent completed work
Automatic movement when a task’s status is set to Done
Fewer completed tasks still appearing in an active column
Support for workflows with multiple Done columns, such as Done followed by Released
One-column-at-a-time progression across multiple completion stages
Stable placement for tasks already in a Done column
The result is a small but meaningful reduction in board maintenance. Your team can complete work from the task itself and trust the board to reflect that change, while projects with staged completion can preserve the flow they need.
Upcoming deadlines take you straight to the work
The Upcoming Deadlines area on the dashboard is now clickable. Select a listed task or SOP run, and OKiDO takes you directly to it instead of making you leave the dashboard and search for the item elsewhere.
This makes the dashboard more useful as a starting point for the day. You can review what is approaching, open the relevant work immediately, and move from awareness to action in fewer steps.
The change applies to both types of work shown there: individual tasks and SOP runs. Whether the deadline belongs to a project task or an active process, the dashboard now provides a direct route to the underlying item.
For teams managing several projects or recurring procedures, that direct navigation also reduces ambiguity. You do not need to remember which project contains a task or locate the correct run from a broader list; the deadline entry itself is now the link.
Time zone settings now work for teams everywhere
You can now choose any time zone from the full IANA time zone database in Settings. The previous picker offered fourteen options, which left many teams choosing an approximation rather than the location that accurately matched their work.
The expanded list includes cities and regions such as Lisbon, Amsterdam, and São Paulo, along with the rest of the IANA database. This gives distributed teams and people working across regions a more precise way to configure their local time zone.
Finding the right option is easier as well. You can search the picker by city or UTC offset, depending on the information you have. If you know the location, search for the city; if you are coordinating around a specific offset, search for that instead.
Familiar labels such as Eastern Time and CET remain pinned at the top. Common choices stay quick to reach, while the complete database is available when you need a more specific region.
The updated picker combines broader coverage with faster selection:
Every IANA time zone is available
City names are searchable
UTC offsets are searchable
Familiar time zone names remain pinned at the top
You can review your current selection in Settings and switch to the time zone that best represents where you work. This is particularly useful if your location was not included in the previous fourteen-option list.
Weekly updates now focus on the product you use
The weekly What shipped this week at OKiDO blog post and newsletter now cover only changes to the OKiDO app and API. Work related to the admin portal or marketing site will no longer appear in either update.
This gives you a clearer, more relevant weekly summary. Every item you read will relate to something customers can use in the product or access through the API, rather than work that does not affect your day-to-day experience.
Both updates continue to be built from OKiDO’s daily changelog files. Each changelog entry now identifies the application it applies to, allowing the weekly blog post and newsletter to maintain that customer-facing scope consistently.
For readers, the practical difference is simple: less time spent separating product changes from unrelated updates. If a change appears in the weekly post or newsletter, you will know it belongs to the app or API surface available to customers.
This week’s changes remove friction at several common points in the working day: finishing a task, opening an approaching deadline, and configuring the correct local time. They also make the update you are reading more focused on changes that directly affect how you use OKiDO.
Try marking a board column as a Done column, opening an item from Upcoming Deadlines, and checking the expanded time zone picker in Settings. If your team uses multiple completion stages, designate more than one Done column and let tasks progress through them in order.
