PermaplanT Labels

Purpose: Document how our current GitLab labels are intended to be used so the team can give focused feedback on what’s missing, confusing, or unused.

Scope: Descriptive only (no changes yet). Missing descriptions are shown as —.

Last updated: 07.09.2025

Conventions

Scopes in use: status::…, type::…, priority::…, scope::…, target::…, meta::…, MRs::…, plus a few general labels.
Common combo on issues: one status::… + one type::… (+ optional priority::…, scope::…, documentation).
MRs::… labels are intended as status for merge requests.

Label Sopes

MR workflow (`MRs::…`)

Label	Intended use
`MRs::needs update`	An update due to a release or breaking change is needed, maybe merge of dev is enough.
`MRs::please merge`	Label for Merge Requests. Indicates the MR is ready to be merged from the author's point of view.
`MRs::please review`	Label for Merge Requests. Indicates that the MR is ready to be reviewed from the author's point of view.

Meta (`meta::…`)

Label	Intended use
`meta::help wanted`	Meta tag that can be used on MRs or issues if you wish to be supported by other team members.
`meta::workaround available`	—

Priority (`priority::…`)

Label	Intended use
`priority::later`	This issue has low priority and can be done at a later point in time, or if no other higher-priority tasks are available.
`priority::now`	This issue needs to be taken care of now and should not be postponed.
`priority::release critical`	This issue is critical for the upcoming release and should be prioritized accordingly.

Status (`status::…`)

Label	Intended use
`status::blocked`	This issue is currently blocked (by another issue or by some external factor) and work on it cannot continue until it's unblocked. (if the blocker is external, please add a comment to the issue explaining the situation)
`status::current sprint`	This issue is included in the scope of the current sprint and will be soon worked on.
`status::in progress`	This issue is currently being worked on.
`status::in review`	This issue has an associated MR and it is waiting for review.
`status::ready`	This issue has been described and is ready to be worked on.
`status::refine`	This issue still needs to be refined, and it is not ready to be worked on.

Type (`type::…`)

Label	Intended use
`type::bug`	This issue describes a defect.
`type::enhancement`	This issue regards adding some new functionality, like improving or expanding an existing feature, or implementing an entirely new feature.
`type::question`	This issue is for discussing an open question.
`type::refactor`	This issue regards the refactoring of existing code, to make things simpler or remove duplicated code. The functionality of the affected features should not change through this issue.

Target (`target::…`)

Label	Intended use
`target::dev`	Should be merged to development branch.
`target::master`	Should be merged to master branch.

Scope (`scope::…`)

Label	Intended use
`scope::CI`	This issue affects the continuous integration / pipeline.
`scope::auth`	This issue affects the authentication service.
`scope::backend`	This issue affects the backend code.
`scope::e2e`	This issue affects the End-to-end testing.
`scope::estimation needed`	—
`scope::frontend`	This issue affects the frontend code.
`scope::nextcloud`	This issue affects the Nextcloud configuration.
`scope::performance`	—
`scope::pm`	This issue affects the project management
`scope::scraper`	This issue affects the Scraper tool.
`scope::triage needed`	An evaluation of what part of the initiative this issue affects is needed.

General (unscoped)

Label	Intended use
`documentation`	This issue affects the documentation.
`duplicate`	—
`project`	Issues belonging to a specific project.
`usability`	This issue affects the usability of the application.
`wontfix`	—