Engineering

# Active Developers

Count of unique individuals who were assigned to dev-items while they progressed through in development workflow statuses during the report period.

# Open Dev-Items

Number of dev-items in any open status at the end of the reporting period.

# Open Story Points

Aggregation of all story points attached to all dev-items in any open status at the end of the reporting period.

# Open Dev Items Linked Items

Number of open dev-items linked to other dev-items.

# Planned Dev Items

Showing planning and delivery status of all tasks active during the reporting period for organizations not working with sprints. Configured based on individual requirements.

Plan vs Actual % Spillover

Percentage of planned dev-items removed from the current plan. Helpful for organizations that don't use sprints.

# Quarterly Dev Items

Count of all dev-items assigned to a quarter.

# Sprint Planned Dev-Items

Count of all unique dev-items planned for inclusion in sprints during the reporting period.

# Sprint Planned Story Points

Count of all story points attached to planned dev-items for active sprints during the reporting period.

# Unplanned Dev-Items

Count of all dev-items added to sprints during the reporting period after those sprints commenced.

# Unplanned Story Points

Aggregation of all story points attached to dev-items added to sprints after they have commenced.

% Planned Dev-items

Percentage of all dev-items during the reporting period which were planned for sprints.

% Planned Story Points

Percentage of total story points during the reporting period attached to planned items.

% Unplanned Dev-items

Percentage of all dev-items which were not originally part of the sprint plan for sprints taking place during the reporting period.

% Unplanned Story Points

Percentage of all story points attached to dev-items which were not originally part of the sprint plan for sprints taking place during the reporting period.

% Planning Accuracy by Dev-Items

Percentage of planned dev-items completed during the reporting period.

% Planning Inaccuracy by Dev-Items

Percentage of planned dev-items that were not completed during the reporting period.

% Planning Delivery by Dev-items

Percentage comparison of the number of planned dev-items with all dev-items closed during the report period

% Planning Accuracy by Story Points

Percentage of story points attached to planned dev-items completed during the reporting period.

% Planning Inaccuracy by Story Points

Percentage of story points attached to planned dev-items that were not completed during the reporting period.

% Planning Delivery by Story Points

Percentage comparison of the amount of story points attached to planned dev-items with story points attached to all dev-items closed during the report period.

Avg Epic Lead Time

Average time from creation of an epic until the last child item is closed.

Dev Items Story Points Accuracy

Accuracy of original story points assigned to dev-items compared with the final story points attached. 100% indicates accurate estimation.

Feature Delivery Quality

Percentage of Story Points attached to bugs, as compared to all issue types during the reporting period.

Average Comments per PR

Average number of comments made on pull requests closed during the reporting period.

Avg Pull Request Review Cycles

Average number of review cycles a pull request goes through. A review cycle is counted when a PR has at least 1 review comment, goes back to the author for changes, and then gets reviewed again. If a PR is approved in the first review and merged, it has 0 review cycles.

Bug Cycle Time

Average time from when a bug enters an In Development workflow status until it is closed, based on bugs closed during the reporting period.

Bug Lead Time

Average time from when a bug is created until it is closed, based on bugs closed during the reporting period.

# New Bugs

Count of new bugs created during the reporting period.

# Total Open Bugs

Count of all bugs in any open status at the end of the reporting period.

# Closed Bugs

Count of all bugs closed under any status during the reporting period.

# Closed Bugs / # Total Opened Bugs

Percentage of bugs opened during the reporting period which have also been closed.

Production Bugs / Deployed Epics Ratio

Average number of production bugs created during the reporting period linked to each already deployed epic.

# Blocked Dev-Items

Number of dev-items currently in the Blocked status, or with an open item linked to it by the 'is blocked by' link type.

% Blocked Dev-Items

Percentage of all currently open dev-items which are Blocked.

Avg Blocked Dev-Items Time

Average time for dev-items to be in the blocked status.

# Blocking Dev-Items

Number of dev-items linked to another item with the 'is blocking' link type.

% Blocking Dev-Items

Percentage of all dev-items which ae blockingthe completion of other dev-items.

Avg Blocking Dev-Items Time

Average time that dev-items were blocking other items during the report period (defined by the 'is blocking' link type).

# Closed Dev-Items

Count of all dev-items which were placed in the Done status category during the reporting period (this includes statuses such as Cancelled and Won't Do).

# Closed Story Points

Aggregation of story points attached to all dev-items which were placed in the Done status category during the reporting period (this includes statuses such as Cancelled and Won't Do).

# Commits

Total number of commits made to the codebase during the report period.

# Dev-Items In Sprints

Shows all dev-items assigned to sprints, best used to breakdown work by sprint and secondary dimensions (eg: status at start or end of sprint, team or classification) to gain a holistic view of your organizations work and track trends in a variety of ways over individual sprints.

# Files Changed in Pull Requests

Number of files changed in all pull requests merged during the reporting period.

# Lines Changed in Pull Request

Aggregated total of all lines changed during pull requests merged during the reporting period.

# New Pull Requests

Count of all new pull requests created during the reporting period.

# New Story Points

Aggregation of all story points attached to new dev-items created during the reporting period.

# Open Pull Requests

Number of Pull Requests currently in any open status.

Epic / Initiative Cycle Time

Average time to complete an epic or initiative. Measured from first time a child item enters into an In Development workflow status until the last item has been moved tothe Done status category.

# Spilledover Dev-Items

Count of dev-items which were originally assigned to sprint, but not completed during that sprint and have been assigned to a later sprint for completion.

# Total Dev-Items

Count of all dev-items in any state from the creation of your organization until the end of the reporting period.

# Total Story Points

The aggregated total of story points attached to all dev-items which exist in the system at the end of the report period.

# Total Done Story Points

Aggregation of all story points attached to completed dev-items from the creation of your instance until the end of the reporting period.

# Total Pull Requests

Count of all pull requests in any state from the creation of your organization until the end of the reporting period.

% Closed Dev-Items

The percentage of dev-items closed during the report period.Useful for tracking the completion progress of Epics, Projects and Initiatives.

% Done Dev-Items

Percentage of all dev-items which have been successfully completed at the end of the report period. Note that this does not include items which are closed under statuses such as Cancelled or Won't Do.

% Epics Closed Within 28 Days

Percentage of epics active during the reporting period which were closed within 28 days of the first child item moving to an in development workflow status.

% Open Dev-Items

Percentage of all dev-items created to date which are in an open status at the end of the report period.

% Open Story Points

Percentage of all story points attached to dev-items which are in an open state at the end of the reporting period.

% Pull Requests Maturity

Measures the number of lines changed when the PR was first created in comparison to the total number of lines changed in the PR when closed. Helpful in understanding the maturity of the PR when it was created.

% Sprint Closed Dev-Items

Percentage of dev-items assigned to active sprints during the report period, which have been closed as of the end of the report period.

% Sprint Closed Story Points

Percentage of all story points assigned to sprints during the report period which are closed.

% Sprint Delivery by Dev-Items

Percentage of dev-items assigned to sprints which have been delivered by the end of sprints included in the reporting period.

% Sprint Delivery by Story Points

Comparison of all story points committed to sprint against the number of story points actually closed for active sprints during the report period.

% Total Closed Story Points

Percentage of all story points created that were closed during the report period.

% Total Done Story Points

Percentage of all story points within your organization that have been completed successfully since the creation of your instance.

Avg # Sprints Per Dev-Item

Average number of sprints a dev-item was assigned to while in any open status.

Epic Cycle Time

Average time from an epic entering an In Development workflow status until the last child item is closed.

Avg Files Changed in Pull Requests

Average number of files changed in pull requests based on pull requests merged during the reporting period.

Avg Lines Changed in Pull Requests

Average number of lines changes in pull requests based on PRs closed during the reporting period.

Avg Lines Changed Per File in a PR

Average number of lines changed in pull requests based on all pull requests closed during the report period.

# Closed Pull Requests

Count of pull requests closed during the selected date range.

Cycle Time

Average time from a dev-item entering an in development status for the first time until that item is closed. Can also be configured to calculate based on median or percentiles.

Dev-Item Velocity

Calculation of average effort for dev-items based on the average number of story points attached.

Dev-Items Status Changes

Count of dev-item status changes during the selected date range. Best practice is to display as a trend with a daily breakdown to track daily work without using the work time component.

Dev-Items Status Timing In Sprints

Average time spent in each status in sprints during taking place during the reporting period.

Dev-Items Time in Status

Shows the average amount of time for dev-items to spend in each workflow status between creation and closure. Highlights bottleneck and common delays.

Merged Pull Requests / Actual Working Days

Average number of pull requests merged per active workday (weekdays which are not public or company holidays) during the reporting period.

Dev-Items Total Status Timing In Sprints

Aggregated time spent in each status during active sprints for all dev-items during the reporting period.

New Dev-Items Average Status Timing In Sprints

Average time spent in each status during active sprints for new dev-items created in the reporting period.

New Pull Requests / Actual Working Day

Average number of new pull requests created per active workday (weekdays which are not public or company holidays) during the reporting period.

PR Merged to Deployment time

Average time from PR merge until FixVersion timestamp.

PR to Deployment time

Time from pull request creation until FixVersion time.

Pull Requests Cycle Time

Average time taken from first commit in a branch until the final merge of the pull request.

Pull requests Time in Status

Average time spent in each status for all pull requests closed during the reporting period.

Story Points In Sprints

Shows aggregation of story points attached to dev-items assigned to sprints, best used to breakdown work by sprint and secondary dimensions (eg: status at start or end of sprint, team or classification) to gain a holistic view of your organisations work and track trends in a variety of ways over individual sprints.

Time to Complete Pull Requests

Average time from the creation of a pull request until its final merge and closure.

Time To Open a Pull Request

Average time from the first commit in a branch until the creation of the first pull request for that branch.

Total Pull Requests Cycle Time

Aggregate time spent closing all pull requests which were closed during the reporting period.

# New Estimated Work Time

Aggregation of estimated work time assigned to new dev-items created during the report period.

# Planned Estimated Work Time

Aggregation of total estimated time attached to all planned dev-items for any sprints taking place in the selected date range.

# Planned Remaining Work Time

Burndown metric tracking how much aggregated estimated work time remains in the sprint for planned items.

# Planned Spent Work Time

Total time logged by developers for dev-items planned for sprints during the reporting period.

# Spent Work Time

Aggregation of total time logged working on dev-items during the reporting period.

# Spent Work Time - Done Dev-Items

Aggregation of all logged development time spent on completed work.

# Estimated Work Time - Done Dev-Items

Aggregation of estimated time attached to all dev-items completed during the reporting period.

# Spilledover Dev-Items Estimated Work Time

Aggregated amount of estimated work time attached to all spilledover dev-items across all sprints included in the report period.

# Spilledover Dev-Items Remaining Work Time

Aggregated amount of remaining work time attached to all spilledover dev-items across all sprints included in the report period.

# Total Estimated Work Time

Aggregated estimated work time for all dev-items that existed in any state at the end of the report period.

# Total Remaining Work Time

Aggregation based on the estimated work time attached to issues and amount of actual development time logged so far.

# Total Spent Work Time

Aggregated total work time logged for all dev-items in the system up to the end of the reporting period.

# Unplanned Estimated Work Time

Aggregation of all time estimations attached to dev-items added to sprints after they have started.

# Unplanned Remaining Work Time

Aggregation of all remaining time needed to complete dev-items added to sprints after they have started based on the original time estimations and logged work hours.

# Unplanned Spent Work Time

Aggregation of all developer-logged time for dev-items added to sprints after they have commenced.

% Estimated vs. Spent Work Time - Done Dev Items

Percentage comparison between estimated work time and actual work time logged in the system for successfully completed dev-items.

% Remaining vs. Estimated Work Time

Point in time metric showing the percentage of work time remaining compared to the current time estimation and calculated for the last day in the specified date range.

% Spent vs. Estimated Work Time

Percentage comparison between logged work time and estimated time for dev-items.

Support Investment

Percentage of total closed story points which were associated with support requests and tickets.

# New Support Tasks

Count of new engineering tasks created by Support channels during the reporting period.

# Closed Support Tasks

Number of support tasks closed during the reporting period.

# Total Open Support Tasks

Number of support tasks in any open status at the end of the reporting period.

% Support Tasks Overdue

Percentage of support-originated tasks which were not completed by the attached due dates.

Time to close a support task

Average time from creation of support originated tasks until they are closed.