The issue has been patched, reviewed, and merged into the project.

The issue has been identified and is currently being patched, as part of the current development cycle.

The patch has been developed and is awaiting team review before final approval.

An issue/feature related to group communication features like group calls, messaging, and conferences. Also applies to the underlying connectivity layer facilitating group connections in the codebase.

The issue is a genuine and identified malfunction within the system, distinguishing it from a feature request, question, or refactoring.

An issue related to design processes and changes, including anything from UI/UX design, graphic design, to overall aesthetic improvements in Jami.

A ticket proposing a new feature or a significant enhancement. The issue should describe the problem, the proposed solution, and the benefits.

An issue that poses a question seeking clarification or information.

An issue focusing on code cleanup, refactoring, or improving existing functionalities in the app. Use the "type::feature request" label for substantial new features or enhancements.

An issue concerning manual testing and the implementation or improvement of automated tests, including smoke tests, to ensure application reliability.

An issue related to user interface (UI) or user experience (UX) design, encompassing layout, interaction, or visual presentation issues.

An issue for which a bug has been reported and for which the user must provide additional information. The ticket is pending until the user responds.

A compatibility, performance, or functionality issue encountered when using Wayland as the display protocol.

An issue related to Jami's account access page, including features such as account creation, logging in, setting up a rendezvous point, connecting to JAMS or a SIP account, and learning more about Jami.

An issue concerning unclear or potentially confusing text, labels, or naming conventions within the application.