# _embedded.elements[].description.raw
In this project we create an integration between the test management system [SquashTM by Henix](https://www.squashtm.com/en) and OpenProject. SquashTM is already integrated with Jira. And Jira, ever more often, is replaced by OpenProject. Thus, an integration between SquashTM and OpenProject makes a lot of sense.

# _embedded.elements[].description.html
In this project we create an integration between the test management system SquashTM by Henix and OpenProject.

SquashTM is already integrated with Jira. And Jira, ever more often, is replaced by OpenProject. Thus, an integration between SquashTM and OpenProject makes a lot of sense.

# _embedded.elements[].description.raw
**Jira exit** is an initiative designed to capture and document the needs, challenges, opportunities and requirements of teams transitioning from Atlassian's Jira Data Center to OpenProject. Are you a Jira user? Please share your feedback and thoughts with us and shape OpenProject together with our team.

Since Atlassian has announced the end-of-life of Jira & Confluence Data Center for March 28, 2029 many companies are currently looking for self-hosted open source alternatives to the Atlassian suite. 

If your organization depends on Jira & Confluence Data Center, you have to act now. The good news is, we are here to guide you on this migration journey.

# _embedded.elements[].description.html
Jira exit is an initiative designed to capture and document the needs, challenges, opportunities and requirements of teams transitioning from Atlassian's Jira Data Center to OpenProject. Are you a Jira user? Please share your feedback and thoughts with us and shape OpenProject together with our team.

Since Atlassian has announced the end-of-life of Jira & Confluence Data Center for March 28, 2029 many companies are currently looking for self-hosted open source alternatives to the Atlassian suite.

If your organization depends on Jira & Confluence Data Center, you have to act now. The good news is, we are here to guide you on this migration journey.

# _embedded.elements[].description.raw
You can track and follow-up incidents and service requests across teams with clear workflows and full traceability.

Track and manage IT services efficiently with OpenProject:

*   Incident and request tracking – Capture, assign, and resolve issues across teams.
    
*   Create and maintain an inventory for your organization.
    
*   Change and Release Management – Control changes and deployments with structured workflows.
    
*   Service transparency – Ensure accountability and visibility across the full service lifecycle.
    
*   Mailboxes & incoming emails – Automatically create and update tickets from shared inboxes.

# _embedded.elements[].description.html
You can track and follow-up incidents and service requests across teams with clear workflows and full traceability.

Track and manage IT services efficiently with OpenProject:

Incident and request tracking – Capture, assign, and resolve issues across teams.

Create and maintain an inventory for your organization.

Change and Release Management – Control changes and deployments with structured workflows.

Service transparency – Ensure accountability and visibility across the full service lifecycle.

Mailboxes & incoming emails – Automatically create and update tickets from shared inboxes.

# _embedded.elements[].description.raw
Here we coordinate the development of the XWiki integration in OpenProject.

# _embedded.elements[].description.html
Here we coordinate the development of the XWiki integration in OpenProject.

# _embedded.elements[]._links.ancestors[].title
Undisclosed - The ancestor is invisible because of lacking permissions.

# _embedded.elements[]._links.parent.title
Undisclosed - The parent is invisible because of lacking permissions.

# _embedded.elements[].description.raw
To enable a seamless migration from Jira and close critical feature gaps, we are strengthening OpenProject’s core capabilities by introducing and refining essential Jira fundamentals, including:

*   Labels field - Introduction of Labels fields for work packages.
    
*   Versions and release management - Adjustment of the concept of versions.
    
*   Advanced workflow configuration - UX improvements for workflow configuration and custom workflows in projects.
    
*   Project IDs and issue key handling - Independent work package keys per project.

# _embedded.elements[].description.html
To enable a seamless migration from Jira and close critical feature gaps, we are strengthening OpenProject’s core capabilities by introducing and refining essential Jira fundamentals, including:

Labels field - Introduction of Labels fields for work packages.

Versions and release management - Adjustment of the concept of versions.

Advanced workflow configuration - UX improvements for workflow configuration and custom workflows in projects.

Project IDs and issue key handling - Independent work package keys per project.

# _embedded.elements[].description.raw
**Purpose of this project**  
This project focuses on further improving OpenProject's support for agile methodologies (Scrum, Kanban, SAFe).

**Product vision**  
Here you can find a detailed vision for agile way of working within OpenProject:  
[https://www.openproject.org/blog/future-of-agile-work/](https://www.openproject.org/blog/future-of-agile-work/) 

**Project goals**

*   Better support for agile artefacts and ceremonies (backlog grooming, sprint planning, retrospectives)
    
    *   Sprint scheduling, start and completion (incl. sprint status)
        
    *   Improved backlog view
        
    *   Automated backlog (showing per default all work packages from the project, except closed and rejected work packages)
        
*   Further improvements for agile boards aligned with agile principles
    
    *   Swimlanes
        
    *   Quick filters
        
    *   Status mapping
        
    *   Automated sprint boards
        
*   Establish agile reports to measure team health and maturity in order to boost continuous improvements
    
    *   burnup charts
        
    *   burndown charts
        
    *   velocity charts
        
    *   number of cards planned, added, completed

# _embedded.elements[].description.html
Purpose of this project
This project focuses on further improving OpenProject's support for agile methodologies (Scrum, Kanban, SAFe).

Product vision
Here you can find a detailed vision for agile way of working within OpenProject:
https://www.openproject.org/blog/future-of-agile-work/

Project goals

Better support for agile artefacts and ceremonies (backlog grooming, sprint planning, retrospectives)

Sprint scheduling, start and completion (incl. sprint status)

Improved backlog view

Automated backlog (showing per default all work packages from the project, except closed and rejected work packages)

Further improvements for agile boards aligned with agile principles

Swimlanes

Quick filters

Status mapping

Automated sprint boards

Establish agile reports to measure team health and maturity in order to boost continuous improvements

burnup charts

burndown charts

velocity charts

number of cards planned, added, completed

# _embedded.elements[].statusExplanation.raw
The backlog view now intuitively remains on the left, while Sprints are displayed on the right.

*   All work packages, except those _Closed_ or _Rejected_, are now automatically populated into the Backlog.
    
*   **Sprint bucket** creation has been introduced for organization and planning.
    
*   Sprint boards and burndown charts are automatically generated whenever a sprint becomes active.
    
*   Move and sorting options have been added.
    

**For version 17.4**

*   **Backlog buckets** have been introduced to support backlog refinement process.
    
*   Work packages can be moved into created backlog buckets.
    
*   A **start** and **completion** button is displayed on the sprint header.
    
*   Letting go of the **drag handle** to ensure possibility of moving an entire card.
    
*   Improved move and sorting options to include "move to sprint".

# _embedded.elements[].statusExplanation.html
The backlog view now intuitively remains on the left, while Sprints are displayed on the right.

All work packages, except those Closed or Rejected, are now automatically populated into the Backlog.

Sprint bucket creation has been introduced for organization and planning.

Sprint boards and burndown charts are automatically generated whenever a sprint becomes active.

Move and sorting options have been added.

For version 17.4

Backlog buckets have been introduced to support backlog refinement process.

Work packages can be moved into created backlog buckets.

A start and completion button is displayed on the sprint header.

Letting go of the drag handle to ensure possibility of moving an entire card.

Improved move and sorting options to include "move to sprint".

# _embedded.elements[].description.raw
This stream is focused on bringing intelligent, AI-powered capabilities into OpenProject to help teams work smarter and more efficiently.

# _embedded.elements[].description.html
This stream is focused on bringing intelligent, AI-powered capabilities into OpenProject to help teams work smarter and more efficiently.

# _embedded.elements[].statusExplanation.raw
**Roadmap**

Epic

Status

Why

Quarter

##62781

Done

Help companies to connect Agentic workflows with OpenProject

2025 Q4 - 2026 Q1

##62215

In development

OpenProject's own LLM infrastructure to not rely on third party providers

Q2 2026

##73261

In specification

To empower AI assistants to not just read OpenProject data, but also act on it

Q3 2026

##66020

Specified but needs refinement

Needed as basis to enable AI for Blocknote

##69620

Creating POC

Find your work packages without remembering specific terms

##69621

Save double work. Find similar work packages already

##69622

Bring work packages into the right format (and add tips)

# _embedded.elements[].statusExplanation.html
Roadmap

Epic

Status

Why

Quarter

Done

Help companies to connect Agentic workflows with OpenProject

2025 Q4 - 2026 Q1

In development

OpenProject's own LLM infrastructure to not rely on third party providers

Q2 2026

In specification

To empower AI assistants to not just read OpenProject data, but also act on it

Q3 2026

Specified but needs refinement

Needed as basis to enable AI for Blocknote

Creating POC

Find your work packages without remembering specific terms

Save double work. Find similar work packages already

Bring work packages into the right format (and add tips)

# _embedded.elements[]._links.ancestors[].title
Undisclosed - The ancestor is invisible because of lacking permissions.

# _embedded.elements[]._links.parent.title
Undisclosed - The parent is invisible because of lacking permissions.

# _embedded.elements[].description.raw
In this project we organize the development of generic BlockNote extensions that shall be used within OpenProject but also within other 3rd party applications using BlockNote integrating with OpenProject.

# _embedded.elements[].description.html
In this project we organize the development of generic BlockNote extensions that shall be used within OpenProject but also within other 3rd party applications using BlockNote integrating with OpenProject.

# _embedded.elements[]._links.ancestors[].title
Undisclosed - The ancestor is invisible because of lacking permissions.

# _embedded.elements[]._links.parent.title
Undisclosed - The parent is invisible because of lacking permissions.

# _embedded.elements[].description.raw
In this project we organize the development of generic BlockNote extensions that shall be used within OpenProject but also within other 3rd party applications using BlockNote integrating with OpenProject.

# _embedded.elements[].description.html
In this project we organize the development of generic BlockNote extensions that shall be used within OpenProject but also within other 3rd party applications using BlockNote integrating with OpenProject.

# _embedded.elements[].name
Stream Jira to OpenProject data Migrator

# _embedded.elements[].description.raw
We want to make it simple to migrate from other project, work and issue management tools to OpenProject. And we will focus on Jira (Atlassian), first.

We know that that migrating from Jira is not a small challenge. Jira and its ecosystem is big. However, the user base of Jira is also big. And many have a strong interest to migrate to OpenProject as it is Open Source, it offers real data sovereignty and it is frees from vendor lock.

We would like to encourage the community to support us with this work. The more the better:

*   Checkout the [development roadmap of the Jira Migrator tool](https://community.openproject.org/projects/jira-migration/work_packages?query_id=6777).
    
*   Get in contact with us. Please write an email with the subject 'Joining community' to [support@openproject.com](mailto:support@openproject.com), if you would like to join our community. We will then invite to this instance you as soon as possible.
    
*   Test our early versions and [give us feedback](https://community.openproject.org/projects/jira-migration/work_packages/create_new?type=149).
    
*   Donate data that we can use for testing our migrations. [Share your files privately here](https://nextcloud.openproject.org/s/yLyH4RTtdTnyPFB) and let us know by [creating a FEEDBACK work package](https://community.openproject.org/projects/jira-migration/work_packages/create_new?type=149).
    
*   Contribute code. Fork the [repository on GitHub](https://github.com/opf/openproject) and get started.
    

**Out of scope of this project**

The Migrator currently focusses on migrating projects and workspaces and not yet on configurations. 

Also, the Migrator can only import those objects that have a representation in OpenProject. Checkout the general [development roadmap](https://www.openproject.org/roadmap/) for more information.

# _embedded.elements[].description.html
We want to make it simple to migrate from other project, work and issue management tools to OpenProject. And we will focus on Jira (Atlassian), first.

We know that that migrating from Jira is not a small challenge. Jira and its ecosystem is big. However, the user base of Jira is also big. And many have a strong interest to migrate to OpenProject as it is Open Source, it offers real data sovereignty and it is frees from vendor lock.

We would like to encourage the community to support us with this work. The more the better:

Checkout the development roadmap of the Jira Migrator tool.

Get in contact with us. Please write an email with the subject 'Joining community' to support@openproject.com, if you would like to join our community. We will then invite to this instance you as soon as possible.

Test our early versions and give us feedback.

Donate data that we can use for testing our migrations. Share your files privately here and let us know by creating a FEEDBACK work package.

Contribute code. Fork the repository on GitHub and get started.

Out of scope of this project

The Migrator currently focusses on migrating projects and workspaces and not yet on configurations.

Also, the Migrator can only import those objects that have a representation in OpenProject. Checkout the general development roadmap for more information.

# _embedded.elements[].statusExplanation.raw
Stay tuned: We ship new features with every monthly release of OpenProject, extending the capabilities of the Jira Migrator.

**Data Currently Supported**:

*   Projects
    
*   Issues (description, history, comments and attachments)
    
*   A subset of custom fields
    
*   Involved users and groups
    

**Comming soon (Q2 2026,** [Validate with official roadmap](https://community.openproject.org/projects/jira-migration/work_packages?query_id=6777)**)**:

*   Project identifiers
    
*   Issues identifiers
    
*   Relations between issues
    
*   Sprint assignments
    
*   Fix versions and Affected versions
    
*   Labels
    
*   Support for further custom field types (one at a time)
    

**Coming later**: 

*   Project-level workflows
    
*   Permissions
    
*   Schemas
    
*   Boards
    
*   Time tracking logs
    
*   Components
    
*   Jira Cloud migrations

# _embedded.elements[].statusExplanation.html
Stay tuned: We ship new features with every monthly release of OpenProject, extending the capabilities of the Jira Migrator.

Data Currently Supported:

Projects

Issues (description, history, comments and attachments)

A subset of custom fields

Involved users and groups

Comming soon (Q2 2026, Validate with official roadmap):

Project identifiers

Issues identifiers

Relations between issues

Sprint assignments

Fix versions and Affected versions

Labels

Support for further custom field types (one at a time)

Coming later:

Project-level workflows

Permissions

Schemas

Boards

Time tracking logs

Components

Jira Cloud migrations

# _embedded.elements[]._links.self.title
Stream Jira to OpenProject data Migrator

# _embedded.elements[].description.raw
Introducing another type of custom field "Calculated value". This requires:

*   Introducing the custom field
    
*   Enabling list custom fields to receive values

# _embedded.elements[].description.html
Introducing another type of custom field "Calculated value". This requires:

Introducing the custom field

Enabling list custom fields to receive values

# _embedded.elements[].description.raw
This project covers OpenProject's CLI utilities. These features emerged out of a passion project and are not part of the official roadmap. However, we invite you to share your feature requests, issues with the team, so that we can add further useful functionalities together.

⚠️ **Attention**

This tool is currently in a pre-release phase. It is not meant to be full-featured, complete, nor will it have official technical support by the OpenProject GmbH.

# _embedded.elements[].description.html
This project covers OpenProject's CLI utilities. These features emerged out of a passion project and are not part of the official roadmap. However, we invite you to share your feature requests, issues with the team, so that we can add further useful functionalities together.

⚠️ Attention

This tool is currently in a pre-release phase. It is not meant to be full-featured, complete, nor will it have official technical support by the OpenProject GmbH.

# _embedded.elements[].description.raw
Improving time tracking and reporting capabilities in OpenProject

# _embedded.elements[].description.html
Improving time tracking and reporting capabilities in OpenProject

# _embedded.elements[].description.raw
Core topics of this stream:

*   Scheduling
    
*   Gantt
    
*   Status reporting
    
*   Cost estimation
    
*   Budgets
    
*   Time tracking
    
*   PDF reports

# _embedded.elements[].description.html
Core topics of this stream:

Scheduling

Gantt

Status reporting

Cost estimation

Budgets

Time tracking

PDF reports

# _embedded.elements[].description.raw
Core focus of this stream:

*   Prioritization of projects
    
*   Project lifecycles (stages and gates)
    
*   Resource planning and allocation

# _embedded.elements[].description.html
Core focus of this stream:

Prioritization of projects

Project lifecycles (stages and gates)

Resource planning and allocation

# _embedded.elements[].description.raw
The purpose of this product development stream is to bundle all work necessary for integrating OpenProject with third party applications in a way that users can navigate seamlessly between them without any individual setup steps required. We strongly focus on implementing open standards:

*   Users shall be logged in and out centrally via OpenID Connect (OIDC).
    
*   Users shall be provisioned centrally from an idP (Identity provider) via SCIM.
    
*   Cross application requests impersonating users shall use JWT access tokens that were obtained centrally by the OIDC provider.
    

These efforts shall be reusable for many future cross application integrations to come, such as openDesk and Nextcloud, but also simplify future integrations, e.g. with XWiki.

The first integration we focus on is the integration with Nextcloud.

# _embedded.elements[].description.html
The purpose of this product development stream is to bundle all work necessary for integrating OpenProject with third party applications in a way that users can navigate seamlessly between them without any individual setup steps required. We strongly focus on implementing open standards:

Users shall be logged in and out centrally via OpenID Connect (OIDC).

Users shall be provisioned centrally from an idP (Identity provider) via SCIM.

Cross application requests impersonating users shall use JWT access tokens that were obtained centrally by the OIDC provider.

These efforts shall be reusable for many future cross application integrations to come, such as openDesk and Nextcloud, but also simplify future integrations, e.g. with XWiki.

The first integration we focus on is the integration with Nextcloud.

# _embedded.elements[].description.html
Coordinating the translations of OpenProject within Crowdin. To get started with translating OpenProject, please see https://www.openproject.org/docs/development/translate-openproject/

# _embedded.elements[].description.raw
The purpose of this product stream is to allow to structure, organize and manage work on files. This also includes integrations into file storage platforms such as Nextcloud and OneDrive/SharePoint.

### Imporant links

*   [Glossary](https://community.openproject.org/projects/document-workflows-stream/wiki/glossary)

# _embedded.elements[].description.html
The purpose of this product stream is to allow to structure, organize and manage work on files. This also includes integrations into file storage platforms such as Nextcloud and OneDrive/SharePoint.

Imporant links

Glossary

# _embedded.elements[].description.raw
Moving forward the meeting functionality in OpenProject.

We believe that good meetings are essential for team and project success. We aim to provide tools to easily have better prepared meetings with more people actively involved. People are less stressed as everybody can put their topic on the agenda whenever they come across a topic or work package that needs discussion.

# _embedded.elements[].description.html
Moving forward the meeting functionality in OpenProject.

We believe that good meetings are essential for team and project success. We aim to provide tools to easily have better prepared meetings with more people actively involved. People are less stressed as everybody can put their topic on the agenda whenever they come across a topic or work package that needs discussion.

# _embedded.elements[].description.raw
The purpose of this product stream is to constantly improve OpenProject’s capabilities to have successful communication on complex topics while allowing every participant to manage one’s own attention.

### Communicator team's responsibilities

*   Work package activities
    
    *   Comments
        
    *   Internal comments
        
    *   Inline attachments
        
*   Notification center
    
    *   Notification emails
        
*   Reminders
    
*   Documents
    
    *   Real-time text editing
        
    *   Legacy documents
        
*   Emoji reactions
    
*   Inbound emails
    
    *   Help desk
        
*   Text editor

# _embedded.elements[].description.html
The purpose of this product stream is to constantly improve OpenProject’s capabilities to have successful communication on complex topics while allowing every participant to manage one’s own attention.

Communicator team's responsibilities

Work package activities

Comments

Internal comments

Inline attachments

Notification center

Notification emails

Reminders

Documents

Real-time text editing

Legacy documents

Emoji reactions

Inbound emails

Help desk

Text editor

# _embedded.elements[].description.raw
Here we store public assets to be shared across community and elsewhere.

# _embedded.elements[].description.html
Here we store public assets to be shared across community and elsewhere.

# _embedded.elements[]._links.ancestors[].title
Undisclosed - The ancestor is invisible because of lacking permissions.

# _embedded.elements[]._links.ancestors[].title
Undisclosed - The ancestor is invisible because of lacking permissions.

# _embedded.elements[]._links.parent.title
Undisclosed - The parent is invisible because of lacking permissions.

# _embedded.elements[].description.raw
The Stream Mobile App (A-Team) takes care of the **OpenProject Mobile app.** Designed as a **companion application** to the OpenProject web and desktop experience. It allows you to:

*   **Access your work packages** and projects on the go.
    
*   **React and respond** quickly to updates, comments, and notifications.
    
*   **Stay informed** about project progress, tasks, and deadlines — anytime, anywhere.
    
*   **Track your work and log time** directly within the app to keep your reporting up to date.
    

The goal is to provide **lightweight mobile access** for essential collaboration and project management tasks, perfectly complementing the full web experience of OpenProject.

# _embedded.elements[].description.html
The Stream Mobile App (A-Team) takes care of the OpenProject Mobile app. Designed as a companion application to the OpenProject web and desktop experience. It allows you to:

Access your work packages and projects on the go.

React and respond quickly to updates, comments, and notifications.

Stay informed about project progress, tasks, and deadlines — anytime, anywhere.

Track your work and log time directly within the app to keep your reporting up to date.

The goal is to provide lightweight mobile access for essential collaboration and project management tasks, perfectly complementing the full web experience of OpenProject.

# _embedded.elements[]._links.ancestors[].title
Undisclosed - The ancestor is invisible because of lacking permissions.

# _embedded.elements[]._links.parent.title
Undisclosed - The parent is invisible because of lacking permissions.

# _embedded.elements[].name
Stream Matrix Hookshot - Element Integration

# _embedded.elements[].description.raw
Develop an integration using Matrix Hookshot for OpenProject in Element app.

# _embedded.elements[].description.html
Develop an integration using Matrix Hookshot for OpenProject in Element app.

# _embedded.elements[].statusExplanation.html
https://community.openproject.org/projects/openproject/work_packages/50676/activity

# _embedded.elements[]._links.self.title
Stream Matrix Hookshot - Element Integration

# _embedded.elements[].name
Stream Nextcloud app "OpenProject Integration"

# _embedded.elements[].description.raw
Here we coordinate the development of a Nextcloud app that tightly integrates with OpenProject. Please find the code [here on Github.](https://github.com/nextcloud/integration_openproject)

# _embedded.elements[].description.html
Here we coordinate the development of a Nextcloud app that tightly integrates with OpenProject. Please find the code here on Github.

# _embedded.elements[]._links.self.title
Stream Nextcloud app "OpenProject Integration"

# _embedded.elements[].description.raw
**Goal**

A consistent, intuitive and modern look and feel throughout the whole application based on the principles and components of our Primer design system.

<br>

**Tasks**

*   Develop and maintain design system components
    
*   Develop and implement design patterns within OpenProject
    
*   Support other teams in the usage of the components and patterns
    
*   Continously improve the accessibility of OpenProject
    

<br>

# _embedded.elements[].description.html
Goal

A consistent, intuitive and modern look and feel throughout the whole application based on the principles and components of our Primer design system.

Tasks

Develop and maintain design system components

Develop and implement design patterns within OpenProject

Support other teams in the usage of the components and patterns

Continously improve the accessibility of OpenProject

# _embedded.elements[].statusExplanation.raw
### **Roadmap**

<br>

#### **1) WorkPackage module**

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" style="width:75px;"><p class="op-uc-p">ID</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Title</p></th><th class="op-uc-table--cell op-uc-table--cell_head" style="width:120px;"><p class="op-uc-p">Status</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Quarter</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:71380:id</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:71380:subject</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:71380:status</p></td><td class="op-uc-table--cell"><p class="op-uc-p">2026 Q1</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:67012:id</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:67012:subject</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:67012:status</p></td><td class="op-uc-table--cell"><p class="op-uc-p">2026 Q2</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:55476:id</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:55476:subject</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:55476:status</p></td><td class="op-uc-table--cell"><p class="op-uc-p">2026 Q3</p></td></tr></tbody></table></figure><br>

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

####   

#### **2) Harmonizing the UI with Primer components**

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" style="width:75px;"><p class="op-uc-p">ID</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Title</p></th><th class="op-uc-table--cell op-uc-table--cell_head" style="width:120px;"><p class="op-uc-p">Status</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Quarter</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:56584:id</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:56584:subject</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:56584:status</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:56584:Roadmap</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:70725:id</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:70725:subject</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:70725:status</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:70725:Roadmap</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:60356:id</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:60356:subject</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:60356:status</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Continous effort</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:55520:id</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:55520:subject</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:55520:status</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Continous effort</p></td></tr></tbody></table></figure><br>

#####   

####   

####   

####   

####   

####   

####   

####   

#### 3) Accessibility

<br>

[Accessibility Report 2025](https://community.openproject.org/projects/design-system/work_packages?query_id=8005)

[Accessibility Report 2026](https://community.openproject.org/projects/design-system/work_packages?query_id=7930)

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" style="width:75px;"><p class="op-uc-p">ID</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Title</p></th><th class="op-uc-table--cell op-uc-table--cell_head" style="width:120px;"><p class="op-uc-p">Status</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Quarter</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:48530:id</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:48530:subject</p></td><td class="op-uc-table--cell"><p class="op-uc-p">workPackageValue:48530:status</p></td><td class="op-uc-table--cell"><p class="op-uc-p">Continous effort</p></td></tr></tbody></table></figure><br>

# _embedded.elements[].statusExplanation.html
Roadmap

1) WorkPackage module

ID

Title

Status

Quarter

2026 Q1

2026 Q2

2026 Q3

2) Harmonizing the UI with Primer components

ID

Title

Status

Quarter

Continous effort

Continous effort

3) Accessibility

Accessibility Report 2025

Accessibility Report 2026

ID

Title

Status

Quarter

Continous effort

# _embedded.elements[].description.html
Welcome to the OpenProject Documentation project to create a best-in-class multi-language documentation for OpenProject.

On GitHub: https://github.com/opf/openproject/tree/dev/docs

If you want to contribute, please have a look at https://www.openproject.org/docs/development/contribution-documentation/

Please also take a look at our list of spellings and translated terms before contributing to the OpenProject Documentation.

# _embedded.elements[].statusExplanation.html
Ongoing improvements and changes.

# _embedded.elements[].description.html
https://github.com/opf/OpenProjectExcel

# _embedded.elements[].description.raw
A Dockerfile that installs OpenProject. Take a look at the [Docker installation guide](https://www.openproject.org/docker/) for details.

# _embedded.elements[].description.html
A Dockerfile that installs OpenProject. Take a look at the Docker installation guide for details.

# _embedded.elements[].description.raw
**Welcome to the public development project of OpenProject.**

[**OpenProject**](https://www.openproject.org/) is free and open source project management software, licensed under GNU GPL v3. It supports classic, agile as well as hybrid project management. The source code is publicly available on [GitHub](https://github.com/opf/openproject).

What do you want to do?

*   [Report a bug](https://community.openproject.org/projects/openproject/work_packages/new?query_id=2649&type=1)
*   [Open a new feature request](https://community.openproject.org/projects/openproject/work_packages/new?query_id=180&type=6)
*   [View or post in OpenProject Community forum](https://community.openproject.org/projects/openproject/forums)
*   [View the release plan](https://community.openproject.org/projects/openproject/work_packages?query_id=918)

The Community edition can be downloaded and installed for free. For enterprise customers, OpenProject offers a hosted cloud edition as well as an on-premises edition with support, as well premium features, and additional security features.

Please [contact us](https://www.openproject.org/contact/) if you have any questions. We are always happy to help!

# _embedded.elements[].description.html
Welcome to the public development project of OpenProject.

OpenProject is free and open source project management software, licensed under GNU GPL v3. It supports classic, agile as well as hybrid project management. The source code is publicly available on GitHub.

What do you want to do?

Report a bug

Open a new feature request

View or post in OpenProject Community forum

View the release plan

The Community edition can be downloaded and installed for free. For enterprise customers, OpenProject offers a hosted cloud edition as well as an on-premises edition with support, as well premium features, and additional security features.

Please contact us if you have any questions. We are always happy to help!