Bug #226
closed
webapp session page - adding a checkin to one session adds it to all sessions
Added by Sam Pearson 21 days ago.
Updated 19 days ago.
Description
on the sessions page, if you add a checkin to one session, it is applied to all sessions.
You can even expand the search scope and then look at the newly-displayed sessions, they'll have the checkin as well.
API endpoint is broken:
searching for a target id that doesn't exist:
{{protocol}}://{{host}}:{{port}}/api/checkins?target_type=session&target_id=99999
returns whatever session happens to have a checkin:
[
{
"created_at": "2026-06-25T20:39:18.444177+00:00",
"id": 1,
"note": "big party",
"occurred_at": "2026-06-25T20:39:18.427000-05:00",
"target_id": 5,
"target_type": "session",
"updated_at": "2026-06-25T20:39:18.444185+00:00",
"user_id": 1
}
]
- Status changed from New to Resolved
checkins_bp.add_url_rule("/api/checkins/target", view_func=checkins.list_checkins, methods=["GET"])
checkins_bp.add_url_rule("/api/checkins", view_func=checkins.list_all_checkins, methods=["GET"])
hitting the wrong endpoint.
updated session_display.js to hit the correct endpoint, seems to be working fine now.
- Target version set to V2.2.1 - Usability MVP
- Status changed from Resolved to Closed
Also available in: Atom
PDF