Skip to content

Issue labels

Jump to bottom
Tobias Lorenz edited this page May 20, 2014 · 1 revision

Each issues gets a label dependent on whether this is a new feature, a problem or just a question/answer.

Issue Category (1.x)

  • "1.1 Major Improvement" means that it is a huge enhancement, such as a new bus system, architectural changes or technology migration (MFC->Qt).
  • "1.2 Minor Improvement" means that is brings in a new functionality, such as a new hardware interface in an already existing bus system technology
  • "1.3 Patch (Defect)" is labeled for problems that need to be solved.
  • "1.4 Other (Support)" is often used if the issue can be closed without further changes in the repository, such as a support question resp. answer.

Subsystem (2.x)

  • Not applicable any more.

Error Classification (3.x)

Business-value based definition of priorities:

  • 3.1 High Priority (EC1): Bug fix is absolutely necessary. The customer cannot work (anymore) with the tool. OR he can find an alternative only at competitors. OR he can only continue his work if he returns to the predecessor release.
  • 3.2 Medium Priority (EC2): Problem is pressing for customer. The customer can work with all functions (like he did before the update) but a singular function does not work (anymore) => The customer cannot roll-out the update in his organization.
  • 3.3 Low Priority (EC3): Situation is temporarily acceptable. The customer can use all functions as before but partly restricted

Guidelines to set the priority (Prioritization if answer is yes.):

  1. Is there an acceptable workaround available? EC-3.
  2. Does the error pattern not appear all over the customer‘s work stations? Presumably a problem with another software, otherwise proceed with question 3.
  3. Has the customer been using the tool for a longer period of time and the problem appears suddenly? Presumably a data problem, otherwise proceed with question 4.
  4. Can the customer not at all proceed working with the tool because of the problem? EC-1
  5. Can the customer only proceed working with the ETAS tool if he goes back to the former installed release? EC-1
  6. Can the customer precede working with all functions after an update except one singular function? EC-2
  7. Is there a chance for the customer to get a solution for his technical problem if he migrates to a competitor's tool? EC-1
Clone this wiki locally