Worklenz/worklenz

All in one project management tool for efficient teams

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 20 minutes ago
Added to GitGenius on September 21st, 2026
Created on May 16th, 2024
Open Issues & Pull Requests: 81 (+0)
GitHub issues: Enabled
Number of forks: 371
Total Stargazers: 3,181 (+0)
Total Subscribers: 15 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.6 days
Mean response time: 16.1 days
90th percentile: 23.1 days
Tracked items: 73

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 75% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 59
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 340 days
Stale 30+ days: 57
Stale 90+ days: 43

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Feature request (2)
  • bug (1)
  • enhancement (1)
  • help wanted (1)
  • performance (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Worklenz is a project management tool that combines task management, resource allocation, scheduling, and time tracking in a single platform.

The tool addresses the fragmentation problem of managing projects across multiple specialized applications. It provides an integrated workspace where teams can define tasks, assign resources, schedule work, and track time spent without switching between different systems. The platform is built on a TypeScript stack with a React frontend and Express backend, backed by PostgreSQL for data persistence.

Teams should consider Worklenz if they want to consolidate their project management workflow into one application rather than maintain separate tools for tasks, scheduling, and time tracking. It suits organizations that need visibility across resource allocation and project timelines alongside basic task management. The README does not compare the tool to specific alternatives, so potential adopters should evaluate it based on their need for an integrated approach versus best-of-breed point solutions.

The project shows active development with regular commits across the codebase. The team maintains both frontend and backend components consistently, indicating ongoing feature work and maintenance. The repository demonstrates engagement with the codebase through updates to core functionality and infrastructure.