Skip to main content

jira.psom_comment

Every comment on every PSOM ticket, one row per comment per snapshot.

Every comment on every PSOM ticket, one row per comment per snapshot.

Each row is one comment on one ticket (key) as it stood on one snapshot date. Join to psom on key and date.

Keywords: jira, psom, comments, internal notes, replies, support

Provenance

Written by the psom-sync Lambda in the same run as psom, from each ticket’s full comment history. Snapshots before 2026-09-29 were backfilled from the JSON comments column that psom used to carry.

  • Updated: Daily, at ~06:00 ET
  • Retention: 2 years
  • Steward: EDCP Data and Research Team
  • Contact: Yinlin Zhang (Data and Research team)

Fields

Field Name Type Description
date varchar Partition key: the date the Lambda ran (YYYY-MM-DD).
key varchar Jira ticket key, e.g. PSOM-42.
comment_id varchar Jira’s ID for the comment. Null before 2026-09-29.
author varchar Display name of the comment’s author.
created varchar ISO 8601 timestamp when the comment was posted, e.g. 2026-07-02T08:32:40.494-0400.
updated varchar ISO 8601 timestamp when the comment was last edited. Equals created if never edited.
body varchar The comment text, extracted from Atlassian Document Format (ADF) to plain text.
internal boolean Is the comment a JSM internal note, hidden from the customer? false means a public reply.
fetched_at varchar UTC timestamp when the Lambda wrote this row (YYYY-MM-DD HH:MM:SS).

Notes

Every snapshot repeats every comment. Like psom, each partition holds the full comment history of every ticket still in the project, so a comment appears once per snapshot. Filter to one date before counting. Comments on archived tickets drop out along with the ticket (see psom).

Backfilled history (through 2026-09-28). Snapshots are daily from 2026-09-29. Before that they were weekly, on Mondays. In the backfilled snapshots, comment_id is null. To match a comment across them, use key, author and created.