Developer Summary Improvements

We redesigned the Developer Summary feature, adding new metrics and visual enhancements to improve usability. The new Developer Summary metrics include tt100, PRs Merged Without Review, PR Comments Addressed, and more. You can learn more about the new Developer Summary metrics here.

NEW: Pull Request Velocity Metrics

We've worked with our customers' feedback to develop metrics that reflect the Pull Request Velocity. You can now visualize the average duration for each step of the pull request cycle

We also built quantitative pull request metrics, such as the number of pull requests merged without rebasing, the number of pull requests merged without review, and more.

You can find the Pull Request Velocity metrics in the Developer Performance, Team Performance, and Repositories Stats reports. Click on the Pull Requests Stats button to toggle the Pull Request Velocity metrics.

NEW: Pull Request Risk

Introducing Pull Request Risk - Monitor the probability of a pull request to cause problems. The Pull Request Risk metric aggregates multiple data points, among the number of commits, the size of the commits, the spread and depth of the changes.

You can visualize Pull Request Risk using the Work Log and the Review Workflow features.

Activity Improvement

We've improved the Activity feature by adding more events that label an engineer as active.

We are now looking at Commits, Pull Requests, Pull Requests Comments/ Reviews, Tickets, and Ticket Comments.

NEW: Team Settings

Team Settings enable users to assign settings for a particular team. With the Team Settings you can:

  • Ignore commits based on a message (This is based on a regex. ex: /\bweb\b/i, result: all this team's commits that have a message which contains the word "web" will be ignored)
  • Ignore commits based on LoC (By default, we ignore commits with more than 8,000 LoC. Insert a positive integer to ignore this team's commits that have more LoC than the positive integer selected.)
  • Include merges into reports (By default, we don't include merges into reports, except for the Work Log. If you insert 'yes', we will include merges into this team's reports.)
  • Select the stats timezone (By default, we display stats according to the local time of execution. ex. If you are located in Los Angeles (PDT) and you have a team located in Chicago (CDT), selecting the PDT timezone for the team located in Chicago will convert that team's stats to the PDT timezone.)

You can assign team settings for both existing and new teams.

Assigning team settings for existing teams 

Step 1: Navigate to the Engineers page, in the Project section.

Step 2: Select a team from the team list, and then click Edit on the right side of the page.

Step 3: In the modal, select Settings. Insert the values you want to assign, and click Update.

Assigning team settings for new teams 

Step 1: Navigate to the Engineers page, in the Project section.

Step 2: Click Create new team.

Step 3: In the modal insert the team name and description. Then, click Settings. Insert the values you want to assign, and click Create.


Work Log improvements

You can now navigate to an engineer's Developer Summary profile by clicking on their name & avatar in the Work Log.

You can now access your commit in the Git provider by clicking the 'Go to Commit' button in the zoomed-in view of the Work Log.

NEW feature: Targets

The Targets feature enables users to set custom targets for their developers, teams, and organizations. You can check in on your goals and see how much progress has been made. 

To create a new target, click on the Create New Target button.

Targets Configuration

You will be prompted to insert your target values in the Targets Configuration section. It is not required to set target values for every metric.


Assignments Configuration

In the Assignments Configuration, you will need to select the teams, developers, and repositories you want to set targets for. It is not required to assign the targets for all of them. For example, you can assign a target only for a specific team.

Time Configuration

In the Time Configuration section, you need to select the Start Date. This will be the date when Waydev starts tracking your target. You need to select an End Date for your target. This will be the date Waydev finishes tracking your target.

Repeat

If you toggle on Repeat, Waydev will create an identical target one day after the end date. The identical target created will have the same time frame. For example, if you select the Start Date as Jun 1, 2020, and the End Date as Jun 30, 2020, Waydev will create an identical target on Jul 1, 2020, with the Start Date as Jul 1, 2020, and the End Date as Jul 30, 2020.

Timezone & Ignore Days

You need to select the Timezone for your target. You can ignore certain days, such as weekends, by selecting Ignore Days, and then clicking the plus sign on the right side. The ignored days will be displayed below.

Alerts Configuration

In the Alerts Configuration section, you can set alerts for specific events. You can choose to receive a full report at the end date of the target. You can set Waydev to alert you if your target Impact was reached before the end date.

Churn % Alert

You can set Waydev to alert you if the target was not reached at the end date. You can set Waydev to alert you if the Churn % exceeds a chosen value before the end date. If you toggle this on, you need to insert the chosen value of Churn % in the field below.

Target alert

You can set Waydev to alert you if the target falls below a chosen value before the end date. After you select the metrics, you need to insert the chosen values in the fields below.

Email & Slack alerts

You can set Waydev to send you alerts via email or via Slack. Learn how to configure alert channels (Email and Slack) here. In the drop-down, you can select the users who will receive the alerts.

Configuring alerts is not mandatory. All information regarding targets will be available in our app.

After you finished configuring your targets, click Save. Done!

Tracking progress

Tracking your targets' progress can be done by clicking the SHOW buttons corresponding to teams, developers, and repositories.


Progress report

In the modal, you will see the progress for each target metric. You can download the progress report as PDF, Excel, or print it right from the app. You can customize column visibility and search for a specific team, developer, or repository.

You can sort the metrics by clicking on the corresponding column header. You can rearrange the columns by dragging and dropping.

You can rearrange the columns of the main targets table by dragging and dropping the column headers. You can also sort the main targets table by clicking on the column header. You can also customize the column visibility of the main targets table.

Edit & delete targets

You can search for a target by creator name (ex. Harry Nielsen) or by date (ex. 2020-05-15). You can also edit or delete a target from the right side of the main targets table.

You can filter the targets by date, team, developer, and repository.

You can find the Targets feature in the Reports section.


Show Previous EntriesShow Previous Entries