Dataset: Activity Events
Entity: Activity Events
Field ID: created_at
Type: Datetime
Description: The datetime at which the event was created.
Note that this may not always reflect when the event is supposed to have occurred. For instance, it is common for users to set a date when submitting WORK_LOGGED events. This date is captured via the Value at field, which may be more suitable if you are looking at displaying events in chronological order of occurrence.
Source: Applications support the following events
Github:
CREATED,CLOSED,REOPENED,MERGED,REVIEWER_ASSIGNED,REVIEWER_UNASSIGNED,USER_ASSIGNED,USER_UNASSIGNEDGitLab:
CREATED,CLOSED,REOPENED,MERGED,REVIEWER_ASSIGNED,REVIEWER_UNASSIGNED,USER_ASSIGNED,USER_UNASSIGNED,WORK_LOGGEDBitbucket:
CREATED,CLOSED,MERGED,REVIEWER_ASSIGNED,REVIEWER_UNASSIGNEDJira:
CREATED,CLOSED,REOPENED,USER_ASSIGNED,USER_UNASSIGNED,WORK_LOGGED,WORKFLOW_STATUS_UPDATEDClickUp:
CREATED,CLOSED. ClickUp does not expose an events API. Keypup generates these two events based on the issue timestamps (date_created&date_closed)Trello:
CREATED,CLOSED,REOPENED,USER_ASSIGNED,USER_UNASSIGNED,WORKFLOW_STATUS_UPDATED
Transformation logic: N/A
From: |
|
Github (Timeline Items) |
|
Gitlab (Discussions, State Events) |
|
Bitbucket (Activity) |
|
JIRA (Changelog, Worklog) |
|
ClickUp (Issue timestamps) |
|
Trello (Actions) |
|