Skip to the latest update
LogbookProduct updates, with the details.
Version 1.8Feature

Keep the view. Lose the setup.

Save a combination of filters as a named view, then come back to the same working set without rebuilding it.

Interactive sample
OrbitWorkspace / Team workv1.8

Team work

A live list of sample work items.

Work itemOwnerStatusDue
Review onboarding copyWebsite
MMayaIn progressToday
Document keyboard behaviorProduct
MMayaIn progressToday

2 of 6 items

Changes stay in this browser preview. No account is connected.

A saved view remembers all three filters. Change the list, then restore the saved view to see the difference.

Read full release notes

A view is a set of decisions

A view remembers the owner, status and project you selected. Its name appears above the work list, so the context remains visible even after you close the filters. Views in this demonstration are kept only for the current page visit.

Change your mind without losing the original

Adjusting a saved view creates a temporary variation. Choose Restore saved view to return to the saved filters, or save the variation under a different name. The original is never silently overwritten.

Nothing changes for your existing work

The feature changes how a list is displayed. It does not move, reassign or delete the sample items. Existing unfiltered lists remain available through Reset filters.

Illustrative release history

Availability
Local demonstration
Data
Six illustrative work items
Persistence
This page visit only

A quieter way to keep up.

Choose the updates you want to receive. Preview the subscription before connecting your own email service.

Sample form. No email will be sent.

The small things,
made a little better.

Two recent updates that make everyday work easier to understand.

Version 1.7.1Fix

The right day, in every view.

All-day dates now retain their calendar day when a shared view is opened in another time zone.

Read full release notes

Dates are not always timestamps

An all-day due date is stored and displayed as a calendar date. A timed event still includes its time-zone context. Treating the two values separately prevents a midnight conversion from showing the preceding day.

What to check in your integration

For a date-only field, use YYYY-MM-DD. For a scheduled event, include an explicit offset. These notes describe the sample product model; connect and test your own date handling before launch.

Illustrative release history

Availability
Local demonstration
Data
Six illustrative work items
Persistence
This page visit only

A quieter way to keep up.

Choose the updates you want to receive. Preview the subscription before connecting your own email service.

Sample form. No email will be sent.

Version 1.7Feature

Make the next step someone’s step.

A handoff keeps the decision, the next action and its owner in one place.

Read full release notes

A handoff, not another notification

The record contains a short decision, a named owner and a concrete next action. The receiving person can read the context before accepting responsibility. This is more useful than a message that merely says an item has changed.

An explicit unfinished state

If an owner has not been chosen, the handoff remains a draft. The interface tells you which field is missing rather than inventing a default assignment.

A readable history

Accepted and returned handoffs stay in the same chronological list. A return includes a reason, so the next attempt begins with the missing context rather than another blank form.

Illustrative release history

Availability
Local demonstration
Data
Six illustrative work items
Persistence
This page visit only

A quieter way to keep up.

Choose the updates you want to receive. Preview the subscription before connecting your own email service.

Sample form. No email will be sent.

Handoff / Website launchAccepted

Ship the revised onboarding.

Decision
Keep the first screen focused on the project name. Ask for team members after the project exists.
Next action
Maya will prepare the final copy and keyboard states.
Owner
Maya · Product design

Illustrative record. No task has been assigned.

What we’re
working through.

A roadmap should distinguish a question from a commitment. These are sample planning notes, not launch promises.

Share a saved viewIn design

Let a teammate open the same filters without changing their personal workspace. The open question is how to show permissions before a link is shared.

Next step
Prototype the permission preview.
Not decided
Whether shared views can be edited together.
Keep a local change historyExploring

Show which fields changed, who changed them and how to return to the earlier state. The history should explain the decision without overwhelming the work itself.

Next step
Study which changes need a visible record.
Not decided
How much history a compact view should show.
Make recurring work explicitExploring

Separate the repeating rule from the next individual item. Completing one occurrence should not accidentally remove the plan for the next.

Next step
Map completion, skip and stop states.
Not decided
How exceptions affect future dates.

3 planning notes

A release is a change.
The work should stay yours.

These updates share one principle: make the new behavior clear without quietly changing the existing work.

  • A saved view changes the list, not the items.
  • A date fix preserves the intended calendar day.
  • A handoff names an owner before it is accepted.
Try the latest change

A few useful details.

Does this example connect to a real account?

No. The work items, release history and planning notes are illustrative. Filters, saved views and subscription previews run locally in this page.

Will a saved view survive closing the page?

This prototype keeps saved views for the current visit only. A production product should store them against an authenticated account and make its persistence rules visible.

What does the subscription preview do?

It validates the email address and shows the selected cadence. It does not subscribe anyone or send an email. Connect your own mailing service before using the form on a live publication.

How should release notes be written?

Start with what changed for the person using the product. Show the changed behavior, explain relevant compatibility details and distinguish available features from plans.