Labels

• 1. SIZE: L

  large issue - 1 - 2 days work
• 1. SIZE: M

  medium issue - 4 hours - 1 day work
• 1. SIZE: S

  small issues - easy to fix - 2 - 4 hour needed
• 1. SIZE: XL

  largest size - more than 2 days of work
• 2. TYPE: bug

  This is a bug present in an component. In certain scenarios an unwanted behaiviour appears.
• 2. TYPE: documentation

  the issue requires writing user-facing documentation (separate from code docs)
• 2. TYPE: enhancement

  This is an improvement to an already existing feature. i. e. a new capability is added
• 2. TYPE: new feature

  This is a new feature that needs to be added. The work will start from scrach.
• 2. TYPE: ops

  task related to the app deployment or CI/CD pipeline
• 2. TYPE: org task

  everything that does not fit with the other issues
• 3. PRIORITY: blocker

  the most important type of issue, a release will be delayed if a blocker issue is present
• 3. PRIORITY: critical

  critical issue, should be fixed as soon as possible but it does not block a release
• 3. PRIORITY: low

  not a priority, can be added to a release if bandwidth is available
• 3. PRIORITY: major

  major issue, should be included in a release but not neccessary
• 6. THEME: capabilities

  the issue will add a new capability to the user, i. e. It can now process a different type of email
• 6. THEME: performance

  the issue will improve the platform performance
• 6. THEME: security

  the issue will improve the platform security
• 6. THEME: usability

  the issue will improve a preexisting capability or improve the general user experiance
• 7. RESOLUTION: duplicate

  This issue or pull request already exists
• 7. RESOLUTION: wontfix

  This will not be worked on