This label is for issues that raises questions about our frontend or the design of our user-experience.

An issue that needs confirmation or more detailed information by testers who manage to reproduce it. OR: An issue that can be disproven (as e.g. outdated) by code observation.

Label the issue with this, if you are stuck and would like some help.

on hold as it needs discussion or decision within foodsharing (board, AMB-forum,...) ... let the product team have a crack at it?

Needs beta testing. Should be applied after a merge and removed after beta test tasks have been announced on #foodsharing-beta

Primary skill needed: flourish

Primary skill needed: php

Primary skill needed: vue

This only affects Orga-people. If your issue can only be resolved by orga: don't use this label; instead please tag/mention the orga persons!

Issue only reproducible on beta. Would move to production if we deployed the system in its current state!

Use this to denote a necessary migration. Might contain new rows / lines in the database.

This merge request has no (German) release notes description yet, but needs one

Primary skill needed: JS

This issue only affects some working groups, who have special rights on the platform.

An administrative task for the backoffice.

This issue must be resolved for a release to be possible. It is too critical to be neglected.