Project timeline: Compare work output against code focus for a release cycle

Tags: Flow

The Project timeline report provides overviews of different work types for each engineer. These overviews allow team leads, managers, and executives to compare work types and see where engineers are contributing.

Use Project timeline to:

  • Visualize your teams’ work trends with data on multiple levels.
  • Gain insights into the engineering teams’ volume and work focus.
  • Compare Code volume and Commit volume with Impact and Code focus.

Who can use this?


Using Project timelines

Executives may want a 90-day view to get a sense of long-term trends for their organization. Managers may want to compare data across sprints.

Executives and managers use Project timelines to:

  • Analyze productivity
  • Ensure teams are on track.
  • Communicate with stakeholders using data.
  • View sprint data over time.
  • Spot roadblocks and debug development life cycles.
  • See when a team is working on a big release, updating older areas of the code base, or writing new code.
  • Demonstrate how a team's work is disrupted by late-stage changes to a spec from a product manager or other stakeholder.

back to top

View work volume

The first graph in project timeline shows you the aggregate work volume for your team.

Use the filters at the top of the report to select which users, teams, repos, and dates appear in the work volume graph.

Use the Work volume dropdown menu to select which volume type appears in the graph. View commit volume, code volume, commits per active day, and total impact.

Check the boxes to select what data type the graph shows. View trends, moving averages, or daily averages for a period of time.

Hover over a bar in the bar graph for more details about a data event.

back to top

Adding events

Add events to the Project timeline to provide context to historic data. For example, you may want to look back on hackathons, planning days, or offsites.

Create events for new hires. This helps team leads understand ramp-up and explain spikes in code or commit volume.

Import or create sprint calendars to provide quick filtering by team or organization. Learn how to create a calendar.

To add an event:

  1. Click Add event.
  2. In the pop-up modal, select the calendar you want to add and click Next.
  3. Enter the event name, date, time, repeating, and event type parameters.
  4. Click Create.
  5. Review the event and click Done to finish or click Add event to add another event.

back to top

Work trends show the breakout of work focus over time.

Use the Work trend dropdown menu to filter which work trends display on the graph. View absolute, relative, and stacked work trends.

Hover over data on the graph to view details on work trends for a specific point.

Details are broken down and color coded by Work type. The Work type key displays the names and colors of these Work types.

Use the Total lines of code or LoC toggle to view total lines of code by percentage or integer.

back to top

Navigating Work types

Find the Code focus leaderboards at the bottom of Project timeline. These graphs show the top individual contributors for New work, Legacy refactor, Helped others, and Rework.

Learn more about Flow metrics and Work types.

Use the date range filter to change what date range the report shows.

Click the dot icon next to an engineer’s name to view that engineer’s data.

Total lines of code shows the total lines of code for the date range. Hover over a data point to view how many lines of code were written by each engineer in the selected date range.

Note: Typically, the leader of New work is also near the top of Rework. Experienced developers tend lead in Legacy refactor and Help others.

back to top

If you need help, please email Support (opens email form) for 24/7 assistance.