Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>last_assigned_at</code>

Description: The datetime at which a user was last assigned to the item.

GitHub, GitLab, Jira, and Trello: It is the datetime of the last <code>user assigned</code> event, which happens when a user is added to the list of assignees.

ClickUp: Since this app do not expose historical events, Keypup tracks changes on the <code>assignees</code> field to detect this timestamp. This tracking only applies to assignments performed after the project has been connected to Keypup. This field remains null when we detect that reviewers were assigned prior to importing the issue or pull request to Keypup because we cannot know precisely when this assignment occurred. ​

- GitHub, GitLab, Jira, and Trello: It is the datetime of the last <code>user assigned</code> event, which happens when a user is added to the list of assignees.
- ClickUp: Since this app do not expose historical events, Keypup tracks changes on the <code>assignees</code> field to detect this timestamp. This tracking only applies to assignments performed after the project has been connected to Keypup. This field remains null when we detect that reviewers were assigned prior to importing the issue or pull request to Keypup because we cannot know precisely when this assignment occurred. ​

Issues and PRs > Last assigned at

Find answers and get help from Intercom Support and Community Experts

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Title

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

From:
Github (PRs, Issues)	The date of the last `user assigned` event
Gitlab (PRs, Issues)	The date of the last `user assigned` event
Bitbucket (PRs)	N/A - no concepts of assignment
JIRA (Issues)	The date of the last `user assigned` event
ClickUp (Issues)	Use `updated_at` when the `assignees` attribute is populated.
Trello (Issues)	The date of the last `user assigned` event