Keypup

Dataset: Issues &amp; Pull Requests

Description: The datetime at which the pull request or issue was created.

The <code>Created At</code> field is a cornerstone for nearly all time-based analysis, marking the exact moment an issue or pull request was opened. It serves as the "start" point for the item's entire lifecycle and is fundamental for tracking workload, calculating performance metrics, and analyzing trends.

Reporting and Trend Analysis: Its most common use is as a dimension in time-series charts to track the volume of incoming work.

- By grouping data with a dimension like <code>YEAR_MONTH(created_at)</code> and using <code>COUNT()</code> as a metric, you can build a line chart that visualizes the number of new issues or pull requests created each month. This is essential for understanding team workload and for capacity planning.
- You can compare the volume of created items to closed items over the same period to monitor whether your backlog is growing or shrinking.

Calculating Lead Times and Item Age: As the definitive start time, <code>Created At</code> is the baseline for measuring how long different phases of the development process take.

- Lead Time for Changes: This critical DORA metric measures the total time from creation to completion and is calculated with the formula <code>(closed_at - created_at) / DAY()</code>.
- Time to Triage: You can measure how quickly new issues are picked up by calculating the time from creation to first assignment: <code>(assigned_at - created_at) / HOUR()</code>.
- Age of Open Items: For items that are still open, you can calculate their current age with <code>(NOW() - created_at) / DAY()</code>, which is crucial for identifying and prioritizing stale or forgotten work.

Filtering by Time: You can scope any widget to a specific creation period, which is standard practice for building relevant, time-bound reports.

- To analyze recent activity, you can apply a filter like <code>Created At in the previous 12 months</code>.
- To find potentially outdated items in your backlog, you could filter for all open issues where <code>Created At before 2 years ago</code>.

- Reporting and Trend Analysis: Its most common use is as a dimension in time-series charts to track the volume of incoming work.
 - By grouping data with a dimension like <code>YEAR_MONTH(created_at)</code> and using <code>COUNT()</code> as a metric, you can build a line chart that visualizes the number of new issues or pull requests created each month. This is essential for understanding team workload and for capacity planning.
 - You can compare the volume of created items to closed items over the same period to monitor whether your backlog is growing or shrinking.
- Calculating Lead Times and Item Age: As the definitive start time, <code>Created At</code> is the baseline for measuring how long different phases of the development process take.
 - Lead Time for Changes: This critical DORA metric measures the total time from creation to completion and is calculated with the formula <code>(closed_at - created_at) / DAY()</code>.
 - Time to Triage: You can measure how quickly new issues are picked up by calculating the time from creation to first assignment: <code>(assigned_at - created_at) / HOUR()</code>.
 - Age of Open Items: For items that are still open, you can calculate their current age with <code>(NOW() - created_at) / DAY()</code>, which is crucial for identifying and prioritizing stale or forgotten work.
- Filtering by Time: You can scope any widget to a specific creation period, which is standard practice for building relevant, time-bound reports.
 - To analyze recent activity, you can apply a filter like <code>Created At in the previous 12 months</code>.
 - To find potentially outdated items in your backlog, you could filter for all open issues where <code>Created At before 2 years ago</code>.

Issues and PRs > Created 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 (PRs, Issues)	`created_at`
Gitlab (PRs, Issues)	`created_at`
Bitbucket (PRs)	`created_on`
Azure DevOps (PRs, Issues)	`creationDate`
JIRA (Issues)	`created`
ClickUp (Issues)	`date_created`
Trello (Issues)	`created_at`

Issues and PRs > Created at

Reporting Use Cases