We need good motivating use cases for this issue. Tell us (with a clear example) why this issue is this a good idea to do?

We welcome help on this issue!

This issue should be suitable for those without in-depth knowledge of the project. The issue typically requires only knowledge of common languages and technologies.

Issues with IDEs, OSs -- typically external tools

unit testing, performance testing, ...

Support Answering questions

Git repos, CI, release management, deployment, ...

issues that add new functionality

Improvement of existing features

creating/improving documentation

a harmful microorganism, typically a bacterium.

Non-critical functionality of your software is affected, and the issue may have a workaround.

An issue that results in complete loss of functionality and has no workaround, or; part of your application or software doesn’t do what it’s specifically designed to do; there may be a workaround.

Should be fixed if time permits but can be postponed.

An urgent problem that blocks the system use until the issue is resolved.

Suitable for a master thesis topic

A closing action, we won't fix it -- or we do not accept the feature request.

the issue is verified/reproduced by the project

The issue is on hold for some reason, which should be described in comments.

Typical use is for closing features or ideas that are no longer relevant. Obsolete issues can be reopened if they become relevant again.