Labels
Prioritized labels 8
Drag to reorder prioritized labels and change their relative priority.
-
Prioto be decidedcivilmrcc / onefleetUnknown priority for freshly created issues. Please assign this label if you are not a OneFleet developer or if you are unsure which priority to assign to a new issue. Priorities will be assigned to new issues in our weekly meeting.
-
Prio5 (High)civilmrcc
😱 Most important. Timeframe: 1 Day! (These are highly time-critical issues that need to be implemented as soon as possible. Examples are: Security breaches, Data consistency bugs, Data loss risks, etc. Be aware that the actual importance of an issue may change as time goes on, so always re-evaluate if this label is really still applicable to each issue that uses it.) -
Prio4civilmrcc
🚨 Increased Priority. Timeframe: 1 Week. (colours blended with https://meyerweb.com/eric/tools/color-blend/) -
Prio3 (Normal)civilmrcc
🍎 Normal priority issues. Timeframe: 1 Month. (These issues should be dealt with soon, but should be solved through thoughtful engineering, not quickfixes.) -
Prio2civilmrcc
🍊 Decreased Priority. Timeframe: 3-4 Months. (Issues with this priority should be considered, but there are probably some more pressing higher-priority issues to be dealt with first) -
Prio1 (Low)civilmrcc
🍏 Low Priority. Timeframe: 6-12 Months. (These issues might track things that we also need to do, but there might be a feasible workaround for them right now or they are less urgent due to other reasons. They might be given a higher priority in the future if our situation changes, so low-prio issues should regularly be evaluated to check if they still warrant the lowest priority label or if they should be given a higher priority due to changing external circumstances.)
Other labels 37
-
Aim: Data Qualitycivilmrcc / onefleetThe Data Quality should be affected (hopefully improved) by this issue/MR. This label can be attached to MRs that either directly fix an issue that was causing data corruption, or to UX features that help improve the Data Quality through easier curation of entered data.
-
Aim: Developer Experiencecivilmrcc / onefleetThis issue or MR makes the life of developers easier, by improving development workflows.
-
Aim: Technical Debtcivilmrcc / onefleetThis issue or MR is aimed at reducing our technical debt, i.e., repairing damage that was done while quick-fixing something else, or just following proper software development practices for future maintainability and health of our codebase.
-
Aim: UXcivilmrcc / onefleetThis issue or MR tries to improve user experience, usually including some form of UI change.
-
Do not merge: Adjustments Neededcivilmrcc / onefleetThis MR still needs some improvements before it is ready. An issue with this label may need more explanation on what exactly needs to be done, so the issue description may be lacking some info. A merge request with this label could be lacking some code changes that definitely need to be done before merging (i.e.
🍎 ). When this label is attached to an issue or MR, the person attaching it should usually also add a comment explaining n why this label was added and what needs to be done before removing it again.) -
Do not merge: wait until next releasecivilmrcc / onefleetSometimes there are MRs that already address a field change that should only be applied in a minor or major release instead of a patch release. Thus, the MR must wait and can only be merged when the patch release was deployed
-
Knowledge: CI/CDcivilmrcc / onefleetAn issue or MR related to our continuous integration / continuous delivery pipeline. Used for quickly viewing all CI/CD related issues and MRs. You will likely use and/or gain knowledge on CI/CD while working on this!
😉 -
Knowledge: CouchDBcivilmrcc / onefleetAn issue dealing with CouchDB. You will likely use and/or gain knowledge on CouchDB while working on this!
😉 -
Knowledge: InterviewTaskcivilmrcc / onefleetThese issues should be solvable with the least amount of knowledge about our specific codebase. They require even less codebase knowledge than issues with the "Knowledge: Onboarding" labels.