Skip to content

Issue labels

lukdumi edited this page Aug 18, 2014 · 11 revisions

The issue labels have been divided into three domains:

  1. Activity
  2. Functionality
  3. Rejection reason

Activity labels

Give information on what type of work will be/ has been involved in completing the given task. The activity label titles are prefixed with 'a'.

  • bug - correct the reported bug
  • 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 'env' 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
  • wiki - describe the specified concept/ problem/ solution etc. on wiki pages

Functionality labels

Inform which functionality of the application will be/ has been affected by the task. The label titles are prefixed with 'f'.

  • 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.
  • env - application environment, not an actual part of the application (CI, code quality systems, deployment scripts etc.)
  • gui - parts of the system that are directly related to web user experience and that are not part of greater functionality, e.g. screen showing judgment details (but not search screen which is one of the parts of the search functionality).
  • import - the data import functionality
  • restful-api - the restful api of the system
  • search - the search functionaly based on solr (judgment search, court search etc.)

Rejection reason

The rejection reason labels say that the task has been rejected and why. The labels of this kind are prefixed with 'r'.

  • 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.