12.2. Attributes of an issue

This is what the different attributes mean and how they are used in the ArgoUML project. This is to be read as an addendum to the Tigris definition of the resolutions and for that reason it is not a complete list.

12.2.1. Priorities

The priorities are used in the following manner in ArgoUML:

  • P1 - Fatal error

    These issues are blockers for all releases.

    Examples: ArgoUML cannot start; Crashes program, jvm or computer; and Significant loss of user data.

  • P2 - Serious error

    These issues are blockers for stable releases.

    Examples: Information lost.

  • P3 - Not so serious error

    Examples: Functions not working; Strange behavior; and Exceptions logged.

  • P4 - Confusing behavior

    Examples: Incorrect help texts and documentation; Inconsistant behavior; UI not updated; and Incorrect javadoc.

  • P5 - Small problems

    Examples: Spelling errors. Ugly icons. Excessive logging. Missing javadoc.

12.2.2. Resolutions

  • LATER

    Used to denote that a certain issue cannot be resolved until some special upcoming and planned-for event has happened. The event in question is noted in the target milestone.

    Events can be things like, dropping support for a jdk version, changing the version of UML that we support, or replacing some central mechanism within ArgoUML. Once they have a target milestone registered, they are considered events.

  • REMIND

    Not used.

  • WORKSFORME

    This means that it works in a released version of ArgoUML. State the version in the comment.

    If the version stated by the reporter in the issue is not the same as the version in the comment then this probably means that problem was fixed in some release without anyone noticing that this problem was fixed.