[OPIK-4473] [FE] Update Traces table default columns

[YarivHashaiComet]

Details

Update default visible columns for new users on the Traces tab. Previously showed: ID, Name, Start time, Input, Output, Duration, Comments, User Feedback. Now shows: Start time, Input, Output, Errors, Duration, Total tokens, Estimated cost, Tags, Comments.

Also split the shared DEFAULT_TRACES_PAGE_COLUMNS into separate DEFAULT_TRACES_COLUMNS and DEFAULT_SPANS_COLUMNS constants so each view can have independent defaults.

Existing users with saved column preferences are not affected (localStorage takes precedence).

Change checklist

• User facing
• Documentation update

Issues

• OPIK-4473

Testing

• Clear localStorage for the traces table (or use incognito)
• Navigate to a project's Traces tab
• Verify the default visible columns are: Start time, Input, Output, Errors, Duration, Total tokens, Estimated cost, Tags, Comments
• Verify ID, Name, and User Feedback are available in the column selector but not shown by default
• Verify the Spans tab still uses its own defaults (unchanged)

Documentation

N/A

[aadereiko]

This solution is ok but we should also take into account that users already have some columns in local storages, and it will work when they open it newly

[baz-reviewer]

migrateColumnsOrder JSON.parses ${type}-columns-order without guarding, so a corrupted or manually edited value throws during TracesSpansTab initialization and the table fails to render; can we wrap this parse in a try/catch and fall back to the default order instead?

Suggested change

	const oldData = localStorage.getItem(oldStorageKey);
	if (oldData !== null) {
	const parsed = JSON.parse(oldData);
	if (Array.isArray(parsed) && parsed.length > 0) {
	return parsed;
	const oldData = localStorage.getItem(oldStorageKey);
	if (oldData !== null) {
	try {
	const parsed = JSON.parse(oldData);
	if (Array.isArray(parsed) && parsed.length > 0) {
	return parsed;
	}
	} catch {
	// Ignore malformed JSON and fall back to defaultOrder
	}

_{Finding type: Logical Bugs}

---

• Apply fix with Baz

[baz-reviewer]

Commit 7d7652f addressed this comment by wrapping the JSON.parse(oldData) call in a try/catch inside migrateColumnsOrder. On parse failure it now ignores the malformed value and falls back to defaultOrder, preventing TracesSpansTab initialization from crashing due to corrupted localStorage.

[baz-reviewer]

Switched to ${type}-selected-columns-v3 with hardcoded defaults but no migration, so every user who had custom selections under the previous ${type}-selected-columns(-v2) keys loses their visibility setup; can we migrate the old localStorage data instead of unconditionally falling back to the new defaults?

_{Finding type: Logical Bugs}

---

• Apply fix with Baz

Other fix methods

Prompt for AI Agents:

In apps/opik-frontend/src/components/pages/TracesPage/TracesSpansTab/TracesSpansTab.tsx
around lines 503 to 510, the selectedColumns initialization (useLocalStorageState) was
switched to `${type}-${SELECTED_COLUMNS_KEY_V3_SUFFIX}` with hardcoded defaults but no
migration. Modify this initialization to attempt to migrate any existing values from the
older keys (`${type}-${SELECTED_COLUMNS_KEY_SUFFIX}` and
`${type}-${SELECTED_COLUMNS_KEY_V2_SUFFIX}`) into the new v3 key before falling back to
the defaults; implement this by reading localStorage (or using an existing migration
helper like migrateColumnsOrder/migrateSelectedColumns if available), normalizing the
stored column arrays, writing the migrated value into the v3 key, and passing that
migrated array as defaultValue to useLocalStorageState. Ensure this runs once on
initialization so users keep their prior custom selections.