Logilica Documentation
HomepageDemoBlogContact
  • About Logilica
    • Overview
  • Getting Started
    • Onboarding Data
    • Onboarding Users
    • Setting up Teams
  • Integration
    • Connecting Tools
    • Uploading Custom Data
  • Metrics & Reports
    • Introduction
      • Navigation
      • Dashboards
      • Data Exploration
    • Epics Delivery Tracker
    • Planning
      • Ticket Lead Time
      • Ticket Velocity
      • Ticket Overload
      • Sprint Health
      • Ticket Activities / Risks
    • Code
      • Code Cycle Time
      • Coding Velocity
      • Review Process
      • Developer Health
      • Code Activities / Risks
    • Build
    • Team Management
      • Teams Overview
      • Team Pulse
      • Activity Lens
    • Reports
    • Customization
    • Glossary
  • Configuration
    • User Management
    • Managing Contributors
    • Menu Management
    • Release Detection
    • Targets & Thresholds
    • DORA Configuration
  • Advanced
    • API Token Management
    • Import API
      • API Overview
      • Uploading Planning Data
      • Uploading CI Build Data
        • CDEvents Integration
      • Uploading Test Data
      • Uploading Team Data (beta)
      • Repositories
    • Export API
    • DataStudio
      • Data Models
        • CI Build
        • CI Build Stage
        • Contributor
        • Coverage Commit
        • Coverage File
        • Coverage Label
        • Coverage Test Result
        • Jira Component
        • Jira Epic
        • Jira Hierarchy Issues
        • Jira Issue Hierarchy Link
        • Jira Issue
        • Jira Issue
        • Jira Label
        • Jira Project
        • Jira Release
        • Jira Sprint
        • Project
        • Pull Request
        • Pull Request
        • Release
        • Team
      • Advanced Transformations
    • Integrations: Data Mapping
      • GitHub Projects Support
  • SSO Integration
    • Keycloak SSO
  • Subprocessors
  • Changelog
Powered by GitBook
On this page
  • Purpose
  • Explanations
  • Good to Know
  1. Metrics & Reports
  2. Team Management

Activity Lens

Understand what each team member is working on right now.

PreviousTeam PulseNextReports

Last updated 11 months ago

Purpose

The activity lens is a team manager's view to be aware of each team member's activity. It shows the most recent active items across tickets and PRs, and highlights some of the risks to delivery. This report also serves as a communication basis with team members to sync on progress and concerns.

Improvement Actions: The activity view helps for direct communication with contributors, being aware of what they are working on, celebrate progress and to address any concerns. Some actions might be to reallocate work across the team, set expectations, and prepare for standup meetings.

Explanations

The activity view includes the most recent progress on open items (tickets + PRs). By default a limited history includes items that have been recently closed as well. This includes:

  • the PR/ticket description and link.

  • a timestamp on the last activity as recorded in the repository/planning tool

  • the duration of since the ticket has been assigned or the since the first commit of the PR that is opened

  • a cycle/lead time breakdown of the different stages up to now

  • a set of risk tags listing potential delays/risks on tickets and PRs as defined for

  • and the state of the ticket/PR

Good to Know

The activity view serves as an entry point for a conversation with the team and its members for process improvements. It is not intended as a performance tracker. Note, the timeliness of the data is also affected by the scan frequency as defined by your organisation, which is 24h by default.

their categories