Two UX issues and two API issues:

Hi — some feedback after migrating ~1,900 time entries between workspaces.

Context on how this was found: the investigation and migration were carried out

by Claude Opus 5 (Anthropic) running in Claude Code, working against your GraphQL

API and the desktop app. All four issues below surfaced during that work. A

second model, OpenAI Codex (GPT-5.6), was used to review the migration tooling

itself — it didn't find these, but it's why the migration ran without touching

teammates' data. Issue 3 in particular was only caught because a human screenshot

of the settings UI contradicted what the API was reporting.

Two UX issues and two API issues:

1. TIME SILENTLY LANDING IN THE WRONG WORKSPACE

I've been an active member of a team workspace, but all of my tracked time was

going into my old personal workspace instead. The team report showed me at 0.0h

for over two years — ~958 hours across ~1,900 entries — with nothing in the UI

indicating the data existed elsewhere. Rize knows both facts (that I'm an active

member of the team, and that I have entries piling up in another workspace) but

never connects them. A warning when a member's tracked time is accumulating

outside the team they belong to would have caught this immediately.

2. TWO "DEFAULT TEAM" SETTINGS, AND THE HIDDEN ONE WINS

"Default Team" under Settings > Time Entries is separate from the profile-level

default team, and silently overrides it. My profile showed the correct team the

whole time while entries went to the wrong one. Worth cross-referencing these in

the UI, or warning when they disagree.

3. API: auto_tag_* FIELDS DON'T REFLECT ACTUAL STATE

get_tagging_settings returns auto_tag_clients / auto_tag_projects /

auto_tag_tasks as false, while the corresponding "Enable ... Suggestions"

toggles are switched on and the feature demonstrably works (entries come back

with project assignments and tag suggestions at 85-95% confidence). The API

field appears disconnected from the real setting. This one actively caused a

misdiagnosis — an automated agent reading the API would reasonably conclude the

feature was disabled.

4. API: OPAQUE ERROR WHEN MOVING AN ENTRY BETWEEN WORKSPACES

updateTimeEntry with a new teamId fails with:

"An unexpected error occurred: Non-matching team ids found for time entry"

...whenever the entry still references a project belonging to the source

workspace. The fix is to explicitly null clientId / projectId / taskId in the

same mutation, but neither the error nor the docs mention this. Since the API

clears those assignments on success anyway, it could either do so automatically

or return an error that says what to clear.

Also, docs.rize.io doesn't currently document how tracked time is attributed to

a workspace at all — the Teams setup pages cover creating teams and inviting

members, but not which workspace a member's entries actually land in.

One broader note: AI agents are increasingly going to be the ones reading your

API and acting on it. Issues 3 and 4 are both cases where the API's self-report

or error message would lead a competent agent to the wrong conclusion. Those are

worth weighting higher than they'd have been a year ago.

Happy to provide reproduction details for the API issues if useful.