Export CSV for BI
Download of raw data in CSV format, for further analysis in external BI tools.
| Field | What it does | Default value |
|---|---|---|
| Select projects | which projects are included in the export | none, a selection is required |
| From / To | the period from which data is pulled | last 30 days |
Without selecting a project, the export will not start. The date range can be changed freely, but keep in mind that a wide range on a large organization produces a file that will not open comfortably in a spreadsheet and is better fed directly into a BI tool.
File contents
One row corresponds to one event, that is a single commit or a single change in Jira or Confluence. The file contains no aggregates: summing and grouping is the job of the BI tool.
Columns, in order of appearance:
| Column | Content |
|---|---|
id | the event's identifier in Q247 |
project | the Q247 project identifier, not its name |
user | the email address of the person the event is assigned to, after alias resolution, that is the main account's address |
calories | the event's calorie score |
creationTime | timestamp in milliseconds since January 1, 1970, unformatted |
commitId | the commit identifier; empty for events from Jira and Confluence |
authorName | the author's full name from Git |
authorEmail | the author's email address from Git |
message | the commit message |
changedFiles | number of changed files |
inserts | number of inserted lines |
deletions | number of deleted lines |
File format
| Property | Value |
|---|---|
| Column separator | comma |
| Encoding | UTF-8 with a BOM marker, so Excel reads special characters correctly |
| Decimal separator | period |
| Line ending | newline character |
| File name | <project>_Bi-Export_<from>_<to>_Exported_<date and time>.csv, and with several projects the name is replaced with Multiple-Projects |
Before saving, the commit message is cleaned: newline characters, commas and quotation marks are replaced with spaces, so they do not break the row.
Data scope in the file
The export goes through some of the same rules as the dashboards, but not all of them.
The file does not include: pull request events, accounts with Untracked status, commits fully excluded by file patterns, and commits from branches excluded from the analysis. Activity from accounts with Other status is summed under a single aggregate entry.
The file does include, however, commits excluded from statistics: manually, by the visibility threshold, or by automatic classification as a cherry-pick, revert or rebase. The file has no column marking them.
Since excluded commits are in the file but not on the dashboard, the sum of Calories calculated in the BI tool will be higher than the value shown in Q247 for the same period. This is not an export bug, just a different data scope.
If a report needs to match the dashboard, base the calculations on dashboard data and treat the export as a raw source for your own analyses.
Limits
Up to 60,000 events can be exported at once. Q247 checks this number before preparing the file, so exceeding the limit ends with a message asking you to narrow the date range or select fewer projects, rather than the file being cut off halfway through.
The export works as an immediate download: the file is generated in full during the request, so for a wide range it is worth waiting instead of clicking the button again.