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.

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!

a harmful microorganism, typically a bacterium.

Should be fixed if time permits but can be postponed.

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

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.

The project team is not able to reproduce the error.

creating/improving documentation

issues that add new functionality

Improvement of existing features

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

unit testing, performance testing, ...

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

The issue is in a preliminary state, it could be a possible idea that needs to mature.

Suitable for a master thesis topic

Issues with IDEs, OSs -- typically external tools

Support Answering questions

the issue is verified/reproduced by the project