# Waydev Documentation

> Waydev's Documentation

## Guides
- [Welcome to Waydev](https://docs.waydev.co/docs/about-us.md)
- [Configuring Waydev](https://docs.waydev.co/docs/configuring-waydev.md): All steps needed to get the most out of Waydev.
- [Set up Repositories](https://docs.waydev.co/docs/setup-repositories.md)
- [Set up Ticket Projects](https://docs.waydev.co/docs/setup-ticket-projects.md): Configure your ticket projects to ensure that you'll have accurate and real-time data regarding your boards.
- [Set up Contributors](https://docs.waydev.co/docs/setup-contributors.md)
- [Merge Profiles](https://docs.waydev.co/docs/merge-contributor-profiles.md): How to merge duplicate contributor profiles.
- [Include new organization's contributors](https://docs.waydev.co/docs/include-new-organization-contributors.md)
- [Set up Teams](https://docs.waydev.co/docs/setup-teams.md)
- [Set up Groups](https://docs.waydev.co/docs/setup-groups.md): Project, group, initiative, workspace.
- [Set up DORA Metrics](https://docs.waydev.co/docs/setup-dora-metrics.md)
- [Set up Operational Users](https://docs.waydev.co/docs/setup-operational-users.md): The setup page for managing users and roles.
- [Invite new Users](https://docs.waydev.co/docs/invite-new-users.md): The Operational Users page is where you manage all users
- [Manage User Roles](https://docs.waydev.co/docs/manage-user-roles.md): The Operational Users page is where you manage all users
- [Set up Cost Capitalization](https://docs.waydev.co/docs/setup-cost-capitalization.md): In order to calculate the Cost Capitalization, Waydev requires to set up capitalizable tickets. Below is a guide on setting this up!
- [Set up Custom Metrics](https://docs.waydev.co/docs/setup-custom-metrics.md)
- [Missing data?](https://docs.waydev.co/docs/missing-data.md): What to do in case of missing data in your Waydev account. Here are a few steps that you should check if you notice there is missing data in your account.
- [Missing commits](https://docs.waydev.co/docs/missing-commits.md)
- [Missing Pull Requests](https://docs.waydev.co/docs/missing-pull-requests.md)
- [Missing tickets](https://docs.waydev.co/docs/missing-tickets.md)
- [Missing contributors](https://docs.waydev.co/docs/missing-contributors.md)
- [Missing repositories](https://docs.waydev.co/docs/missing-repositories.md)
- [Missing ticket projects](https://docs.waydev.co/docs/missing-ticket-projects.md)
- [Waydev Metrics](https://docs.waydev.co/docs/waydev-metrics.md)
- [Active Days](https://docs.waydev.co/docs/active-days.md): Number of days with any activity from contributors.
- [Active Weeks](https://docs.waydev.co/docs/active-weeks.md): Represents the number of weeks in which any activity occurred (commits, pull requests, tickets).
- [Coding Weeks](https://docs.waydev.co/docs/coding-weeks.md): Represents the number of weeks in which code was committed by any member of the team during the specified time period.
- [Commits](https://docs.waydev.co/docs/commits.md): Number of code commits made by contributors.
- [Collaborative Commits](https://docs.waydev.co/docs/collaborative-commits.md): Number of commits to a repository involving more than one contributor.
- [Coding Days](https://docs.waydev.co/docs/coding-days.md): Number of days with contributor code commits.
- [Commits/Day (commits)](https://docs.waydev.co/docs/commits-per-day.md): Number of code commits made by contributors per days with contributor code commits.
- [Total Pull Requests](https://docs.waydev.co/docs/total-pull-requests.md): The total number of Pull Requests.
- [Throughput (LoC)](https://docs.waydev.co/docs/throughput-loc.md): Total lines of new, churn, help and refactored code.
- [Productive Throughput (LoC)](https://docs.waydev.co/docs/productive-throughput-loc.md): Total lines of new, help and refactored code.
- [Collaborative Throughput](https://docs.waydev.co/docs/collaborative-throughput.md): Total lines affected in code commits in which contributor participated in but is not the main author.
- [Low Risk Commits](https://docs.waydev.co/docs/low-risk-commits.md): Risk is a measure of how likely a commit is to cause problems (code quality/stability). It is calculated based on the size of the commit, how the changes are spread across the code base, and how serious the changes are.
- [Medium Risk Commits](https://docs.waydev.co/docs/medium-risk-commits.md): Risk is a measure of how likely a commit is to cause problems (code quality/stability). It is calculated based on the size of the commit, how the changes are spread across the code base, and how serious the changes are.
- [High Risk Commits](https://docs.waydev.co/docs/high-risk-commits.md): Risk is a measure of how likely a commit is to cause problems (code quality/stability). It is calculated based on the size of the commit, how the changes are spread across the code base, and how serious the changes are.
- [Efficiency](https://docs.waydev.co/docs/efficiency.md): The percentage of productive code(New Work, Help and Refactor), independent of the amount of code written. The higher the efficiency rate, the longer the code provides business value.
- [Weekly Coding Days](https://docs.waydev.co/docs/weekly-coding-days.md): Number of days within a given week that an individual or team dedicates to writing code and push commits.
- [Weekly Active Days](https://docs.waydev.co/docs/weekly-active-days.md): Number of days within a given week that an individual or team dedicates to engineering work like writing code, reviewing other's work, discuss architecture and push commits.
- [Avg. Weekly Coding Days](https://docs.waydev.co/docs/avg-weekly-coding-days.md): Average number of days per week that an individual or team dedicates to writing code and push commits.
- [Avg. Weekly Active Days](https://docs.waydev.co/docs/avg-weekly-active-days.md): Average number of days within a given week that an individual or team dedicates to engineering work like writing code, reviewing other's work, discuss architecture and push commits.
- [Technical Debt (%)](https://docs.waydev.co/docs/technical-debt.md): Amount of refactoring code commited. Represents the volume of code modifications aimed at improving internal structure, readability, or maintainability, without altering the external behavior of the software.
- [New Work (LoC)](https://docs.waydev.co/docs/new-work-loc.md): Total lines of code added to the code base (without replacing old code).
- [New Work (%)](https://docs.waydev.co/docs/new-work.md): Percentage of new lines of code reported to total (new, churn, help and refactored).
- [Refactor (LoC)](https://docs.waydev.co/docs/refactor-loc.md): Total lines of code restructured to improve readability, design, or reduce technical debt.
- [Refactor (%)](https://docs.waydev.co/docs/refactor.md): Percentage of refactored lines of code reported to total (new, churn, help and refactored).
- [Help (LoC)](https://docs.waydev.co/docs/help-loc.md): Total number of code lines authored with the intent to support or enable other contributors.
- [Help (%)](https://docs.waydev.co/docs/help.md): Percentage of help lines of code reported to total (new, churn, help and refactored).
- [Churn (LoC)](https://docs.waydev.co/docs/churn-loc.md): Total number of lines of code that were added and subsequently removed or modified within a short time frame.
- [Churn (%)](https://docs.waydev.co/docs/churn.md): Percentage of churn lines of code reported to total (new, churn, help and refactored).
- [Commits Score](https://docs.waydev.co/docs/commits-score.md): Sum of code commits score. The commit score provides a single metric that rewards meaningful contributions, penalises risky changes, helps identify high-quality vs. problematic commits, balances quantity (impact) with quality (risk).
- [tt100](https://docs.waydev.co/docs/tt100.md): TT100 represents the time it takes for a contributor to create 100 productive lines of code (without churn).
- [Work Type](https://docs.waydev.co/docs/work-type.md): Represents the highest types of work an engineer is focused on (New Work, Legacy Refactor, Help Others, and Churn).
- [Merged PRs](https://docs.waydev.co/docs/merged-prs.md): Total Merged Pull Requests is a count metric that measures the number of pull requests that were successfully merged into the main codebase in a given time period.
- [Total Pull Requests Merged Without Review](https://docs.waydev.co/docs/total-pull-requests-merged-without-review.md): Total Pull Requests Merged Without Review is a count metric that measures the number of pull requests that were merged without undergoing the required code review process.
- [Total Closed Pull Requests](https://docs.waydev.co/docs/total-closed-pull-requests.md): Total Closed Pull Requests is a count metric that measures the number of pull requests that were closed without being merged in the project management system.
- [Total Open Pull Requests](https://docs.waydev.co/docs/total-open-pull-requests.md): Total Open Pull Requests is a count metric that measures the number of pull requests that are currently open and awaiting review, approval, or completion in the project management system.
- [Total Failed Pull Requests](https://docs.waydev.co/docs/total-failed-pull-requests.md): Tracks the total number of pull requests that failed during the specified time period.
- [Total Pull Requests Commented](https://docs.waydev.co/docs/total-pull-requests-commented.md): Tracks the total number of pull requests(created by the contributor or team) that received comments during the specified time period.
- [Reviews received (reviews)](https://docs.waydev.co/docs/reviews-received.md): Tracks the total number of pull request reviews performed during the specified time period.
- [Total Pull Requests Reviewed](https://docs.waydev.co/docs/total-pull-requests-reviewed.md): The total number of pull requests(created by the contributor or team) that received at least one review during the specified time period.
- [Total Pull Requests Without Reviews](https://docs.waydev.co/docs/total-pull-requests-without-reviews.md): The number of pull requests that were merged or closed without receiving any code reviews from other team members.
- [Total Pull Requests Without Comments](https://docs.waydev.co/docs/total-pull-requests-without-comments.md): This metric counts how many pull requests (code changes) received no comments or feedback from reviewers during the development process.
- [Total Pull Requests Merged Without Rebase](https://docs.waydev.co/docs/total-pull-requests-merged-without-rebase.md): This metric counts how many pull requests were merged into the main codebase without first being cleaned up or reorganized to match the current state of the main code.
- [Comments received (comments)](https://docs.waydev.co/docs/comments-received.md): The total number of comments left on pull requests (created by the contributor or team) during a specific time period. *Some providers may mark comments left by assigned reviewers as **reviews**, not comments (e.g. GitHub).
- [PRs Merged and Commented](https://docs.waydev.co/docs/prs-merged-and-commented.md): The number of pull requests that were both successfully merged into the main codebase AND received comments during the review process.
- [PR Failure Rate (%)](https://docs.waydev.co/docs/pr-failure-rate.md): The percentage of pull requests that failed during a specific time period.
- [Pull Requests Active Days](https://docs.waydev.co/docs/pull-requests-active-days.md): The number of unique days during a time period when pull requests were actively being worked on (created, reviewed, or merged).
- [Total Time: PRs Create → Merge](https://docs.waydev.co/docs/total-time-prs-create-merge.md): The total amount of time (in seconds) that all pull requests took from when they were first created until they were successfully merged into the main codebase.
- [Total Time: PRs First Review → Merge](https://docs.waydev.co/docs/total-time-prs-first-review-merge.md): The total amount of time (in seconds) that all pull requests took from when they received their first review until they were successfully merged into the main codebase.
- [Total Time: PRs Create → Review](https://docs.waydev.co/docs/total-time-prs-create-review.md): The total amount of time (in seconds) that all pull requests waited from when they were first submitted until someone provided the first review or feedback.
- [Total Time: PRs Create → Comment](https://docs.waydev.co/docs/total-time-prs-create-comment.md): The total amount of time (in seconds) that all pull requests took from when they were first created until someone left the very first comment on them.
- [Total Time: PRs Merge → Deploy](https://docs.waydev.co/docs/total-time-prs-merge-deploy.md): The total amount of time (in seconds) that all pull requests took from when they were successfully merged into the main codebase until they were deployed to production (live environment where users can access the changes).
- [Total Time: PRs Comment → Merge](https://docs.waydev.co/docs/total-time-prs-comment-merge.md): The total amount of time (in seconds) that all pull requests took from when the first comment was made on them until they were successfully merged into the main codebase.
- [Total Time: PRs Commit → Merge](https://docs.waydev.co/docs/total-time-prs-commit-merge.md): The total amount of time (in seconds) that all pull requests took from when the first code change was made until the pull request was successfully merged into the main codebase.
- [Total Time: Commit → PRs Create](https://docs.waydev.co/docs/total-time-commit-prs-create.md): The total amount of time (in seconds) that developers spent working on code changes before creating pull requests. It measures the time from when a developer first started making changes (first commit) until they felt the changes were ready for review (pull request creation).
- [Lead Time for Changes](https://docs.waydev.co/docs/lead-time-for-changes.md): The total time (in seconds) it takes for a code change to go from the first commit to being successfully deployed to production. It's like measuring how long it takes for a product idea to go from concept to being available to customers.
- [Follow-On Commits](https://docs.waydev.co/docs/follow-on-commits.md): The total number of additional commits that were made to fix issues or make improvements after a pull request was initially created.
- [Total Thoroughly Reviewed PRs](https://docs.waydev.co/docs/total-thoroughly-reviewed-pull-requests.md): The total number of pull requests (created by the contributor or team) that received thorough, meaningful reviews rather than just quick approvals or rubber-stamp reviews.
- [Total Rubber-Stamped PRs](https://docs.waydev.co/docs/total-rubber-stamped-pull-requests.md): The total number of pull requests that were approved with minimal or no meaningful review - essentially "rubber stamped" through the approval process.
- [Total Iterated PRs](https://docs.waydev.co/docs/total-iterated-pull-requests.md): The total number of pull requests that went through multiple rounds of review and revision before being finally merged.
- [Total Time: PRs Iterations](https://docs.waydev.co/docs/total-time-prs-iterations.md): The total amount of time (in seconds) that all pull requests spent in "iteration cycles" - the back-and-forth process between developers and reviewers when changes are requested, made, and re-reviewed.
- [Total Reviewer Comments](https://docs.waydev.co/docs/total-reviewer-comments.md): The total number of comments made by reviewers across all pull requests(opened by the contributor or team) during the specified time period.
- [Pull Requests Impact](https://docs.waydev.co/docs/pull-requests-impact.md): A composite score that evaluates how impactful pull request activity has been during a specific time period, considering factors like the number of active days, number of contributors, and the overall pull request score.
- [Impact](https://docs.waydev.co/docs/impact.md): A composite score that represents the overall effectiveness and productivity of development work across all activities (code commits, pull requests, and other development tasks) during a specific time period.
- [Code Impact](https://docs.waydev.co/docs/code-impact.md): Code Impact is a way of measuring the significance of code changes, with respect to the nuances of software engineering.
- [Avg. to first comment](https://docs.waydev.co/docs/avg-to-first-comment.md): The average amount of time it takes for someone to leave the first comment on a pull request after it's created.
- [Avg. to first review](https://docs.waydev.co/docs/avg-to-first-review.md): The average amount of time it takes for a pull request to receive its first review after being created.
- [Avg. to merge from create](https://docs.waydev.co/docs/avg-to-merge-from-create.md): The average amount of time it takes for a pull request to go from creation to successful merge across all pull requests in a given time period.
- [Avg. to merge from first commit](https://docs.waydev.co/docs/avg-to-merge-from-first-commit.md): The average amount of time it takes for a pull request to be merged, starting from when the first code change (commit) was made, rather than when the pull request was officially created.
- [Avg. to merge from first comment](https://docs.waydev.co/docs/avg-to-merge-from-first-comment.md): The average amount of time it takes for a pull request to be merged after receiving its first comment from a reviewer.
- [Avg. to merge from first review](https://docs.waydev.co/docs/avg-to-merge-from-first-review.md): The average amount of time (in seconds) that pull requests take from when they receive their first review until they are successfully merged into the main codebase.
- [Avg. to issue PR](https://docs.waydev.co/docs/avg-to-issue-pr.md): The average amount of time it takes for developers to create a pull request after they make their first code change (commit) in a feature branch.
- [Avg. from merge to deploy](https://docs.waydev.co/docs/avg-from-merge-to-deploy.md): The average amount of time it takes for code changes to go from being merged into the main codebase to being deployed to production (where users can actually use the new features).
- [Avg. comments/PR](https://docs.waydev.co/docs/avg-comments-pr.md): The average number of comments received on each pull request(created by the contributor or team) during the review process.
- [Knowledge Sharing Index](https://docs.waydev.co/docs/knowledge-sharing-index.md): Indicates how well knowledge is shared across the development team through code reviews. It measures the diversity and distribution of review participation.
- [Reviewer Comments per PR](https://docs.waydev.co/docs/reviewer-comments-per-pr.md): The average number of comments that reviewers leave on each pull request(created by the contributor or team) during the code review process.
- [Thoroughly Reviewed PRs %](https://docs.waydev.co/docs/thoroughly-reviewed-prs.md): The percentage of pull requests (created by the contributor or team) that received thorough, high-quality reviews rather than just quick approvals or rubber-stamp reviews.
- [Rubber-Stamped PRs %](https://docs.waydev.co/docs/rubber-stamped-prs.md): The percentage of pull requests that were "rubber stamped" - meaning they received very quick, superficial reviews that likely didn't provide meaningful feedback or catch potential issues.
- [Unreviewed PRs (%)](https://docs.waydev.co/docs/unreviewd-prs.md): The percentage of pull requests that were merged into the main codebase without receiving any code reviews from other team members.
- [Iterated PRs](https://docs.waydev.co/docs/iterated-prs.md): The percentage of pull requests that required multiple rounds of changes and reviews before being approved and merged.
- [Avg. PR Iteration Time](https://docs.waydev.co/docs/avg-pr-iteration-time.md): The average amount of time (in seconds) that pull requests spend in "iteration cycles" - the back-and-forth process between developers and reviewers when changes are requested and implemented.
- [Avg. PR Size (LoC)](https://docs.waydev.co/docs/avg-pr-size-loc.md): The average number of lines of code changed across all pull requests in a given time period.
- [Total Time: Incidents → Recovery](https://docs.waydev.co/docs/total-time-incidents-recovery.md): Total Time to Recovery is a cumulative metric that measures the total time spent recovering from incidents across all incidents in a given time period.
- [Total Deployments](https://docs.waydev.co/docs/total-deployments.md): Total Deployments is a count metric that measures the number of successful releases/deployments in a given time period across selected repositories.
- [Deployment Frequency (per day)](https://docs.waydev.co/docs/deployment-frequency-per-day.md): Deployment Frequency is a key DORA metric that measures how often code is deployed to production (or another target environment) within a given time period.
- [Failed Deployments](https://docs.waydev.co/docs/failed-deployments.md): Failed Deployments is a count metric that measures the number of deployments that resulted in incidents or failures in a given time period.
- [Change Failure Rate](https://docs.waydev.co/docs/change-failure-rate.md): Change Failure Rate is a percentage-based metric that measures the proportion of deployments that result in failures or incidents in a given time period.
- [Number of Incidents](https://docs.waydev.co/docs/number-of-incidents.md): Number of Incidents is a count metric that measures the total number of incidents that occurred in a given time period across selected repositories.
- [Mean Time To Recovery](https://docs.waydev.co/docs/mean-time-to-recovery.md): Mean Time to Recovery (MTTR) is an average metric that measures the average time it takes to recover from incidents in a given time period.
- [Touched Tickets](https://docs.waydev.co/docs/touched-tickets.md): Touched Tickets is a count metric that measures the total number of tickets that were touched or interacted with in a given time period across selected project management (PM) projects.
- [Created Tickets](https://docs.waydev.co/docs/created-tickets.md): This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the Created stage of the development process.
- [Tickets in Backlog](https://docs.waydev.co/docs/tickets-in-backlog.md): This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the Backlog stage of the development process.
- [Tickets in ToDo](https://docs.waydev.co/docs/tickets-in-todo.md): This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the ToDo stage of the development process.
- [Tickets in Development](https://docs.waydev.co/docs/tickets-in-development.md): This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the Development stage of the development process.
- [Tickets in QA](https://docs.waydev.co/docs/tickets-in-qa.md): This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the Development stage of the development process.
- [Resolved Tickets](https://docs.waydev.co/docs/resolved-tickets.md): This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the Resolved stage of the development process.
- [Active Tickets](https://docs.waydev.co/docs/active-tickets.md): This metric tracks tickets based on their state/category in the project management workflow. The metric represents tickets in the Active stage of the development process.
- [Created Bug Tickets](https://docs.waydev.co/docs/created-bug-tickets.md): This metric tracks bug tickets based on their state/category in the project management workflow. It represents bug tickets in the Created stage of the development process.
- [Bug Tickets in Backlog](https://docs.waydev.co/docs/bug-tickets-in-backlog.md): This metric tracks bug tickets based on their state/category in the project management workflow. It represents bug tickets in the Backlog stage of the development process.
- [Bug Tickets in ToDo](https://docs.waydev.co/docs/bug-tickets-in-todo.md): This metric tracks bug tickets based on their state/category in the project management workflow. The metric represents bug tickets in the ToDo stage of the development process.
- [Bug Tickets in Development](https://docs.waydev.co/docs/bug-tickets-in-development.md): This metric tracks bug tickets based on their state/category in the project management workflow. The metric represents bug tickets in the Development stage of the development process.
- [Bug Tickets in QA](https://docs.waydev.co/docs/bug-tickets-in-qa.md): This metric tracks bug tickets based on their state/category in the project management workflow. The metric represents bug tickets in the QA stage of the development process.
- [Resolved Bug Tickets](https://docs.waydev.co/docs/resolved-bug-tickets.md): This metric tracks bug tickets based on their state/category in the project management workflow. The metric represents bug tickets in the Resolved stage of the development process.
- [Active Bug Tickets](https://docs.waydev.co/docs/active-bug-tickets.md): This metric tracks bug tickets based on their state/category in the project management workflow. The metric represents bug tickets in the Resolved stage of the development process.
- [Assigned tickets](https://docs.waydev.co/docs/assigned-tickets.md): This metric tracks tickets assigned to a specific developer in the project management system.
- [Unassigned Tickets](https://docs.waydev.co/docs/unassigned-tickets.md): This metric tracks tickets that remain unassigned in the project management system.
- [Planned Tickets](https://docs.waydev.co/docs/planned-tickets.md): This metrics tracks tickets were planned in advance (part of sprint/iteration planning).
- [Unplanned Tickets](https://docs.waydev.co/docs/unplanned-tickets.md): This metric tracks unplanned tickets (emergency work, bugs, or ad-hoc requests).
- [Tracked Tickets](https://docs.waydev.co/docs/tracked-tickets.md): This metric distinguishes between tickets that are explicitly tracked in the project management system and those that are not tracked (work done outside the formal tracking system).
- [Untracked Tickets](https://docs.waydev.co/docs/untracked-tickets.md): This metric distinguishes between tickets that are explicitly tracked in the project management system and those that are not tracked (work done outside the formal tracking system).
- [Estimated Tickets](https://docs.waydev.co/docs/estimated-tickets.md): This metric tracks tickets that have been assigned story points (estimated).
- [Unestimated Tickets](https://docs.waydev.co/docs/unestimated-tickets.md): This metric tracks tickets that lack story points (unestimated) in the project management system.
- [Epicless Tickets](https://docs.waydev.co/docs/epicless-tickets.md): Epicless Tickets is a count metric that measures the number of tickets that are not associated with any epic in the project management system.
- [Unlinked Tickets](https://docs.waydev.co/docs/unlinked-tickets.md): Unlinked Tickets is a count metric that measures the number of tickets that have no associated Git activity (commits or pull requests) in the project management system.
- [Stalled Tickets](https://docs.waydev.co/docs/stalled-tickets.md): Stalled Tickets is a count metric that measures the number of tickets that have been inactive for an extended period and are considered "stalled" in the project management system.
- [Stuck Tickets](https://docs.waydev.co/docs/stuck-tickets.md): Stuck Tickets is a count metric that measures the number of tickets that are blocked or impeded from progressing due to specific issues or dependencies in the project management system.
- [Subtask Tickets](https://docs.waydev.co/docs/subtask-tickets.md): Subtask Tickets is a count metric that measures the number of subtasks associated with tickets in the project management system.
- [Story Points Touched](https://docs.waydev.co/docs/story-points-touched.md): Story Points Total is a cumulative metric that measures the total sum of all story points across all estimated tickets in the project management system.
- [Story Points Created](https://docs.waydev.co/docs/story-points-created.md): This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Created stage of the development process.
- [Story Points in Backlog](https://docs.waydev.co/docs/story-points-in-backlog.md): This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Backlog stage of the development process.
- [Story Points in ToDo](https://docs.waydev.co/docs/story-points-in-todo.md): This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the ToDo stage of the development process.
- [Story Points in Development](https://docs.waydev.co/docs/story-points-in-development.md): This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Development stage of the process.
- [Story Points in QA](https://docs.waydev.co/docs/story-points-in-qa.md): This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the QA stage of the development process.
- [Story Points Resolved](https://docs.waydev.co/docs/story-points-resolved.md): This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Resolved stage of the development process.
- [Story Points Bug Created](https://docs.waydev.co/docs/story-points-bug-created.md): This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the Created stage of the development process.
- [Story Points Bug in Backlog](https://docs.waydev.co/docs/story-points-bug-in-backlog.md): This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the Backlog stage of the development process.
- [Story Points Bug in ToDo](https://docs.waydev.co/docs/story-points-bug-in-todo.md): This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the ToDO stage of the development process.
- [Story Points Bug in Development](https://docs.waydev.co/docs/story-points-bug-in-development.md): This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the Development stage of the process.
- [Story Points Bug in QA](https://docs.waydev.co/docs/story-points-bug-in-qa.md): This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the QA stage of the development process.
- [Story Points Bug Resolved](https://docs.waydev.co/docs/story-points-bug-resolved.md): This metric tracks story points on estimated bug tickets based on their state/category in the project management workflow. The metric represents story points for bug tickets in the Resolved stage of the development process.
- [Story Points Active](https://docs.waydev.co/docs/story-points-active.md): This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Active stage of the development process.
- [Story Points Bug Active](https://docs.waydev.co/docs/story-points-bug-active.md): This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Active stage of the development process.
- [Planned Story Points](https://docs.waydev.co/docs/planned-story-points.md): This metric tracks story points on estimated tickets based on their state/category in the project management workflow. The metric represents story points for tickets in the Active stage of the development process.
- [Unplanned Story Points](https://docs.waydev.co/docs/unplanned-story-points.md): These metrics track story points that were not planned in advance (emergency work, ad-hoc requests) in the project management system.
- [Tracked Story Points](https://docs.waydev.co/docs/tracked-story-points.md): These metrics track story points that were not planned in advance (emergency work, ad-hoc requests) in the project management system.
- [Story Points per Tracked Tickets](https://docs.waydev.co/docs/story-points-per-tracked-tickets.md): Story Points Per Tracked Tickets is an average metric that measures the average number of story points per tracked ticket in the project management system.
- [Traceable Pull Requests](https://docs.waydev.co/docs/traceable-pull-requests.md): Represents the number of pull requests that are linked to tickets or issues in the project management system. These metrics show if work is properly tracked and documented.
- [Untraceable Pull Requests](https://docs.waydev.co/docs/untraceable-pull-requests.md): Represents the number of pull requests that are not linked to tickets or issues in the project management system. These metrics show if work is properly tracked and documented.
- [Traceability](https://docs.waydev.co/docs/traceability.md): Indicates the percentage of pull requests that are linked to at least one ticket.
- [Industry Benchmarks](https://docs.waydev.co/docs/industry-benchmarks.md): Compare your teams' averages with the industry averages.
- [User Guides](https://docs.waydev.co/docs/waydev-user-guides.md): Resources for your Waydev users.
- [Role Guidelines](https://docs.waydev.co/docs/waydev-role-guidelines.md): Review the useful features based on the user role.
- [Guide for Owners](https://docs.waydev.co/docs/guide-for-owners.md): Manage your Organization in Waydev
- [Guide for Leader & Executive](https://docs.waydev.co/docs/guide-for-leader-executive.md): Your Guide to Waydev Metrics and Reports
- [Guide for Scrum Master & Manager](https://docs.waydev.co/docs/guide-for-scrum-master-manager.md): Your Guide to Waydev Metrics and Reports
- [Guide for Individual Contributor & Engineer](https://docs.waydev.co/docs/guide-for-individual-contributor-engineer.md)
- [Use Cases](https://docs.waydev.co/docs/waydev-use-cases.md): Accomplish different reporting goals using Waydev.
- [Understand Engineering Throughput](https://docs.waydev.co/docs/understand-engineering-throughput.md): Use Case. Share it with the roles that have interest in that.
- [Identify Bottlenecks in the Development Lifecycle](https://docs.waydev.co/docs/identify-bottlenecks-in-the-development-lifecycle.md): Use Case. Share it with the roles that have interest in that.
- [Track Sprint Execution and Delivery Predictability](https://docs.waydev.co/docs/track-sprint-execution-and-delivery-predictability.md): Use Case. Share it with the roles that have interest in that.
- [Monitor Team Collaboration and Code Review Quality](https://docs.waydev.co/docs/monitor-team-collaboration-and-code-review-quality.md): Use Case. Share it with the roles that have interest in that.
- [Understand Team Workload Distribution](https://docs.waydev.co/docs/understand-team-workload-distribution.md): Use Case. Share it with the roles that have interest in that.
- [Onboard New Engineers More Effectively](https://docs.waydev.co/docs/onboard-new-engineers-more-effectively.md): Use Case. Share it with the roles that have interest in that.
- [Detect and Address Personal Workflow Inefficiencies](https://docs.waydev.co/docs/detect-and-address-personal-workflow-inefficiencies.md): Use Case. Share it with the roles that have interest in that.
- [Improve Code Review Participation and Responsiveness](https://docs.waydev.co/docs/improve-code-review-participation-and-responsiveness.md): Use Case. Share it with the roles that have interest in that.
- [Understand Personal Contribution Trends](https://docs.waydev.co/docs/understand-personal-contribution-trends.md): Use Case. Share it with the roles that have interest in that.
- [Monitor Engineering Health Over Time](https://docs.waydev.co/docs/monitor-engineering-health-over-time.md): Use Case. Share it with the roles that have interest in that.
- [Benchmark Teams and Projects Across the Organization](https://docs.waydev.co/docs/benchmark-teams-and-projects-across-the-organization.md): Use Case. Share it with the roles that have interest in that.
- [Evaluate ROI of Engineering Teams](https://docs.waydev.co/docs/evaluate-roi-of-engineering-teams.md): Use Case. Share it with the roles that have interest in that.
- [Gain Insight Into the Impact of Their Work](https://docs.waydev.co/docs/gain-insight-into-the-impact-of-their-work.md): Use Case. Share it with the roles that have interest in that.
- [Advocate for Career Growth with Data](https://docs.waydev.co/docs/advocate-for-career-growth-with-data.md): Use Case. Share it with the roles that have interest in that.
- [Waydev Core 4](https://docs.waydev.co/docs/waydev-core-4.md): Waydev CORE 4 is available on the platform's launch page.
- [Waydev Modules](https://docs.waydev.co/docs/waydev-modules.md): Start leveraging all our capabilities.
- [Delivery](https://docs.waydev.co/docs/delivery-module.md): The delivery section provides you with the best tools to ship and deploy your solution faster.
- [DORA Metrics](https://docs.waydev.co/docs/dora-metrics.md): A Google research group has identified four key metrics that indicate the health and performance of software engineering teams - DORA Metrics. The DORA Metrics have become an industry standard for how effectively organizations deliver software.
- [Pull Request Insights](https://docs.waydev.co/docs/pr-insights.md): Identify the bottlenecks in your Pull Request cycles over the course of the sprint. Find outliers, and visualize high-level team dynamics and the underlying activities that can contribute to those dynamics.
- [Sprints Commitment](https://docs.waydev.co/docs/sprints-commitment.md): Get a clear summary of your sprint with our Sprint Commitment Report! Track and analyze the ticket activity in your teams and identify any bottlenecks.
- [Merge Quality](https://docs.waydev.co/docs/merge-quality.md): Gain deeper insights into your team’s review process with our Merge Quality feature
- [Velocity Report](https://docs.waydev.co/docs/sprints.md): Keep a pulse on your sprint progress. Visualize and mitigate sprint risk using our forecast model. Identify capacity issues and scope creep.
- [Health](https://docs.waydev.co/docs/health-module.md): The activity section provides you with a birds-eye view for you to optimise your engineering teams
- [Bird’s-eye view](https://docs.waydev.co/docs/birds-eye-view.md): Bird’s-eye view provides a quick-to-read visual summary of your group's and team's performance, making complex data comprehensible.
- [Insights](https://docs.waydev.co/docs/insights.md): The Insights dashboard provides a comprehensive summary of your company and projects' recent activities, enabling you to understand progress better.
- [Team Insights](https://docs.waydev.co/docs/team-insights.md)
- [Benchmark](https://docs.waydev.co/docs/benchmark.md)
- [Developer Experience (DX)](https://docs.waydev.co/docs/developer-experience.md): DX through surveys ingested in Waydev
- [Planning](https://docs.waydev.co/docs/planning-module.md): The Throughput section keeps you in touch with the progress of your engineering teams and your projects.
- [Resource Allocation](https://docs.waydev.co/docs/resource-allocation.md): Get a better understanding of how well engineering resources are allocated, visualize financial costs, and have more control over the progress of key initiatives.
- [Project Costs](https://docs.waydev.co/docs/project-costs.md): Accelerate innovation and maximize business impact.
- [Cost Capitalization](https://docs.waydev.co/docs/cost-capitalization.md): Capitalize software development work based on flexible rules that you set up. Generate and export reports to track effort and expenses effortlessly.
- [Diagnose](https://docs.waydev.co/docs/diagnose.md): The newest module in Waydev.
- [Hygiene](https://docs.waydev.co/docs/hygiene.md): Overview of all the linked and unlinked PRs for all the active repositories
- [AI Predictability](https://docs.waydev.co/docs/ai-predictability.md)
- [AI Adoption](https://docs.waydev.co/docs/ai-adoption.md): Measure the AI adoption in your company by seeing how many contributors are actively using AI Coding tools.
- [Studio](https://docs.waydev.co/docs/studio-module.md)
- [Custom Metrics](https://docs.waydev.co/docs/custom-metrics-how-to.md)
- [Custom Reports](https://docs.waydev.co/docs/reports.md): The Reports feature enables the creation of custom, complex reports using any Waydev metric.  Designed for extensive datasets, it offers scalability for in-depth analysis of engineering performance
- [Dashboards](https://docs.waydev.co/docs/custom-dashboards.md): Waydev's custom dashboards feature helps you create dashboards tailored to your needs.
- [Waydev API](https://docs.waydev.co/docs/waydev-api.md): Info regarding Waydev's API
- [Custom Targets](https://docs.waydev.co/docs/targets.md): Set targets within Waydev, so you can keep track of your team’s progress.
- [Notifications](https://docs.waydev.co/docs/notifications.md): Learn how to configure your Notifications
- [Usage Analytics](https://docs.waydev.co/docs/usage-analytics-feature.md): Track and analyze user engagement with Waydev's Usage Analytics feature. Monitor login frequency, user activity patterns, and platform usage across your organization.
- [Supported Tool Stack](https://docs.waydev.co/docs/supported-integrations.md): All tools that you can connect with Waydev.
- [Code](https://docs.waydev.co/docs/code.md)
- [GitHub](https://docs.waydev.co/docs/github.md)
- [GitHub Enterprise](https://docs.waydev.co/docs/github-enterprise.md)
- [Bitbucket](https://docs.waydev.co/docs/bitbucket.md)
- [Bitbucket Server](https://docs.waydev.co/docs/bitbucket-server.md)
- [GitLab](https://docs.waydev.co/docs/gitlab.md)
- [GitLab Self-Hosted](https://docs.waydev.co/docs/gitlab-self-hosted.md)
- [Azure DevOps](https://docs.waydev.co/docs/azure-devops.md)
- [Azure DevOps Server](https://docs.waydev.co/docs/azure-devops-server.md)
- [AWS CodeCommit](https://docs.waydev.co/docs/aws-codecommit.md)
- [Gerrit](https://docs.waydev.co/docs/gerrit.md)
- [Ticketing](https://docs.waydev.co/docs/ticket-integration.md)
- [Jira](https://docs.waydev.co/docs/jira.md)
- [Jira Server](https://docs.waydev.co/docs/jira-server.md)
- [Azure Boards](https://docs.waydev.co/docs/azure-boards.md)
- [Azure Boards Server](https://docs.waydev.co/docs/azure-boards-server.md)
- [ClickUp](https://docs.waydev.co/docs/clickup.md)
- [Alerts](https://docs.waydev.co/docs/alerts-integration.md): Learn how to setup and make the most out of alerts.
- [Slack Alerts](https://docs.waydev.co/docs/slack-alerts-and-targets.md)
- [Google Chat Alerts](https://docs.waydev.co/docs/google-chat-alerts.md)
- [Microsoft Teams Alerts](https://docs.waydev.co/docs/microsoft-teams-alerts.md)
- [Code Quality Analysis](https://docs.waydev.co/docs/code-quality-integrations.md)
- [Sonar Source](https://docs.waydev.co/docs/sonar-source.md): Connect your Code Quality Tools for static code-level metrics and make sure your teams are submitting qualitative code.
- [Bots](https://docs.waydev.co/docs/bot-integrations.md)
- [Slack Bot](https://docs.waydev.co/docs/slack-bot.md): Required Integration to Send DX Surveys.
- [AI Adoption](https://docs.waydev.co/docs/ai-adoption-integrations.md)
- [GitHub Copilot](https://docs.waydev.co/docs/github-copilot-integration.md): To zoom into the AI Adoption in your organization, integrate with GitHub Copilot.
- [Cursor](https://docs.waydev.co/docs/cursor-integration.md): Learn how to integrate Cursor in Waydev
- [Claude Code](https://docs.waydev.co/docs/claude-code.md): Learn how to integrate Claude Code in Waydev
- [Windsurf](https://docs.waydev.co/docs/windsurf.md): Learn how to integrate Windsurf in Waydev
- [Devin](https://docs.waydev.co/docs/devin-integration.md): To zoom into the AI Adoption in your organization, integrate with Devin.
- [Methodologies](https://docs.waydev.co/docs/methodologies.md): Review the most popular methodologies in the industry.
- [SAFe®, A Framework For Scaling Agile In Large Organizations](https://docs.waydev.co/docs/safe-a-framework-for-scaling-agile-in-large-organizations.md)
- [Agile - Kanban](https://docs.waydev.co/docs/kanban.md): Project management is all about making the complex simple.
- [Agile - Scrum](https://docs.waydev.co/docs/scrum.md)
- [Agile - Engineering OKRs](https://docs.waydev.co/docs/agile-engineering-okrs.md)
- [RAG Status in Engineering](https://docs.waydev.co/docs/rag-status-in-engineering.md): RAG status convention is used in a report that project managers use to assess how well the projects are going.
- [SSO/SAML](https://docs.waydev.co/docs/samlsso.md): Step-by-Step Guides for integrating your SAML IDP with the Waydev platfrom.
- [SSO/Custom Identity Provider via SAML 2.0](https://docs.waydev.co/docs/sso-custom-idp.md): Step-by-step guide to connecting your Waydev account using a Custom Identity Provider via SAML 2.0
- [SSO/Okta](https://docs.waydev.co/docs/sso-okta.md): A step-by-step guide for connecting your Waydev account using Okta.
- [SSO/Microsoft AD](https://docs.waydev.co/docs/sso-microsoft-ad.md): Step-by-step insturctions for connecting your Waydev account using Microsoft Active Directory.
- [SSO/Google](https://docs.waydev.co/docs/sso-google.md): Step-by-step guide to connecting your Waydev account using Google SSO
- [SSO/Microsoft Entra ID](https://docs.waydev.co/docs/sso-microsoft-entra-id.md)
- [Two Factor Authentication (2FA)](https://docs.waydev.co/docs/two-factor-authentication-2fa.md): A step-by-step guide to enable Two-Factor Authentication (2FA)
- [Privacy Policy](https://docs.waydev.co/docs/privacy-policy.md)
- [Security at Waydev](https://docs.waydev.co/docs/security.md): Security is one of the biggest considerations in everything we do.

## API Reference
- [Getting Started With Your API](https://docs.waydev.co/reference/getting-started-with-your-api.md): This page will help you get started with Waydev API.