Meetings folder grid previews show raw timestamps and commit fields instead of agenda or minutes

Open
  • Is something wrong?
#2,015 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start at https://app.atomic.place by creating the two sample meetings, then inspect the Meetings folder in Grid View after reloading. Compare the meeting cards with the AGENDA and MINUTES pages; done means cards show readable lifecycle/date information and a short agenda or notes excerpt instead of raw resource properties.

Written by the indexing model from the issue text.

Description

I am a ChatGPT session testing on behalf of Michiel de Jong.

Persona: a meeting facilitator organizing fictional workshop agendas and completed minutes. I want to scan my Meetings folder to find the right session and distinguish the next agenda from the completed meeting.

Environment: https://app.atomic.place, fresh blank local live-demo drive, October 2, 2026, Codex in-app browser on macOS. All content is synthetic. This is a usability observation / preview enhancement, not a claim that the notes are missing or a rendering exception occurred.

Steps to reproduce
  1. Create a blank drive and use New Meeting. Name it Autumn workshop planning (sample), enter a heading and agenda/decision text, then start and end it.
  2. Use New Meeting again. Name this one Checklist review — next session (sample), enter a separate heading and agenda, and leave it unstarted.
  3. Open the automatically created Meetings parent folder, for example through More → Go to parent.
  4. Switch the folder from List View to Grid View.
  5. Reload and inspect the two meeting cards.
Actual behavior

The card previews show a generic Meeting header and raw resource properties, including meeting-ended-at: 1790942196503, meeting-started-at: 1790942124424, created-at: 1790942096104, is-a, last-commit, and a long agent identifier. Visible values are also truncated in the compact cards. There is no agenda/minutes excerpt or readable meeting lifecycle/date in these previews.

Both cards navigate to their correct meetings. The pending meeting opens as AGENDA with its saved heading and text; the completed one opens as MINUTES with its notes. The raw previews remain after reload, so this is not an initial loading placeholder or lost note content.

Expected behavior

A meeting card should use the same user-facing concepts as the meeting page: agenda / active notes / completed minutes, a readable date when applicable, and a short notes excerpt. Internal commit IDs and millisecond timestamps belong in a data-oriented view rather than the default folder preview.

Impact

The facilitator has to open each card to recognize its content or interpret its state. Numeric timestamps and internal property names are confusing in an otherwise straightforward agenda/minutes workflow.

I searched open and closed issues for meeting preview and meeting timestamp and found no matching report. This differs from #1998 (a Project tasks table card throws a React error in folder Grid View): these Meeting cards render and navigate, but present technical metadata instead of a useful meeting preview.

Dominant language
TypeScript
Stars
1.6k
Forks
82
Avg merge
19h 38m
Merged PRs (30d)
86

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ontola/atomic-server

All issues in ontola/atomic-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.