If you are already using OpenProject with your team to manage projects, you might want to explore additional use cases. One of them is ticket tracking: a flexible way to manage internal requests, service tasks, or user support alongside your existing workflows.
While OpenProject is primarily a project and task management tool, we are planning to release additional features in 2025 that will further support using it as a lightweight helpdesk solution.
Creating tickets
In OpenProject, you use work packages as tickets. All team members can create tickets and fill in the relevant information. You can define a dedicated work package type such as ‘Ticket’ or ‘Request’ to structure this.
You could also use the option to automatically create tickets from incoming emails. This is useful when external requests or issues are submitted via email — for example, when OpenProject is used as a lightweight helpdesk tool.
In order to capture all relevant information, you have different options to customize your work packages. One is to customize your work package types. If you like, you could create a work package type TICKET. Or you use the work package type TASK for tickets and add additional types such as sales opportunity to track those differently. Make sure that your work package forms are set up with fields for information that is required. Customize the work package forms to your needs. Remove any fields that are irrelevant, e.g. version. And you could add custom fields to your work packages, such as ticket type to indicate if it was coming in call or email or from your website.
The work package table will show you all tickets with the details that you would like to be displayed. Use the comprehensive filter option to sort the ticket list as needed, e.g. by priority, status, assignee or type of ticket / work package.
In the detail view of your work package, you can add comments to your ticket. If you mention team members with @name, they will receive a notification and reply accordingly.
Set reminders for a specific date and time, or activate date alerts to automatically notify team members when a ticket is due or needs attention (Enterprise add-on). Learn how to configure reminders and date alerts.
Another great new feature that helps you communicating on tickets is using internal comments (Enterprise add-on): For internal discussions that should not be visible to external collaborators (e.g. when a work package is shared). These are visible only to specific roles. Read more in our article on internal comments.
Kanban board to work on tickets
If you prefer a board view to work on your tickets and have a better, visual overview, you can use the agile boards in OpenProject. Choose a status board to know how many tickets are still open or check on your team by viewing the assignee board and how many tickets each team member is working on.
Ticket report
To get a quick overview of all tickets, the project overview can provide information about how many tickets are closed and how many are still open.
This is how you could manage tickets in OpenProject on a small scale which could be an additional benefit to your project management in OpenProject.
This is how you could manage tickets in OpenProject on a small or medium scale – a flexible and transparent solution that complements classic project management workflows.
We are excited to share that OpenProject has once again been recognized as a top-tier project management solution in 2026 by Gartner Digital Markets.
Building on our achievements from previous years, OpenProject earned an expanded set of distinctions in 2026. These new badges highlight our continued focus on strong functionality, ease of use, and high-quality customer support.
Gartner Digital Markets is a Gartner business unit that includes Capterra, GetApp, and Software Advice. It helps software buyers make confident decisions through verified user reviews, research, and insights.
OpenProject awards in 2026
Software Advice recognitions
In 2026, OpenProject received multiple Software Advice badges across core product categories:
Front Runners in Project management and Time tracking categories
Best Customer Support and Most Recommended across multiple categories in 2026:
Task management, Team management, Project management, Small business project management, Marketing project management, Online project management, Project management software for architects, Nonprofit project management, Strategic planning, Project portfolio management.
Capterra recognition
OpenProject was also recognized by Capterra in 2026 with the following distinctions:
Shortlist in Project management, Time tracking and Task management categories.
Best Value and Best Ease of Use in multiples categories:
Construction management, Project management, Project planning, Time tracking, Team management, Task management, Project portfolio management, Nonprofit project management, Strategic planning.
Powered by real user feedback
These recognitions are based on user reviews from real teams using OpenProject in their day-to-day work. We’re proud to see our focus on reliable project delivery, clear collaboration, and strong support reflected in the feedback.
Thank you ❤️
A big thank you to everyone who shared a review and helped us grow. Your input helps us prioritize what matters most and keep improving OpenProject.
Do you know why we forked Redmine back in 2012? The reason was accessibility. At the time, Deutsche Telekom hired us to remove various barriers in Redmine. When the Redmine maintainers showed no interest in reviewing our patches, we made the pivotal decision to fork the project. This allowed us to tackle the issue at its root. And it’s absolutely understandable that the Redmine maintainers, working in their free time, didn’t want to deal with ARIA labels and contrast ratios — there are simply more exciting features on the roadmap.
At OpenProject, we believe that everyone should have access to powerful project management tools, regardless of physical ability. Accessibility is not a checkbox for us. It is a core principle and a constant part of our product development.
OpenProject is accessible to a very large extent. Over the past years, we have invested heavily in making OpenProject more accessible and we have made great progress. With each release, we bring improvements with regard to accessibility. Our goal is clear. We want to be among the leading software providers when it comes to accessibility in open source project management.
Over the next couple of weeks we plan a series of articles to share our lessons learned.
There have already been a great number of achievements with regard to accessibility and a list of prioritized topics to be addressed:
20 releases with 64 accessibility improvements (progress report)
Accessible date pickers for complex scheduling tasks
Automate accessibility testing to avoid regressions
Screenreaders and ARIA live regions
Lessons learned when building the accessible TreeView component for our design system #62667
Why accessibility matters to me
This commitment is not just professional. It is also personal. After finishing school, I completed my civil service by assisting a high school student in his final year. He had a severe physical disability caused by illness. He could no longer walk and could barely operate a mouse. Working with him gave me a deep and lasting understanding of how much accessibility in technology can shape participation and independence.
This experience still resonates with me today and influences how we approach our work at OpenProject.
We have published an official Accessibility Statement on our website that reflects our ongoing commitment.
Building an accessible design system for OpenProject
In 2023, we made a key decision. We would build every new interface in OpenProject using an accessible design system. We chose GitHub Primer as the foundation. It provides robust and accessible core components, addressing crucial topics like color contrast and screen reader compatibility.
A dedicated team of designers and developers is continuously expanding our internal design system based on Primer. These components are reusable across the application, helping us ensure consistency and accessibility everywhere.
Every new view in OpenProject is now developed using this system.
Accessibility is complex and costly
Building accessible software is difficult. It requires deep technical knowledge, specialized design skills, and constant testing. It is also expensive. But it is worth it.
Modern collaborative platforms must support rich interactions like drag and drop or visual timelines. These features are helpful for many users, but they are a challenge for people who rely on screen readers. We work hard to create strong and usable alternatives.
A good example of our commitment is the introduction of the High Contrast Mode. This feature allows users with limited vision or visual impairments to work with OpenProject in a color scheme optimized for clarity and contrast. It improves legibility and reduces eye strain, especially in long working sessions.
To prevent regressions, we run automated accessibility tests with every build. These tests help us detect and fix issues early, long before they can affect our users.
We are grateful to be supported by ZenDiS, who help us with both funding and accessibility expertise. Their support enables us to move faster and with greater confidence.
Independent accessibility audit
The German Federal Ministry of the Interior commissioned an external test of OpenProject’s accessibility. The full test report can be found here (PDF).
We carefully reviewed the findings and resolved many of the reported issues. A list of the items we have already addressed is available in our community tracker.
We continue to improve. Our public roadmap lists further accessibility improvements that are planned for upcoming releases.
Working with the community
OpenProject is built with the support of other open source projects. We use libraries like CKEditor 5, FullCalendar, NG Select, and of course GitHub Primer. These libraries are essential to OpenProject. They save us thousands of hours of work and allow us to focus on what makes our platform unique.
We are happy to see that accessibility is becoming more important in these projects. When a component does not meet all our needs, we contribute back. One example is our work on a Tree View component for Primer, which we are developing to be fully accessible and available for the whole community.
What comes next?
We are not done. Accessibility is a continuous journey. We are proud of the progress we have made. And we are committed to going even further.
Thus, we are moving forward with every release. We eliminate barriers, improve features, and train our teams to consider accessibility from the very beginning and incorporate it in their decisions. That means during planning, design, development, and testing.
Here you find a list of the improvements planned for the next releases:
If you are interested in accessibility at OpenProject and would like to learn more about it, please feel welcome to contact us. Hearing about the real experiences of our users is very valuable to us.
How can open source tools from across Europe work better together? That’s the question OpenProject will explore at HackDays Paris, a hackathon organized by the French government’s DINUM, from June 2–4, 2025. We are thrilled to be a part of HackDays and aim to introduce task management features into the French-built Docs. Specifically, the OpenProject team plans to develop a first prototype exploring an integration with Docs.
Let’s take a look behind the scenes and explore how a shared vision for open source collaboration and Europe’s digital autonomy is becoming reality.
About HackDays Paris
HackDays is an open source hackathon organized by DINUM, the digital directorate of the French government. It brings together developers, UX/UI designers and contributors from across the public sector and open source ecosystem to work on shared goals, build working prototypes, and exchange ideas for a more sovereign digital future.
Under the slogan “We code, we build, we transform”, participants follow the mission to create open source apps aimed at strengthening European digital sovereignty. Specifically, it’s all about everyday collaborative tools. A category that OpenProject perfectly fits in.
Note
Docs, developed by DINUM, has recently joined the openDesk ecosystem initiated by ZenDiS in Germany. OpenDesk brings together powerful open source tools like OpenProject to form a digital workplace for public institutions. The collaboration between DINUM and ZenDiS around Docs and OpenProject is an example of cross-border cooperation in digital sovereignty. HackDays offers a valuable opportunity to strengthen that collaboration and build practical bridges between the two ecosystems.
Integrating task management into Docs with OpenProject
One of the most exciting developments in La suite numérique is the Docs app: a collaborative note-taking tool that supports real-time editing and rich content blocks. The software is built using BlockNote, a flexible JavaScript-based editor. Docs is already used in public institutions across France. Learn more about Docs here.
To demonstrate the potential of deeper collaboration, the OpenProject team at Paris will prototype an integration between OpenProject and Docs. The idea is simple: Users working in Docs should be able to create and link OpenProject work packages directly within the document. That way, notes and discussions can seamlessly turn into structured tasks, all while staying in the same interface.
Planned objectives for our participation at HackDays 2025:
Search and display OpenProject work packages in Docs.
Show dynamic metadata for linked work packages (e.g. type, status, dates).
Create OpenProject work packages directly from within Docs, possibly using selected content.
This prototype is only the beginning. Our broader goal is to show how open source tools — and the public institutions behind them — can work together more effectively.
United in mission and code: Open source software in Europe
Hackathons like HackDays are about more than prototypes. They’re about building relationships, exchanging knowledge, and strengthening the ecosystem of open source solutions in the public sector.
By bringing together tools like Docs and OpenProject, we’re not just solving immediate problems. We’re laying the foundation for a digital infrastructure that is open, modular, and aligned with public values – shaped by those who use it most. At OpenProject, we see a lot of potential in strengthening collaboration between projects supported by ZenDiS, DINUM, and other European partners. HackDays Paris is an important step in that direction.
With increasing pressure on governments to ensure transparency, interoperability, and control over their digital infrastructure, open source collaboration across borders is no longer optional but essential.
We look forward to sharing what we’ve built at the end of HackDays. Open collaboration leads to better tools. Let’s code, build and transform them together.
The OpenProject integration app for Nextcloud was updated to version 2.9! ✨ This update fully supports the OIDC authentication between Nextcloud and OpenProject.
We recommend to update to the newest version of the app through your Nextcloud app center to take advantage of the latest enhancements and fixes.
Changes of the release 2.9.0:
Support OIDC authentication method between Nextcloud and OpenProject
Add option to enable/disable token exchange with external OIDC provider
Add information for OpenProject version and plan required for OIDC setup
Support setup with Nextcloud Hub
Thanks, Nextcloud, for our continued partnership! 💙
OpenProject 16.0 has been released and this new major version introduces a range of new features and improvements. We look forward to hearing your thoughts and feedback on the latest updates. Please take a few minutes to learn what changes for you. We will summarize the most important changes in this blog article and, as always, please see our release notes that contain all changes, features and bug fixes.
In this blog article, we will present these feature updates:
We are especially excited about this improvement: Meeting backlogs make organizing and preparing meetings even easier — and help make the transition from classic meetings to the newer one-time and recurring meeting types even more powerful.
In OpenProject 16.0, users can now collect and manage agenda items flexibly using the new backlog feature. For one-time meetings, the Agenda backlog offers a space to store topics that are not yet scheduled but might be added later. For recurring meetings, the Series backlog allows teams to track open points across all meetings in a series and move items between occurrences as needed — without having to manually copy or recreate them.
Agenda items can easily be dragged from the backlog into a meeting or moved back again. Work packages can also be added directly to the backlog. Even if a meeting has no agenda yet, it can still maintain a list of important topics through the backlog.
Here’s an example of an Agenda backlog for one-time meetings:
And this is how a Series backlog for a recurring meeting looks like – with the option to move an agenda item to the current meeting:
Meeting backlogs bring more flexibility, better preparation, and a clearer structure to the way teams organize discussions — and are another great step toward making OpenProject’s meeting management even more efficient. Learn more about OpenProject meeting management in our documentation.
The end of classic meetings
As we announced earlier in this blog article, the Classic meeting type is no longer available in OpenProject 16.0. Existing classic meetings have been automatically converted into one-time meetings. No data is lost during this transition, apart from the meeting history.
To manage your meetings going forward, you can choose between one-time and recurring meetings. These dynamic formats give you more flexibility to structure your agendas and meeting workflows. For documenting decisions and results, you can use the Outcome feature, which replaces the classic Minutes functionality.
Internal comments in work packages (Enterprise add-on)
A new Enterprise add-on, available in the Professional plan and higher, allows adding internal comments to work packages. Internal comments are visible only to authorized users and help teams keep sensitive information separate from public discussions.
This feature is a further step to replace Atlassian Jira Service Management functionalities.
Automatically generated work package subjects (Enterprise add-on)
Consistent naming of work packages is now easier than ever. Users of the Enterprise Professional plan and higher can now automatically generate work package subjects based on predefined patterns. Subjects are created automatically during work package creation and do not need to be entered manually.
Tracking and reviewing time entries is now even more convenient. OpenProject 16.0 introduces the My time tracking module, which is personal to each user and must be activated by an administrator. Users can view, edit and log time entries either in a structured list or in a new calendar view for better overview.
Release to Community: Graphs on project overview page
We are happy to share that a feature previously available only as an Enterprise add-on is now released to the Community version with OpenProject 16.0: Displaying different types of work package graphs directly on the project overview page.
This means that all users can now display graphs directly on the project overview page to visualize important project information and communicate project status at a glance. Users can choose between different graph types, such as bar charts or pie charts, depending on their needs.
Updated Enterprise plans
With 16.0 OpenProject has updated its Enterprise offering. Each Enterprise plan (Basic, Professional, Premium, Corporate) now comes with a clearly defined set of Enterprise add-ons on top of the additional services and support levels.
This means that, going forward, some new Enterprise add-ons will be introduced in higher-tier plans. For example, the new Internal comments Enterprise add-on is part of the Professional plan.
Important information about these changes:
Pricing remains unchanged.
Support levels remain unchanged.
No features are removed for existing Enterprise customers.
If you are not yet using an Enterprise plan, you can easily test all Enterprise add-ons:
You will find more information about all new features and changes in our Release notes or in the OpenProject Documentation.
If you need support, you can post your questions in the Community Forum, or if you are eligible for Enterprise support, please contact us and we are happy to support you personally.
New to OpenProject? To test all features of OpenProject 16.0 right away, create a 14 days free trial instance for our OpenProject Enterprise cloud.
Prefer to run OpenProject 16.0 in your own infrastructure? Here you can find the Installation guidelines for OpenProject.
A very special thank you goes to the City of Cologne, Deutsche Bahn and ZenDiS for sponsoring released or upcoming features. Your support, alongside the efforts of our amazing Community, helps drive these innovations.
Also, a big thanks to our Community members for reporting bugs and helping us identify and provide fixes. Special thanks for reporting and finding bugs go to alex e, Klaas vT, Daniel Elkeles, Regina Schikora, Çağlar Yeşilyurt, and Александр Татаринцев.
Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings. This release we would like to particularly thank the following users:
Сергей Баранов, for a great number of translations into Russian.
Gzyyy, for a great number of translations into Chinese simplified.
rlmpereira, for a great number of translations into Portuguese.
Would you like to help out with translations yourself? Then take a look at our translation guide and find out exactly how you can contribute. It is very much appreciated!
As always, we welcome any feedback on this release. 💙
This module is planned to be released with version 16.0 on May 21, 2025. It will be available in all editions, Enterprise and Community.
Self-organization has become a key skill in today’s remote and flexible work environments. It’s not unusual for new employees to be asked during job interviews: “How well do you organize yourself?” Teams are expected to work independently. Managers are expected to trust them. But trust needs transparency — and the right tools to support it.
One of the most essential aspects of self-organization is managing your own time. And it’s not just about logging hours. It’s about giving people structure, helping them reflect on their work, and enabling teams to stay aligned without micromanagement.
Starting this May with OpenProject 16.0, we are introducing the My time tracking module. It comes with a calendar view and makes it easier than ever to view, log, and manage personal time entries with start and end times.
Read this article to learn more about this exciting update, including two practical use cases.
Track personal start and end times in a calendar view – How it works
Modern time tracking isn’t just about numbers — it’s about visibility. That’s why OpenProject 16.0 will introduce a new My time tracking module, enabling users to log their time with start and end times and visualize it in a calendar view.
This global module is designed for personal use: it helps users reflect on their daily and weekly workload, see time blocks at a glance, and create new entries directly from the calendar. Of course, every time entry in OpenProject is still connected to a work package — so your time tracking remains structured and linked to tasks.
Depending on your configuration, you’ll see either a calendar or list view:
If exact time tracking is enabled, the calendar view is shown by default.
If not, the list view is shown — a simpler overview for users who only track hours, not the start and end times.
Display your calendar either in a Day, Week, Work week or Month view. In the calendar, users can:
Click and drag to create new entries.
Move entries to different times or days.
Resize entries to adjust their duration.
Move an entry to the “No specific time” row on top of each day, to remove start and end time.
Each time entry is color-coded based on the type of its work package — just like in the Team planner, so you can easily identify different items of work.
You can also visually distinguish between working (lighter grey) and non-working days (darker grey). Choose the Work week view to only see the working days that are enabled under Administration → Calendars and dates → Working days and hours.
Tip
Admins can enable exact time tracking in the global administration — and enforce it with the setting Require exact times (Enterprise add-on). This helps organizations improve accountability and prepare for future resource planning features. See the two examples below for different use cases.
When is the list view the better choice?
If the exact time tracking is not enabled, a calendar view does not make much sense. The calendar in the My time tracking module then adds all time entries at the top of each day, which clutters the view. Here, the list view comes in handy and is also set as a default if the exact time tracking is disabled.
Of course, you might also choose the list view if exact time tracking with start and finish date is enabled. It displays your logged times in a collapsible list that also shows sums and other logged information.
Practical benefits: Time tracking for freelancers and growing teams
The new My time tracking module supports different ways of working — from independent teams to organizations with structured planning needs. Let’s look at two example scenarios to show how flexible time tracking with start and end times can be.
Example 1: Small team with freelancers — balancing autonomy and structure
Imagine a small digital agency in Berlin. The team consists of five full-time employees who manage their own schedules and two freelancers who invoice by the hour. Everyone tracks their time — not because they’re told to, but because they want to stay on top of their workload.
With the new calendar view in OpenProject, all team members can:
Quickly enter time directly by clicking and dragging in the calendar.
Get a visual overview of how much time they’ve spent on different tasks.
Spot gaps or overloads in their week at a glance.
For freelancers, start and end times provide the exact data that is sometimes needed in cost reports. For the whole team, it’s a simple way to reflect, stay aligned, and avoid time slipping through the cracks — all without micromanagement.
Example 2: Growing teams who need efficient resource management
Now consider a mid-sized city administration in Germany. The digitalization team has grown to 20 employees, and it’s become harder for department heads to keep an overview of team capacity. At the same time, the organization wants to foster trust and avoid excessive reporting requirements.
By using the My time tracking module with start and end time enforcement (available in the Enterprise edition), admins can:
Ensure that team members always track their time precisely
View consistent data across the organization for reporting and planning
Identify over- or under-allocation of resources early on
Time entries remain private in the personal module, but the structured data feeds into cost reports and will lay the foundation for upcoming resource management features.
Important
The ability to require exact time tracking is available in the Enterprise Professional plan. You can activate it in the Administration → Time and costs → Defaults.
Summary: Calendar-based time tracking with start and end times
The new My time tracking module in OpenProject 16.0 helps you log, review, and manage your personal time entries more intuitively. With a calendar-based interface and support for start and end times, it makes time tracking more visual, structured, and user-friendly.
Whether you’re working independently or as part of a growing team, this module provides the tools you need to stay organized, maintain transparency, and prepare for future planning features.
Two views available: Calendar (default if start/end time tracking is enabled) or list view (default if disabled).
Calendar interactions: Click and drag to create entries, move or resize them, or remove times by dragging to the “No specific time” row.
Color-coded entries: Time entries inherit the color of the work package type to provide visual context.
Workdays vs. non-workdays: Configurable workdays appear with a lighter background, while non-working days are dimmed. A “Work week” toggle hides weekends.
Admin settings:
Enable start and end time tracking (all editions).
Enforce exact time tracking (Enterprise only).
Benefits for teams of all sizes:
For small teams: intuitive tracking and visual workload overview.
For larger organizations: consistent data for reporting and long-term resource planning.
Update May 2025: Internal comments have been released with version 16.0, and are included in our Enterprise professional plan.
With OpenProject 16.0, scheduled for May 21, 2025, we will introduce a new way to communicate with your team: internal comments in the work package Activity tab. This blog post will talk about why we developed this feature, how you can use it and how it might evolve in the future.
Why do we need internal comments?
OpenProject is as much a tool for team communication as it is for project management. In public offices, hospitals, universities and small and large companies, teams use OpenProject to manage the exchange of information.
Most of this information is contained within individual projects and our users sometimes work across multiple projects, each with a limited set of users with different roles. Each of these roles comes with a different set of permissions. For example, project admins generally have full, unrestricted access to the project, project members might have the ability to create only certain types of work packages or execute certain status changes, while external (non-project) collaborators might only be able to read and write comments. This approach allows for fine-grained access control.
In version 13.1 of OpenProject, we introduced work package sharing. This made it possible to invite users who are not project members to individual work packages in a limited capacity, with rights to only view, view and comment, or even modify the shared work package.
Sharing is especially useful when you need to involve people in very specific, small scopes. They might be external collaborators, clients, suppliers or observers. However, until now, anyone who could view a work package could also view all the comments in the Activity tab. This might not always be ideal. There might be times when a core team might want to discuss things related to a work package confidentially amongst themselves and keep that conversation separate from what is visible to all other stakeholders.
That’s where internal comments come in.
Internal communication
Internal comments lets core project members limit the visibility of certain comments to a select group that is a smaller subset of project members.
To use this feature, a project admin will be able to enable internal comments for their project. By default, these internal comments are only visible to the project admin role. To expand who can view these comments, instance administrators can grant a new set of permissions (to view, write and edit internal comments) to any number of roles.
Users who have these roles within their project will then see a checkbox under the comment box labeled “Internal comment”:
Checking this will turn that comment into an internal comment. The background color of the comment box will change to indicate this.
Once posted, the comment will also be marked in the same color, along with a lock icon, to distinguish it from regular comments.
Users without the necessary permissions will not be able to see these comments, nor that new comments were posted. They will not be visible in neither the Activity tab nor the other places where user activity is reported, like the user activity and project activity pages.
A project can include a number of different stakeholders and not all stakeholders should be privy to all information. Ideally, all discussion around a single topic or work package should happen in the same place but because there are currently no visibility controls, confidential conversations need to currently happen elsewhere. This is often a separate work package (in a different project), a Matrix chat room or email. All of these introduce inefficiencies by introducing information duplication and blind spots.
With internal comments, all information and stakeholders can be gathered in one work package that is considered the single source of truth and core project members are nevertheless able to communicate amongst only themselves.
Collaborate with an external client or supplier
Projects often involve external clients or suppliers. They can be invited to a project or an individual work package with specific, limited roles. This reduces the need to organize outside the project context using different incompatible tools.
However, the core project team might want to keep some of their conversation private and limited to a smaller group, for example when discussing rates, negotiations, sensitive financial information or contextual information. With restricted visibility comments, the core team can have a meta-level conversation within work packages that external clients or suppliers cannot access.
Use OpenProject as a helpdesk tool
Implementing internal comments is also a step towards making OpenProject a capable helpdesk tool. Customer support teams can write internal notes only they can view, along with public comments and responses the customer can read and react to.
This will be supplemented in the future with other important helpdesk features such as the ability to set up OpenProject to automatically create work packages based on incoming emails to certain addresses and allow responding to comments via email.
Your feedback
We are excited to release internal comments this May with version 16.0.
As an open source software company, we value the ideas and feedback of our user Community. If you have opinions about these changes or have feature requests, feel free to join our Community instance and share your thoughts.
We would like to thank ZenDiS for sponsoring this feature. We hope you are looking forward to this update as much as we are looking forward to releasing it.
How to choose the best project management software?
Finding the best project management software suited for your organization is a challenging task. We have put together the important criteria to help you make that choice. As an open source software, we of course advocate for choosing an open source project management software.
We prepared a latest overview of the top 5 open source project management software in 2025 for you to compare and see which one could enable you to tackle your challenges best. Take a look at the feature sets, hosting options, prices, security of the open source project management solutions to make an informed decision for your organization.
Please also make sure to check your potential project management software provider’s privacy policy and data security strategy in detail. In a project management software, confidential data is being processed so you have to make sure your data is in the right hands and being protected.
Here are our 5 best open source project management tools in 2025 with different advantages:
OpenProject is the leading open source project management software, licensed under GNU GPL v3.
Free and open source software
The software code is freely available on GitHub and the changes to the source code are transparently traceable any time. With OpenProject there is no vendor lock-in.
As self-hosted versions, the Community and Enterprise on-premises editions provide users with data sovereignty. You will benefit from a set-up with ultimate control over your data and with your preferred technical set up.
If you don’t have the capacity or knowledge to host OpenProject in your environment, we offer the Enterprise cloud edition with secure hosting in the EU or on request in Germany. With the OpenProject Enterprise cloud, you will benefit from a data center and network architecture built to meet the requirements of the most security-sensitive organizations. You can rely on hosting in a high security data center and redundant infrastructure, built for high availability and performance. Continuous encrypted data backups in separate locations, regular data privacy assessment and certification by external auditor are part of the security strategy.
Extensive project management features
OpenProject maps the entire project lifecycle, from project planning, execution and project controlling, to project closure. The software supports classic, agile and hybrid project management. The software includes extensive project management functions, such as project and milestone planning (Gantt charts), task recording, agile boards, project wiki, pre- and post-processing of deadlines, forums, time and cost recording, budgets.
Also, UX and UI play an important role at OpenProject. We invest heavily into our interface design team so that the use of OpenProject is as intuitive as possible and users don’t need much training or a documentation quest before jumping right in.
Configuration
The software is flexibly configurable, can be adapted to individual requirements and is suitable for the respective company processes. With a powerful API, additional systems can be connected if required.
Part of openDesk
OpenProject is one of the software solutions that are used for openDesk – the Sovereign Workplace. The vision of the Sovereign Workplace is to offer a true open source alternative to Microsoft and Google throughout Europe. And OpenProject is ‘openDesk’ ready, which means the current version (and upwards, of course) can be used as part of openDesk.
Active maintenance and development
OpenProject is continuously developed and maintained by an active developer community. New functions, improvements and updates are released regularly. This also allows a quick reaction to possible security gaps.
Professional support and training
OpenProject offers professional support and training. This ensures that users receive both technical and functional support in order to work with the software in the best possible way.
Pricing
The OpenProject Community edition covers a wide range of features and plugins and is free of charge. This is an on-premises version that requires you to host it in your own environment.
The Enterprise cloud and on-premises editions offer you professional support as well as additional premium and security features. Consequently, these are paid plans. Pricing starts from €5.95 per month per user, long-term subscriptions though are cheaper.
OpenProject offers a 14 days free trial which you can extend on request.
GitLab
GitLab is a source code management and DevOps platform that can also be used for project management, licensed under MIT open source license. It has a clear focus on software development. The users benefit from fast deployments, standardization, automation and increased security of the software development process.
GitLab has a vast feature set to allow the mapping of the entire software delivery lifecycle. It offers many specific features targeted at software developers, such as DevOps Reports. Both agile and traditional project management methodologies are supported by GitLab as it also includes timelines, task management and workflows. However, time tracking or budget and costs are features missing in GitLab’s offer.
Overall, one can say that GitLab has a more technical user interface due to the fact that the main target group is software engineers. It might not be as intuitive as other open source project management software in 2025.
Exciting: If you are not entirely convinced by the GitLab offering in terms of project management, but like its feature set, you can use OpenProject with its GitLab integration.
GitLab is available in the cloud and on-premises. The self-installed version provides full data control. GitLab’s cloud version, the GitLab.com core infrastructure, is primarily hosted in Google Cloud Platform’s (GCP) US-East1 region.
The location where your data is stored is important as it determines which regulations and data privacy measures apply (in the EU e.g. the providers have to adhere to GDPR). Feel free to read up more about cloud security.
GitLab Pricing
While there is a free version available (with limited storage, users and features), the paid versions start from $19 per user per month. To test the paid version, GitLab offers a 30 days free trial.
Tuleap
Tuleap is an open source project management software for agile project management, licensed under GNU GPL.
Tuleap comprises all agile project management features like task board, backlog, Kanban boards, burnup and burndown charts, dashboard. It allows you to execute software development, test management, project tracking and agile planning in specific.
If you are an agile or software development team, Tuleap’s clear focus on the agile methodology might work very well for you. For a broader project management approach, you might miss traditional project management features like a Gantt chart or a Wiki, and options to track time, budget and costs. Working in Tuleap, its interface seems very intuitive.
Tuleap is available in the cloud and on-premises. The premium cloud version gives you a hosting choice among providers in France, Switzerland, USA, UK, Korea. There is no information on the basic cloud hosting.
Tuleap Pricing
There is no free version of Tuleap available. The cheapest option is the basic cloud version that starts from 6€ per user per month. However, Tuleap offers a free trial if you contact them.
Taiga
Taiga is an open source project management software whose beginnings date back to a Kaleidos hackathon in 2013. It is licensed under MPL 2.0.
Taiga’s vision was to create an intuitive and visually appealing agile project management tool for developers and designers. Accordingly, Taiga offers a comprehensive feature set for agile project management. It includes Kanban boards, backlog, estimation tool, issue tracking, dashboard and more.
Consequently, classic project management features are not part of Taiga, limiting its use cases to agile methodologies only. Taiga has a very intuitive interface, which makes it easy for users to start working with the software.
Taiga is available in the cloud and on-premises. The cloud version is hosted in the EU by AWS, which means it complies with GDPR in this regard.
Taiga Pricing
There is a free cloud and free on-premises version available. The paid Taiga cloud edition comes with premium support and is at $70 per month (unlimited users).
Orangescrum offers classic as well as agile project management features. Resource management, schedule management (Gantt charts), budget and cost management, issue tracking, time tracking, workflow management as well as backlogs are available.
The on-premises and cloud version include even more features (burndown chart, project overview, task labels, custom task types, recurring tasks, invoicing etc.). Those are premium features and are part of paid plans.
Orangescrum is available in the cloud and self-hosted. The cloud version is hosted with AWS (location not mentioned).
Orangescrum’s privacy policy states that they are taking many steps across the entire company to ensure they will be ready for the GDPR.
Orangescrum Pricing
The Orangescrum open source edition can be downloaded for free. You can add paid support plans to it, from $299 per month. You can try Orangescrum for 15 days for free.
There is a free Orangescrum cloud edition for 3 users and limited storage, paid plans are starting from $8 per user per month. The on-premises version with premium features and support is charged as a once-off (from $4,425), with potential support subscriptions for following years.
Compare the top 5 open source project management software
Choosing the best project management software that fits your organization depends on a variety of criteria, including the features and use cases you want, the size of your team, and hosting preferences. All listed top 5 open source project management software have their advantages.
If you are looking for an open source project management software in 2025, we recommend to have a look at OpenProject, GitLab, Tuleap, Taiga, and Orangescrum.
To give you a quick summary:
OpenProject offers traditional, classic and hybrid project management features with a very intuitive interface. It is available in the cloud and on-premises and focuses on data security and privacy, protecting your confidential data. Therefore, the cloud version is securely hosted in the EU or on request in Germany. The OpenProject Community edition (on-premises) includes a comprehensive feature set and is free of charge.
GitLab has an elaborate feature set that is mainly targeted at software development teams and has a more techy interface. It is available in the cloud and on-premises. The cloud is hosted in the US. They offer a free on-premises version for a maximum of 5 users with limited storage and essential features only.
Tuleap is only for agile project management teams. It offers an intuitive interface. It comes both as on-premises and cloud version. Only for the premium cloud version you can choose the location of the host provider. Tuleap does not offer a free version.
Taiga also only offers agile project management features, though with a very appealing interface. It is available as cloud and on-premises version and the cloud version is hosted in the EU. Taiga offers a free cloud and free on-premises version.
Orangescrum has a big feature set for traditional as well as agile project management with an intuitive interface. There are on-premises and cloud versions, the latter is hosted by AWS but it seems Orangescrum might not comply fully with GDPR. The open source version with reduced feature set is free of charge and there is a free cloud version for a maximum of 3 users.
Regarding the pricing of all top 5 open source project management software, we recommend you visit the individual websites to input your team size and other requirements to find out the detailed pricing as there are many variables that may change the pricing.
Ever wondered what all these project management terms actually mean? Understanding key project management terminology is essential for effective collaboration and successful project execution. In this article, we’ll walk you through fundamental concepts and terms.
If you’re looking for OpenProject-specific definitions, see our Glossary, where we define the most commonly used terms in OpenProject.
Waterfall
Waterfall is sometimes referred to as classic or traditional project management. It is characterized by a sequential flow of tasks. One task is completed before the next can begin. This linear structure gave the method its name — Waterfall.
Because of this sequential nature, careful planning and precise timing are essential. Delays can lead to significant setbacks. A Gantt chart is a typical way to visualize a waterfall project.
Agile
Agile project management recognizes the complexity and uncertainty of many projects. It uses an adaptive approach: a large project is broken into smaller pieces that are handled by cross-functional teams.
Work is done in short cycles, known as iterations or sprints, and customer feedback is integrated regularly. Agile allows for greater flexibility and continuous improvement during the development process.
Scrum
Scrum is a framework used within agile project management. Originally developed in software, it can be applied in many industries. Scrum divides work into small, manageable tasks and emphasizes collaboration, progress tracking, and regular adjustment.
Scrum teams deliver value incrementally. A task board helps visualize the current status.
Sprint
A sprint is a fixed-length iteration in agile development — often lasting one or two weeks. During each sprint, the team works on selected tasks from the backlog. After each sprint, results are reviewed, and the backlog is adjusted based on feedback and progress.
Board
A board is a visual tool used to manage and track tasks in a project. In OpenProject, boards help teams stay organized and collaborate effectively by showing tasks (work packages) in columns such as To Do, In Progress, or Done. This makes boards ideal for agile workflows like Scrum or Kanban, but they are just as useful for managing general task lists, team priorities, or feedback rounds.
In OpenProject, there are basic boards for all users and action boards (with automatic sorting e.g. by status or version) available as Enterprise add-on:
Tip
To learn more about how boards work in OpenProject and which board types are available, read our blog article on Agile Boards.
Kanban
Kanban is a visual approach to agile project management. It focuses on transparency and continuous delivery. A Kanban board shows tasks in columns (e.g., To do, In progress, Done) and helps teams limit work in progress.
Backlog
The backlog is a list of all items that need to be completed to achieve a project goal. Tasks are typically prioritized, and the most important ones are selected for the next sprint. A backlog serves as the central source of truth for the team.
User story
A user story represents a piece of functionality from the user’s perspective — something they want to achieve. Stories should be small enough to complete within a sprint and usually follow a standard format like: “As a [user], I want to [goal] so that [benefit].”
Epic
An epic is a large body of work that represents a big objective or need. It’s typically too large to complete in a single sprint, so it is broken down into smaller user stories that can be tackled incrementally.
Milestone
A milestone marks a significant point in a project — such as deadlines, delivery dates, or decision gates. It helps monitor progress and often represents a non-working task with a specific target date but no duration.
Bug
A bug is an unintended error or issue in the software that affects functionality or performance. Bug tracking is an essential part of product development.
Feature
A feature is a specific piece of functionality that delivers value to the user. In agile teams, features are often driven by user stories and linked to requirements in the backlog.
Story points
Story points are used to estimate the effort required to complete a task, feature, or user story. They are typically assigned using a predefined scale and help teams plan and track sprint velocity.
Burndown chart
A burndown chart is a tool mostly used in Scrum. It is a two-dimensional graph that shows the amount of work remaining (usually measured in story points) versus the time left in a sprint or project. This visual representation helps teams track their progress and stay focused on their goals.
Work package
A work package is a group of related tasks that can be managed and delivered together. In OpenProject, a work package can represent a task, feature, user story, bug, phase, or milestone.
Wiki
A wiki is a collection of collaborative, editable pages where teams can document knowledge, processes, or project information. In OpenProject, each project can have its own wiki, helping centralize documentation.
Dependencies
Dependencies, also known as relations, define how tasks are connected. For example, one task may need to finish before another starts. Managing dependencies helps create realistic timelines and avoid bottlenecks.
Project
A project is a temporary endeavor with a defined goal, timeline, and scope. It can range from small internal improvements to complex product releases. Even though the term is widely used, it’s not always clearly defined. Taking time to align on what constitutes a “project” in your context helps ensure consistent planning and execution.
We are happy to announce the release of OpenProject 15.5. Among other changes, users now can filter for descendants of work packages, which includes children, grandchildren, and deeper levels in the hierarchy. This makes it easier to focus on specific parts of a project hierarchy.
In this blog article, we will take a closer look at these feature updates:
And there are more great updates in this version again. For more details on other changes, features and bug fixes in 15.5, please check out our release notes.
Tip
The next version is already on the horizon: In May 2025, we plan to release OpenProject 16.0 with major feature changes. One change will be the ‘sunsetting’ of classic meetings, meaning users will only be able to create one-time and recurring meetings then. With the release of 15.5, you already see a hint in the application that classic meetings are unsupported. We recommend switching to the newer meeting types now to benefit from recent improvements and to ensure a smooth transition. Read this article to learn more: Classic meetings will be replaced: What changes with OpenProject 16.0
Filter for descendants of work packages
OpenProject 15.5 introduces a helpful new filter to better navigate complex project structures. The Descendants of filter allows you to display all related work packages beneath a selected parent — including its children, grandchildren, and deeper levels.
For example, if you apply the filter “Descendants of” is (OR) “Open Source Conference”, the view will include:
Two direct children: Create sponsorship brochure and hand-outs and Set date and location of conference
Two children of the brochure task — in other words, grandchildren of the main phase: Design brochure and Write brochure text
One grandchild under the location task: Contact sponsoring partners
This filter is available wherever filters are supported, such as work package tables or agile boards. Until now, it was only possible to filter for parent work packages — this new option lets you see the full hierarchy below a selected item, making it easier to focus on a specific part of your project and understand its structure at a glance.
Column for children in work package tables (Enterprise add-on)
OpenProject 15.5 adds a new Children column to work package tables — giving you a faster and more structured way to view hierarchical relationships without needing to apply filters or switch views.
This column shows a clickable dropdown icon alongside the number of child work packages linked to each parent. With one click, you can expand the parent directly in the table to get an immediate overview of its structure. Each child is clearly marked with a Child label, helping you stay oriented even in complex project hierarchies.
This feature is especially useful when working with large datasets or focused views, where quickly understanding relationships between work packages is key.
For example, in a project phase like Open Source Conference, the Children column shows how many related work packages are connected to that phase — helping teams assess scope and progress without leaving the table view.
Note
All relationship columns, including the new Children column, are part of the Enterprise add-ons.
% Complete included in work package table sums
Imagine you’re part of an NGO marketing team planning newsletters, blog articles, and videos for the upcoming year. Each campaign includes several tasks — like writing a blog post titled Behind the scenes: Organizing a field mission or producing the video Meet our volunteers. Both are in progress and marked as 40% complete.
With OpenProject 15.5, it’s now easier to get an overview of your content pipeline: the % Complete value is included in the sum row of work package tables. Alongside Work and Remaining work, this provides a quick snapshot of overall progress — in this case, 42 hours of work planned, 25.2 hours remaining, and an overall completion rate of 40%.
All three values are calculated based on the selected progress tracking mode, giving you accurate insights tailored to your team’s workflow — whether you’re tracking effort manually or automatically.
Advanced accessibility
Accessibility is not just a feature — it’s a fundamental part of building inclusive software. With version 15.5, we’ve taken another step forward in making OpenProject more accessible, especially for users who rely on screen readers or keyboard navigation.
The date picker now provides clearer, more meaningful feedback during manual input, ensuring that everyone can interact with project timelines confidently and independently. This means that screen readers now announce when switching between manual and automatic scheduling modes. Changes to one field, such as the Start date or Duration, are immediately announced when they affect related fields. The “Today” shortcuts come with ARIA labels that give users helpful context — for example, “Select today as start date.”
You will find more information about all new features and changes in our Release notes or in the OpenProject Documentation.
If you need support, you can post your questions in the Community Forum, or if you are eligible for Enterprise support, please contact us and we are happy to support you personally.
New to OpenProject? To test all features of OpenProject 15.5 right away, create a 14 days free trial instance for our OpenProject Enterprise cloud.
Prefer to run OpenProject 15.5 in your own infrastructure? Here you can find the Installation guidelines for OpenProject.
A very special thank you goes to the City of Cologne, Deutsche Bahn and ZenDiS for sponsoring released or upcoming features. Your support, alongside the efforts of our amazing Community, helps drive these innovations.
Also, a big thanks to our Community members for reporting bugs and helping us identify and provide fixes. Special thanks for reporting and finding bugs go to Abhiyan Paudyal, Andreas H., Paul Kernstock, Patrick Stapf, and Stefan Weiberg.
Last but not least, we are very grateful for our very engaged translation contributors on Crowdin, who translated quite a few OpenProject strings! This release we would like to particularly thank the following users:
Yuliia Pavliuk, for a great number of translations into Ukrainian.
Adam Siemienski, for a great number of translations into Polish.
NCAA, for a great number of translations into Danish.
greench, for a great number of translations into Turkish.
Would you like to help out with translations yourself? Then take a look at our translation guide and find out exactly how you can contribute. It is very much appreciated!
As always, we welcome any feedback on this release. 💙
Whether you’re a team of five or fifty — as your organization grows, so does the number of projects, tasks, and priorities. At some point, work packages that once fit on one board become a sea of cards, and keeping focus becomes a challenge.
That’s why we created the Attribute highlighting feature: it helps you immediately see what needs your attention most. In this article, we’ll walk you through a relatable scenario and show how this Enterprise add-on can support you in staying focused and scaling successfully.
You’ve grown — now it’s time to change how you work
Things are going well. Your organization is growing. More clients, more projects, more team members. But with growth comes complexity. What used to be a simple backlog is now a multi-project list of dozens — maybe hundreds — of open tasks. And suddenly, you’re no longer sure what’s urgent, what’s blocked, or what’s been waiting for weeks.
Your system hasn’t changed, but your needs have. And that’s a good thing — because it means it’s time to invest in new ways to keep your growing team aligned.
Clean up your work package table by highlighting priority, status or finish date
Let’s take your team’s work package table as an example.
You’ve filtered for this month’s deliverables — but the list is still long. You spot tasks with due dates coming up, some that are marked high priority, and one that was updated just now. But it takes a few minutes of scrolling and reading to get the full picture.
That’s where Attribute highlighting comes in. This Enterprise add-on allows you to visually emphasize specific values in your work package table using color: overdue tasks can turn red, high-priority items might stand out in orange, and different status values can appear in clearly distinguishable shades.
With just a glance, your team can now immediately see:
What’s overdue,
What’s marked as high or urgent priority,
What’s resolved or in progress.
Important
The Attribute highlighting feature is part of the Enterprise add-ons in OpenProject. You can find more information about it in our documentation.
How Attribute highlighting works
Let’s say your team uses the Priority attribute and a custom status workflow. You can highlight individual attributes inline (Status, Priority, Finish date) or apply full-row highlighting based on Status, Type, or Priority.
Once you’ve set this up in the work package table view, your team sees these visual cues automatically — without needing to open each task individually.
Tip
You can configure which colors are used for each priority and status in the System administration. Learn how to adjust them for priorities and for statuses.
Let’s look at an example work package table and how it looks with different attributes highlighted. Please note that you can change the colors for work package attributes and that they might look different in dark mode or light mode.
1. No attribute highlighting
Image 1: A work package table in OpenProject, no attributes highlighted.
2. Status, Priority and Finish date highlighted inline
Image 2: A work package table in OpenProject, with inline-highlighted Status, Priority and Finish date.
3. Highlighted by Status
Image 3: A work package table in OpenProject, highlighted by Status.
4. Highlighted by Type
Image 4: A work package table in OpenProject, highlighted by Type.
5. Highlighted by Priority
Image 5: A work package table in OpenProject, highlighted by Priority.
Other helpful features for prioritizing work packages
Attribute highlighting works best in combination with other prioritization features. Here are a few tools to support your growing team:
Status workflows
Define which status transitions are possible and by whom, helping structure review and approval processes.
Date alerts and reminders
Automatically notify assignees or watchers when a due date is approaching.
Versions
Group work packages under a common version to align delivery and deadlines across tasks.
Custom fields
Add structured information to work packages that you can then use for filtering, highlighting, or grouping.
Each of these features helps you bring structure to complexity — and together, they make it easier to stay focused.
Stay focused as you scale
Growth is exciting — but only sustainable if your tools grow with you. Features like Attribute highlighting can make a real difference: not by changing how you work, but by making it easier to see what matters.
With a growing team and more responsibilities, the ability to focus at a glance isn’t just a nice-to-have — it’s essential. Let OpenProject help you take that next step.
When we released dynamic meetings in version 13.1 of OpenProject, it was the start of a larger redesign of the Meetings module. Since, we have continued to improve it by adding new features and optimizing the design based on user feedback.
Until now, the new ‘dynamic’ meetings lived alongside the ‘classic’ meetings with the goal of eventually replacing it entirely. We are excited to announce that this May, we will be able to completely remove classic meetings and fully transition to the more modern and versatile dynamic meetings.
With version 15.5 (coming April 2025), classic meetings will still be available but we strongly advise against using it. You can create one-time and recurring meetings instead.
What is changing regarding classic meetings
When you create a new meeting in OpenProject in version 15.4, you have three choices: one-time, recurring and classic. Starting with 16.0, the third ‘classic’ option will no longer be offered.
To further prepare our users, it will already be marked as ‘unsupported’ in the upcoming version (15.5) this April, 2025. The actual removal will happen in May 2025, with the release of OpenProject 16.0.
Why we are removing classic meetings
Ever since 13.1, our goal has been to replace classic meetings with an entirely new, more modern and versatile Meetings module. Since the first release of dynamic meetings in version 13.1, we have added a number of new features and improvements, including:
the ability to document outcomes for each agenda item when a meeting is in progress
To completely replace classic meetings, we had to ensure that all existing features in the old module were available in the new one and that we had a clear migration strategy.
With the release of meeting outcomes in OpenProject 15.4, we now meet both conditions. Our users have also had a chance to get used the new Meetings module over the past year.
Migration to 16.0: What happens to your existing classic meetings
All existing classic meetings will be converted to dynamic (one-time) meetings when migrating to OpenProject 16.0.
How will former classic meetings be displayed?
Since classic meetings did not support individual agenda items, your older meetings will simply contain a single agenda item with the content of the ‘Agenda’ tab. This will have a single outcome, with the content of the ‘Minutes’ tab.
Can I still edit my former classic meetings?
All past classic meetings will be set to a ‘Closed’ state, which makes them read-only. However, roles that have the permission to manage the agenda item will nevertheless be able to modify the meeting status and thereby re-open the meeting to change the content.
What happens with already-created upcoming classic meetings?
Upcoming classic meetings will also be converted to dynamic meetings but with an ‘Open’ meeting state.
What happens to other information and data in my classic meetings?
All existing meeting details, participant list and attachments will be retained unchanged. All information concerning the agenda, the minutes and meetings data will be preserved. Meeting modification history will, however, not be available.
Continuous improvement
Although sunsetting classic meetings marks the completion of a planned transition to the new Meetings module, we will continue to add new features and optimize the design based on user feedback.
Very soon, we will be adding meeting backlogs, allowing you to “park” agenda items in a separate space for more efficient meeting planning. This includes a ‘series’ backlog that is shared with all occurrences of a meeting, enabling you to move things in and out of the backlog to particular occurrences.
We will also update the admin permissions model related to meetings to make them easier to understand and better adapted to new features.
Your feedback
Our motivation for all these changes is to enable teams to have more efficient, better-organized meetings. We extensively use the Meetings module internally at OpenProject and have received positive feedback from a number of our users.
Your feedback helps us know if we’re going in the right direction, if there are things we can improve on and what our users are missing.
As an open source software company, we value the ideas and feedback of our user Community. If you have opinions about these changes or have feature requests, feel free to join our Community instance and share your thoughts on upcoming features related to meetings.
Thank you for your continued support and for being a part of the OpenProject Community.
At OpenProject, we are continuously working to make our platform as accessible as possible for all users. A big part of that is offering our content in multiple languages. We are excited to announce that our website and user guides are now available in Portuguese!
OpenProject website in Portuguese
We’re happy to offer our Portuguese-speaking community a fully translated version of our website. While not all past blog articles will be translated, relevant new content will be published in Portuguese moving forward.
OpenProject user guide in Portuguese
Also, we have translated the OpenProject getting started guide as well as the user guide to Portuguese. These resources explain OpenProject’s features and functionality in detail, helping new and experienced users alike.
Documentation in other languages
In addition to Portuguese, OpenProject user guides are also available in:
OpenProject translations are managed publicly via Crowdin, and we welcome contributions from our global Community! You can help translate both the OpenProject application and the documentation.
We love seeing our community get involved — thank you for helping make OpenProject accessible to everyone!
You decided to take your project management to the next level and chose OpenProject as your open source project management software? You might be excited to get started. But as usual with a new tool: where to start? We put together an overview of the first steps to manage your projects in OpenProject. Please note that all steps described in this article require a project admin status.
Here’s an overview of this article for your quick navigation:
First of all, you would want to create a project. Log in to OpenProject and on the first page in the top left corner under Select a Project you can create a new project by clicking + Project.
Alternatively, on the same start page, in the Projects widget you can create a new project by clicking on the green + Project button. Please note that you can remove, add and change position of widgets on your project overview page.
Once you or other team members created some projects in OpenProject, you can log in and choose a project to open. In order to open an existing project, click the Select a project drop-down menu in the upper left corner of the header and select the project you want to open. You can also start by typing in a project name to filter by the project’s title.
Please note that you have to be a member of a project to be able to see and select it.
[!TIP]
You will also see a project if a work package from this project was shared with you, but in this case only the Work packages module and the shared work package will be visible to you within the project.
Project hierarchy
OpenProject allows you to organize your projects in a hierarchy by creating projects with subprojects. In order to create a subproject, you can do so in the project setting of the main project.
You can also create a project and define its parent project in the settings when creating a new project.
Projects and subprojects are displayed according to their hierarchy in the Select a project drop-down menu.
Project dashboard
In order to manage your projects successfully, you should make sure to be up to date about the status at all times. This allows you to keep the project on track and readjust quickly if needed. OpenProject’s project overview is a single dashboard page with important project information.
You can display relevant information for your team, such as members, news, project description, work package reports, or a project status. Remove or add project information as widgets to the dashboard, and order and re-size the widgets according to your needs.
There are several widgets to choose from, such as:
News,
Members,
Documents,
Project description,
Project status,
Spent time,
Calendar,
Subprojects,
Work packages graph, overview or table,
Custom text.
Project portfolio
To get an overview of all projects that you are involved in, you can check the status and more details under Project lists in the top left corner underneath Select a project. This overview shows you all projects with attributes such as status, latest activity and description. Use filters to customize the view and show the information you need. You can also create custom fields to add any custom information you want.
You might have noticed the yellow stars next to some projects in the screenshots above. These are favorite projects. Users can add projects to their favorites by either clicking the star icon in the project list (first column). Or by navigating to the project overview page and activating the star on the right upper corner. Favorites are personal and you don’t have to be an admin to use this feature.
Project templates
In order to save time and be coherent across projects, use the project templates in OpenProject. You just create a new project and then save it as a template. You can also make a project you are already working with a project template by changing the project settings to Set as a template. With a project template, you set up everything you want available for future projects, such as:
Project members,
Modules,
Default project structure in the Gantt chart,
Work package templates
and more.
Import tasks to OpenProject
In case you are managing your projects in Excel or any other project management software, OpenProject offers you an Excel Sync to upload your tasks into the OpenProject application. First export your tasks from the legacy project management system and then use the Excel Sync to upload them to OpenProject.
Organize and visualize your project
Projects vary and require a different view by project. Depending on what type of projects you are managing, you might want to use a work package table view, Agile Boards, Gantt charts, Backlogs, Task Board or a Roadmap. OpenProject offers both traditional and agile project management and allows you to combine both to a hybrid project management approach.
We would like to show you the major OpenProject modules that offer different project views. However, as mentioned, you can also combine them.
Work packages
Work packages are the base for your project collaboration in OpenProject. They are items in a project (such as tasks, features, risks, user stories, bugs, change requests – and any other type you want to create) and capture various additional attributes, such as status, assignee, priority, or due date. The work package table view shows all work packages as a list with selected attributes in the columns. You can customize the view by filtering by attributes and choosing the attributes shown in the columns, and then save your customized view.
Gantt charts
The Gantt charts module in OpenProject displays the work packages in a timeline. You can collaboratively create and manage your project plan. Have your project timelines available for all team members and share up-to-date information with stakeholders. You can add start and finish date and adapt it with drag and drop in the Gantt chart. Also, you can add dependencies, predecessor or successors within the Gantt chart.
Boards support agile project management methodologies, such as Scrum or Kanban. Our agile boards can be for anything you would like to keep track of within your projects: Tasks to be done, Bugs to be fixed, Articles to be reviewed, Features to be developed, Risks to be monitored, Ideas to be spread, anything! The boards consist of lists (columns) and cards.
You can choose between a Basic board (Community feature) and various Action boards (Enterprise add-on). The following board shows a Kanban example where you move your work packages from one status to the next. If you want to find out more about the different agile boards, please click here.
Backlogs
The starting point for effective work in Scrum teams is a well-maintained and prioritized product backlog as well as the creation of sprint backlogs. In OpenProject, you can easily record and specify requirements represented by user stories. Moreover, you can respond to inquiries and sort them by priority for implementation.
Task boards for Scrum meetings (Backlogs)
To support daily scrum meetings, all of a team’s tasks and sprint impediments are recorded in a digital task board. The digital task board thus allows team members to get a fast overview of the current state of a sprint.
Roadmap
Share your product roadmap with your stakeholders, get feedback about your ideas and break it down into a detailed release plan. In the roadmap, you can see all work packages and their status listed by versions at a glance. For each version, the related work package can be assessed from the list displayed in the roadmap view. Subjects which are crossed out represent closed work packages.
More support and information
We included quite a few links to our documentation in this article which also entails videos to make to easier for you to discover how to use OpenProject. If you would like to discover more videos, please check out the OpenProject YouTube channel.
Other guides and articles that might be helpful for you:
With a rich feature set comes a certain degree of complexity. That’s why good documentation matters, especially in the form of video tutorials that make it easier to learn and navigate OpenProject. In this article, we share our approach to high-quality documentation and video content, and ask our video production manager Dicle what makes a great OpenProject video.
High quality software documentation
When we ask our users what they love about OpenProject, we often hear great feedback about our documentation. This is encouraging because we believe in clear, well-structured, and complete documentation as the foundation for user success.
With monthly releases, we also update our documentation regularly. Of course, our product team strives to make OpenProject as intuitive as possible. But as the platform grows, some features require extra explanation. After all, software is only as good as users’ ability to make the most of it.
That’s why high-quality documentation — and especially helpful video content — is so important to us.
User documentation in English, German, Spanish and French
High-quality documentation starts with accessibility. That’s why key parts of our comprehensive documentation are available not only in English, our primary language, but also in German, Spanish, and French. This includes all user-focused guides designed to particularly support first-time users:
We will soon be providing user documentation in Portuguese as well. As our documentation expands each month, we take the time to ensure high-quality translations.
High quality video content: Tutorials, release overviews and more
To further enhance our documentation and website content, we welcomed a dedicated video producer to our team in January 2025, Dicle Naz Tohumcu. With her expertise in video content, she creates engaging tutorials, walkthroughs, and release overviews. Her videos help users quickly grasp OpenProject’s key features and workflows.
I’m from Ankara, Turkey, with a background in directing fashion, product, and commercial videos. Over time, my work has expanded into content production, with a focus on AI and digitalization.
What do you like about OpenProject?
The slogan “open source, open mind” perfectly captures its spirit, and that’s exactly what I love about OpenProject. The people here are open-minded and collaborative, and it’s exciting to contribute to a product that is constantly evolving.
What makes a good OpenProject video in your opinion?
The most important aspect is enhancing the user experience by clearly presenting new features and improvements. Our goal is to ensure users understand and benefit from updates while also highlighting team collaboration and workflow efficiency. I joined two months ago, and moving forward, one of my goals is to create a diverse range of videos that cover different aspects of OpenProject, using various formats and platforms to reach our audience in the best possible way.
We value user feedback
We’re always looking to improve our documentation and video content. Is there a tutorial you’d like to see, or a topic that needs more explanation? Let us know by commenting on our YouTube videos or joining the discussion in our Community forums.
Whether you’re moving from Docker to a package-based installation, changing databases, or upgrading an older setup, migrating your OpenProject installation can raise important questions. To help you navigate the process, we’ve compiled an overview of supported migration paths, key considerations, and links to detailed documentation. This article gives you the big picture. For in-depth instructions, please refer to our documentation.
OpenProject supports several installation methods: Docker, DEB/RPM packages, Helm Charts for Kubernetes, and manual installations. Depending on your infrastructure and technical requirements, one setup may suit you better than another.
For most users, we recommend the Docker-based installation. It’s the easiest to set up, requires minimal system configuration, and is simple to maintain — especially when updating to new OpenProject versions. This makes Docker the most future-proof option.
Important
We will not build packages for new Linux versions (such as Ubuntu 24.04). We will, however, keep releasing new package versions for the currently supported Linux versions until their EOL (end of life). Learn more in our packaged installation documentation.
Migration between Docker and packaged installations
It is possible to migrate between Docker and packaged (DEB/RPM) installations in both directions. In both cases, the process involves:
Exporting the PostgreSQL database,
Copying attachments and configuration files,
Re-importing the data in the new environment.
You might consider migrating to a packaged installation if your IT environment requires tight system-level integration, custom deployment configurations, or traditional OS-based monitoring tools. In this case, please follow this detailed guide in our documentation: Migrating your packaged OpenProject installation to another environment.
On the other hand, migrating from a packaged installation to Docker is a future-proof choice. It simplifies upgrades and deployments — especially since OpenProject will no longer release packages for newer OS versions such as Ubuntu 24.04, and recommends Docker-based installations for long-term use. To switch from packaged to Docker installation, please see this detailed guide in our documentation.
Migration to Kubernetes (Helm)
Migrating to Kubernetes using Helm charts is a powerful option for teams that need to scale OpenProject in dynamic environments or integrate it into an existing Kubernetes infrastructure. This setup is especially relevant for DevOps teams managing multiple services in containers.
Helm-based deployments are ideal for teams with Kubernetes experience. If you’re new to Kubernetes, consider evaluating Docker first — it provides a more accessible starting point with fewer moving parts.
OpenProject uses PostgreSQL as its database backend. If you’re upgrading PostgreSQL (for example, from version 10 to version 13), you’ll need to migrate the database using a controlled process to avoid data loss or compatibility issues.
We provide specific documentation depending on how OpenProject was installed:
Make sure to create a full backup before performing any PostgreSQL migration.
Tip
Instead of upgrading the database in place, we recommend doing a backup of OpenProject and restoring it on a newly installed database with the newer version where possible.
Migration from an old MySQL database
If you’re using a much older version of OpenProject, you may not be able to directly upgrade to the current version. In that case, we recommend a fresh installation of the latest version and a manual migration of your data.
Most migrations between installation types are technically straightforward — especially with a clear plan and the right tools. Always make sure to consult our installation documentation and follow our backup and restore guide before making changes.
If you have questions or want to exchange with other users, feel free to ask in the Community forum.
We are thrilled to announce that OpenProject has once again been recognized by Gartner Digital Markets in 2025, earning accolades across multiple platforms for our unwavering commitment to excellence in project management solutions.
Gartner Digital Markets is a Gartner business unit composed of Capterra, GetApp, and Software Advice. It is the world’s premier source for software vendors to connect with in-market buyers, through research, reviews, and lead generation.
In 2025, OpenProject has been honored with the following distinctions:
In 2024, OpenProject achieved an impressive overall score of 4.5 out of 5 across all three Gartner Digital Markets platforms: Capterra, GetApp, and Software Advice. This year, we have continued to build on that success, higher improving our rating to 4.6 out of 5, maintaining our high standards and dedication to our users. Our consistent recognition by Gartner Digital Markets is a testament to the trust and satisfaction of our user community.
Gratitude to our Community
We extend our heartfelt gratitude to our users for their continuous support and valuable feedback. Your insights drive us to innovate and improve, ensuring that OpenProject remains at the forefront of project management solutions.
As we celebrate these achievements, we remain committed to empowering teams worldwide with robust, reliable, and innovative project management solutions.
Want to review OpenProject yourself?
We greatly appreciate your valuable feedback and look forward to many more reviews.
How do cities and municipalities keep track of internal tasks, complaints, and maintenance requests? Without a structured solution, delays, unclear responsibilities, and high coordination efforts arise. OpenProject provides a digital ticket management solution for municipalities that simplifies processes and increases transparency. Read this article to learn how to use OpenProject as ticket management, on the example of a German city administration.
Why digital ticket management is essential for public administration
Digital ticket management is more than just processing inquiries. Many municipalities still record daily tasks and internal reports via email, phone, or Excel spreadsheets — often with unclear responsibilities and long processing times.
Every day, cities and municipalities must coordinate numerous inquiries, complaints, and tasks:
Citizens report issues such as noise disturbances or illegal waste disposal.
Public buildings need maintenance and management.
Public order services coordinate operations within the city.
Yet, many municipalities still lack a structured solution for internally recording, processing, and assigning these tasks. Instead, they rely on emails, Excel sheets, or even paper notes — leading to high coordination efforts, unclear responsibilities, and delays.
What happens internally to these tickets once they are created? How can it be ensured that they are efficiently assigned to the right personnel with the necessary capacity and expertise? And how do we ensure that all essential information is included?
OpenProject: More than just project management
A digital ticket management system like OpenProject solves exactly this problem. Employees can record tasks in a structured manner, assign them directly to the right people, and track progress — efficiently, transparently, and without complex IT integration.
OpenProject is more than a traditional project management tool — and also more than a classic ticketing system. The software combines both approaches in a way that suits the users’ needs. While typical ticketing systems are mostly designed for external requests, OpenProject focuses on internal organization and processing of tasks.
This makes OpenProject an ideal solution for municipalities to manage daily administrative tasks and internal processes more efficiently — whether for citizen inquiries, building maintenance, or deployment planning:
Flexible configuration: Custom workflows tailored to different municipal departments.
Structured recording: Tickets contain all relevant information from the start.
Transparent processing: All stakeholders can track status and next steps.
No media disruption: Communication and documentation happen directly in the system — without email clutter or files like “Ticket-2338-in-progress-2”.
Due to its high configurability, OpenProject allows great flexibility for users.
Best practice: How a city administration uses OpenProject for digital ticket management
To illustrate how this works in practice, let’s look at an example: Think of a typical German city administration that handles inquiries via emails, phone calls, and Excel spreadsheets. As this is a time-consuming and error-prone process, the city wants to introduce digital ticket management and decided to use OpenProject.
The city administration now centrally uses OpenProject for ticket management — from complaints in the public order office to building maintenance. With OpenProject as its central ticket management platform, the city administration is now able to:
Record and prioritize complaints and inquiries centrally.
Clearly define responsibilities and deadlines.
Track the processing status in real-time.
Work more efficiently and transparently.
Now, let’s dive deeper into the praxis and look at two concrete practical examples: How does this German city use ticket management in the area of public order services and in building management?
Use case: Ticket management for public order services
The public order office of our example city uses OpenProject to manage daily operations and complaints efficiently:
Incoming complaints (e.g., noise disturbances, illegal parking, waste issues) are recorded as tickets and automatically assigned to the responsible staff.
Task scheduling is managed through an agile board with priorities and deadlines.
Employees document progress in real-time, including evidence or notes directly in the ticket.
Citizen inquiries are handled faster and more transparently.
The advantage of OpenProject as a digital ticket system for public order services: Less coordination effort, faster processing, and transparent tracking.
Example: Managing a noise complaint with OpenProject
Here’s how a noise complaint could be processed using OpenProject:
A citizen reports repeated nighttime noise disturbances from a bar.
A public order officer logs the complaint as a work package of type ‘Ticket’ in OpenProject.
The department head prioritizes the case and assigns the work package to an on-site inspector.
The inspector conducts an on-site check and documents the findings within the ticket.
The status is updated to ‘Resolved’, with additional details added to the ticket’s activity log. The department head, tagged in the entry, automatically receives a notification.
If necessary, the bar is informed and a follow-up inspection is planned — a new work package is created, with a date and automatic reminder for a review in a few weeks.
Here’s how such a noise complaint ticket could look like in OpenProject:
Image: A work package in OpenProject, type ticket, named ‘Lärmbeschwerde: Bar Westend’, with discussions in the Activity tab, priority high and a set end date.
Use case: Ticket management for building maintenance
A municipal administration has to manage and maintain many buildings. This is another great example on how to use OpenProject as digital ticket management software:
Each maintenance request or issue is logged as a ticket and assigned to the responsible team. Automated reminders ensure that regular inspections and maintenance are carried out on time. Priority repairs (e.g., defective heating in winter) can be handled immediately. The administration maintains a complete record of all completed actions. And all data, communication and information is centralized in the ticket.
The advantage of OpenProject as a digital ticket system for facility management: Structured maintenance planning, no overlooked tasks, and better resource allocation.
The city administration can configure OpenProject so that each building is represented via work package types, subdivided by building category. All tasks for these buildings - from repairs to regular inspections - are created directly in the system as associated subtasks and assigned to the responsible team members for processing. No need to search through lists or Excel sheets. And, of course, automated reminders – in-app and/or per email – prevent forgotten maintenance tasks.
An example of a simple agile status board with tickets in OpenProject could look like this:
Image: An agile status board with tickets of types like ‘Stadtmuseum’ or ‘Kita Regenbogenland’, sorted by status.
Example: Managing a heating repair in an elementary school
Here’s how a heating repair could be handled in OpenProject:
The facility management team logs the issue as a work package of type ‘Ticket’ and adds the school name as a custom field of type ‘Building’.
The responsible janitor, added as an external person, receives a notification.
The repair is documented within the ticket, including photos and notes.
Once completed, the ticket is closed and serves as a permanent record.
Why OpenProject is the ideal ticket management solution for public administrations
There are many software options for task and ticket management. With its open source approach and hosting in Europe, OpenProject is an excellent choice for European municipalities and government agencies.
Why OpenProject is the ideal ticket management solution for the public sector:
Easy implementation and no complex IT integration.
Open source and GDPR-compliant — developed for European administrations.
Choice between secure cloud solutions or self-hosting.
Flexible customization — from facility management to public order offices.
Open source and independent — no vendor lock-in with U.S.-based providers.
Part of openDesk — the digital workplace solution for public institutions.
Not just anyone can become a European Capital of Culture. Since 1985, the European Union has awarded this title to cities whose applications were convincing in six criteria of a multi-year selection process. These include long-term strategy, European dimension, cultural and artistic content, but also the ability to implement the project and the successful involvement of society and administration.
A city who manages to do this proves that they are capable of managing the largest and most complex projects, and Chemnitz in Saxony has achieved this: in 2025, Chemnitz proudly bears the title of “European Capital of Culture”, accompanied by a long list of events.
Out of the silos, a single source of truth was needed
Alexander Hoffmann is responsible for digitalization in Chemnitz. Hoffmann has a background in IT project management, was originally trained as a classic project manager (IT), but later switched to agile project management and attaches great importance to using the right approaches and tools for the job. “The added value lies at the process level,” he explains. Many years ago, he took on the task of setting up project management at the City of Chemnitz’s IT department. “There were a lot of projects that had to be implemented and there still are - and we had to get out of the silos.” And that’s where OpenProject came in. Hoffmann was already familiar with the software and also has direct and close contact with Chemnitz Hospital, which also uses OpenProject.
Alexander Hoffmann is Head of Digitization and Development at the Office for Information Processing of the City of Chemnitz
The most important motivation behind the project management in OpenProject is also to promote the digitalization of the City of Chemnitz internally and externally and also to provide the platform for other municipal projects, such as residents’ meetings or construction projects, of the City of Chemnitz. To this end, Chemnitz operates a self-hosted instance of OpenProject, in-house and completely in the city network. 2500 potential users could register and work with it, and there are also plans to offer the software to external partners and connect it to Nextcloud. The approach to open source is not ideological, but very pragmatic. Chemnitz also uses around 200 MS Project licenses, of which around one hundred will probably remain. The approach does not follow any ideology “If we halve the number, we will have recouped the costs for OpenProject,” says Hoffmann happily.
Low entry barriers with open source
Open source as a value in itself is also playing an increasingly important role as a decision-making factor in Chemnitz. “If we can use open source software, then we combine two opportunities: the entry barrier is lower, we can test and evaluate software without consultants, tenders and thoughts about purchasing licenses. This flexibility alone makes it worthwhile for us to increasingly rely on open source software.”
And the fact that the IT architecture for open source software are transparent and comprehensible from the outset also plays a major role. “Whenever we make a purchase, we always check whether there are open source options, which is the first step for all cross-sectional applications, including project management. This is also a question of security,” confirms Hoffmann. “And the fact that we can always use free software solutions the way we want plays a role. It also has to be self-hosted; in many cases, externally hosted clouds are no (longer) an option.”
Implementation of the Digital Agenda
Chemnitz is not alone in this, but the topics of the Digital Agenda, such as the Online Access Act or the e-file and how access for citizens and stakeholders can be created in practice, are also on Hoffmann’s mind day in, day out. “Every e-file that we introduce is a project in a clearly defined tree structure. The “Digital Agenda” is the overarching element in OpenProject and each pillar is a sub-project.
Image source: City of Chemnitz, Roadmap of Digital Agenda
OpenProject is very well suited for this and we can also use it to directly inform the top management. They get an up-to-date status quickly and easily without us having to write extra reports.” Mayors who can read along directly in project management sounds unusual, and of course “we prepare the views for the decision-makers, but since we have introduced the software, it has made our work much easier.”
Project templates reduce workload to a fifth
For implementing these challenging goals, there are project managers who maintain the projects and keep their status up to date. Project templates in OpenProject (e.g. for the e-file) help to reduce the effort for new projects to 20% during planning. Chemnitz uses templates, checklists, wiki articles, and more in OpenProject, so that a project manager only has to adapt the project plan according to the new project.
Image source: City of Chemnitz, project template e-file in OpenProject
“It’s a matter of a few hours, and it frees up the project managers to concentrate on managing the teams and projects. They’re all happy for every bit of administrative work they’re spared,” shares Hoffmann.
Image source: City of Chemnitz, example work package template e-file in OpenProject
Although Chemnitz also operates a separate wiki, the wiki in OpenProject is used for all project-specific content. Time recording is also used, but only in the sense of overall time recording, i.e. estimated for projects, with a target/actual comparison for rough resource planning and personnel requirements planning. Meetings are also planned in OpenProject, “the project management software serves as a single source of truth for the many participants.”
Waterfall and agile: boards, tasks, sprints
Chemnitz combines classic project management with agile methods for its project work. Boards and tasks are used in the projects, even if “the projects of the Digital Agenda are mostly organized in a classic way, development assignments are managed agile with backlogs, roadmaps, sprints, sprint planning and so on. We use both approaches, including hybrid ones,” explains the department head. “Not all employees always use all the options that we and the software offer, nor do they have to. We have the backlogs module, but not everyone needs the burn-down and burn-up charts, story points, and sometimes the employee rights also prevent us from using various approaches, for example if this would make performance control and monitoring possible. But we work a lot with the basics, such as epics and the like.”
Configurable down to the last detail
The administration of the European Capital of Culture is also innovative: it defines its own project types and more and more using the project lists in OpenProject. The developers of OpenProject are now working on project phases, a feature that Chemnitz configured via tasks and milestones and thus automatically fills the timeline. This then almost automatically displays “endangered” projects or extended attributes, for example criteria such as “This is an important infrastructure project”. In a current project, the City of Chemnitz is currently introducing a new work package type “project” - this is also possible due to the flexible open source nature of the software.
Hundreds of projects at work
There are currently 345 projects being planned in Chemnitz, around 116 of which are active, and of which around 60 percent are digitalization projects. Other IT projects make up almost the entire remainder.
“The Digital Agenda in particular has led to a huge increase in projects. Many new projects are only named in the beginning. They are given a short title and classification and still have to go through the process of specification to become a real ‘project’”. Only when the stakeholders and milestones and everything else have been defined clearly are the projects fully implemented in OpenProject.
In the past, all of this was kept in Excel, but today the plans are already available in OpenProject via a link and are waiting to become a project at some point. “The many necessary budget processes beforehand make this necessary - and we can’t yet map them properly. But we are hopeful that we will be able to map this with a ‘project’ work package type at some point.”
Open source is more flexible than the proprietary competition
The conscious decision to use project templates for almost all project types makes everyday life easier for employees and managers. “It is now also a very conscious and comprehensible decision as to when a work package type becomes a project.” Once this is done, the project manager, for example, is also appointed straight away. “We have two views implemented in OpenProject: On the one hand, IT project planning with work package view ‘Project’ and the project list itself. This allows us to mix agile and classic projects - that’s priceless flexibility, not at all like the tight corset imposed by the proprietary competition.”
With OpenProject, Chemnitz has not only found the right tool to manage hundreds of projects efficiently but also created a sustainable foundation for future collaboration and innovation. By integrating the open source project management software into their digital strategy, the city is proving that transparency, flexibility, and self-reliance are key to successfully managing the Digital Agenda and the European Capital of Culture 2025.
Login
