Keypup

Description: The datetime at which the event is supposed to have occurred, as specified by the author of the event. The <a href="https://docs.keypup.io/en/articles/10064175-activity-events-created-at">Created at</a> value is used otherwise.

This field will only differ from the <a href="https://docs.keypup.io/en/articles/10064175-activity-events-created-at">Created at</a> field on <code>WORK_LOGGED</code> events if the user has manually specified a date for their work.

Source: Applications support the following events

Github: <code>CREATED</code>, <code>CLOSED</code>, <code>REOPENED</code>, <code>MERGED</code>, <code>REVIEWER_ASSIGNED</code>, <code>REVIEWER_UNASSIGNED</code>, <code>USER_ASSIGNED</code>, <code>USER_UNASSIGNED</code>

GitLab: <code>CREATED</code>, <code>CLOSED</code>, <code>REOPENED</code>, <code>MERGED</code>, <code>REVIEWER_ASSIGNED</code>, <code>REVIEWER_UNASSIGNED</code>, <code>USER_ASSIGNED</code>, <code>USER_UNASSIGNED</code>, <code>WORK_LOGGED</code>

Bitbucket: <code>CREATED</code>, <code>CLOSED</code>, <code>MERGED</code>, <code>REVIEWER_ASSIGNED</code>, <code>REVIEWER_UNASSIGNED</code>

Azure DevOps: <code>CREATED</code>, <code>CLOSED</code>, <code>MERGED</code>, <code>REVIEWER_ASSIGNED</code>, <code>REVIEWER_UNASSIGNED</code>

Jira: <code>CREATED</code>, <code>CLOSED</code>, <code>REOPENED</code>, <code>USER_ASSIGNED</code>, <code>USER_UNASSIGNED</code>, <code>WORK_LOGGED</code>, <code>WORKFLOW_STATUS_UPDATED</code>

ClickUp: <code>CREATED</code>, <code>CLOSED</code>. ClickUp does not expose an events API. Keypup generates these two events based on the issue timestamps (<code>date_created</code> &amp; <code>date_closed</code>)

Trello: <code>CREATED</code>, <code>CLOSED</code>, <code>REOPENED</code>, <code>USER_ASSIGNED</code>, <code>USER_UNASSIGNED</code>, <code>WORKFLOW_STATUS_UPDATED</code>

- Github: <code>CREATED</code>, <code>CLOSED</code>, <code>REOPENED</code>, <code>MERGED</code>, <code>REVIEWER_ASSIGNED</code>, <code>REVIEWER_UNASSIGNED</code>, <code>USER_ASSIGNED</code>, <code>USER_UNASSIGNED</code>
- GitLab: <code>CREATED</code>, <code>CLOSED</code>, <code>REOPENED</code>, <code>MERGED</code>, <code>REVIEWER_ASSIGNED</code>, <code>REVIEWER_UNASSIGNED</code>, <code>USER_ASSIGNED</code>, <code>USER_UNASSIGNED</code>, <code>WORK_LOGGED</code>
- Bitbucket: <code>CREATED</code>, <code>CLOSED</code>, <code>MERGED</code>, <code>REVIEWER_ASSIGNED</code>, <code>REVIEWER_UNASSIGNED</code>
- Azure DevOps: <code>CREATED</code>, <code>CLOSED</code>, <code>MERGED</code>, <code>REVIEWER_ASSIGNED</code>, <code>REVIEWER_UNASSIGNED</code>
- Jira: <code>CREATED</code>, <code>CLOSED</code>, <code>REOPENED</code>, <code>USER_ASSIGNED</code>, <code>USER_UNASSIGNED</code>, <code>WORK_LOGGED</code>, <code>WORKFLOW_STATUS_UPDATED</code>
- ClickUp: <code>CREATED</code>, <code>CLOSED</code>. ClickUp does not expose an events API. Keypup generates these two events based on the issue timestamps (<code>date_created</code> &amp; <code>date_closed</code>)
- Trello: <code>CREATED</code>, <code>CLOSED</code>, <code>REOPENED</code>, <code>USER_ASSIGNED</code>, <code>USER_UNASSIGNED</code>, <code>WORKFLOW_STATUS_UPDATED</code>

If a value date was specified on the event (e.g. <code>WORK_LOGGED</code>), then this date is used

Otherwise, the <a href="https://docs.keypup.io/en/articles/10064175-activity-events-created-at">Created at</a> value of the event is used

- If a value date was specified on the event (e.g. <code>WORK_LOGGED</code>), then this date is used
- Otherwise, the <a href="https://docs.keypup.io/en/articles/10064175-activity-events-created-at">Created at</a> value of the event is used

The <code>Value At</code> field is a specialized timestamp within the Activity Events dataset that provides the user-reported time for an event, which is particularly relevant for <code>WORK_LOGGED</code> activities. It allows for more accurate time-tracking reports by ensuring that effort is attributed to the correct day, even if it was logged later.

Accurate Time-Tracking Reports: This is the primary use case for this field. When you are reporting on time spent, using <code>Value At</code> instead of <code>Created At</code> ensures your data is correctly allocated.

- For example, if a developer logs their time on a Monday for work they did the previous Friday, <code>Value At</code> will point to Friday, while created_at will point to Monday. To build an accurate report of "Hours Logged per Day," you must use a time-based dimension on <code>Value At</code>, such as <code>YEAR_MONTH_DAY(value_at)</code>, and a <code>SUM(duration)</code> metric.

Correcting Historical Metrics: If you are building reports that combine time spent with other metrics, using <code>Value At</code> ensures that the effort is aligned with the correct time period. This can be crucial for accurately calculating the cost of a feature or the effort spent during a specific sprint.

Filtering by User-Reported Time: You can also use this field to filter your time-logging reports based on when the work was actually done.

- To see all time logged for work done last week, you would use a filter like <code>Value At in the previous week</code>. This is more accurate than filtering by <code>Created At</code>, which would only show when the time was entered into the system.

- Accurate Time-Tracking Reports: This is the primary use case for this field. When you are reporting on time spent, using <code>Value At</code> instead of <code>Created At</code> ensures your data is correctly allocated.
 - For example, if a developer logs their time on a Monday for work they did the previous Friday, <code>Value At</code> will point to Friday, while created_at will point to Monday. To build an accurate report of "Hours Logged per Day," you must use a time-based dimension on <code>Value At</code>, such as <code>YEAR_MONTH_DAY(value_at)</code>, and a <code>SUM(duration)</code> metric.
- Correcting Historical Metrics: If you are building reports that combine time spent with other metrics, using <code>Value At</code> ensures that the effort is aligned with the correct time period. This can be crucial for accurately calculating the cost of a feature or the effort spent during a specific sprint.
- Filtering by User-Reported Time: You can also use this field to filter your time-logging reports based on when the work was actually done.
 - To see all time logged for work done last week, you would use a filter like <code>Value At in the previous week</code>. This is more accurate than filtering by <code>Created At</code>, which would only show when the time was entered into the system.

Activity Events > Value at

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

From:
Github (Timeline Items)	N/A
Gitlab (Discussions, State Events)	Extracted from system discussion content [`WORK_LOGGED` events only]
Bitbucket (Activity)	N/A
Azure DevOps (PR Threads)	N/A
JIRA (Changelog, Worklog)	`started` [`WORK_LOGGED` events only]
ClickUp (Issue timestamps)	N/A
Trello (Actions)	N/A

Activity Events > Value at

Reporting Use Cases