You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to implement as few labels as possible at the beginning and add new as we need them. Based on prior experience, the below labels could be part of an initial proposal:
Status scale:
Backlog: default state on Gitlab so no label needed.
Todo: processed elements that should be done in the future.
Doing: WIP
Review: items that are under review once the developer or contributor has finished it.
Closed: items that has been processed and canceled, finished or no longer apply. For this state no label is required.
Severity scale:
No label: unprocessed item.
Important: default severity for processed items that should be executed/considered.
Urgent: to pay attention in the immediate future when possible.
Critical: topics that require attention immediately when possible.
Impact scale:
high_impact: the crash/feature/task takes place frequently or is a recurrent one and has a significant impact on users everyday's or key work.
No label: the crash/feature/task is infrequent or hard to reproduce and the impact on the users is low or hard to determine.
Topic labels: each repository has its own labels that allow to structure tickets per topic.
bug
enhancement
Other could be proposed and added as needed.
The above scales, together with the milestones, would allow us to create several boards to visualize the current state of the project in a simple way.
The idea is to implement as few labels as possible at the beginning and add new as we need them. Based on prior experience, the below labels could be part of an initial proposal:
Status scale:
Severity scale:
Impact scale:
Topic labels: each repository has its own labels that allow to structure tickets per topic.
Other could be proposed and added as needed.
The above scales, together with the milestones, would allow us to create several boards to visualize the current state of the project in a simple way.
Acting on behalf of MBition GmbH
https://github.com/Daimler/daimler-foss/blob/master/LEGAL_IMPRINT.md
The text was updated successfully, but these errors were encountered: