-
Notifications
You must be signed in to change notification settings - Fork 11
Issue Labels
Łukasz Dumiszewski edited this page May 25, 2016
·
4 revisions
- Activity
- Functionality
- Rejection reason
Give information on what type of work will be/ has been involved in completing the given task. The activity label titles are prefixed with 'activity'.
- bug - correct a bug (one that does not allow some functionality to work)
- tiny bug - correct a tiny bug (one that is a kind of inconvenience but does not make the system work improperly)
- fatal bug - correct a fatal bug (one that does not allow the system to work at all)
- concept - invent a solution of the given problem without actual implementing it
- explore - find more information on the given technology or solution
- impl - write new code that adds or changes some functionality; in case of the 'environment' functionality (see below) it can mean configuring some new functions, writing scripts etc.
- question - anwser the asked question
- refactor - change the code but only in respect to its quality, not meaning or functionality
- document - prepare documentation of the specified concept/ problem/ solution etc.
Inform which functionality of the application will be/ has been affected by the task. The label titles are prefixed with 'functionality'.
- core - the basis of the application architecture or code that is commonly used by various parts of the system. For example: spring configuration, persistence layer repository services or some of webapp tags, javascripts.
- environment - application environment, not an actual part of the application (CI, code quality systems, deployment scripts etc.)
The rejection reason labels say that the task has been rejected and why. The labels of this kind are prefixed with 'rejection reason'.
- duplicate - the task is a duplicate of some other task
- invalid - the task is invalid, i.e. it provides incorrect information or it does not make any sense in case of the saos system
- wontfix - the task will not be accomplished because the system works as expected or the reported issue does not matter or there are too many resources needed to accomplish it.