Vridlo/types/Issue

From ALT Linux Wiki

Issue is a primary structure that represents an issue belonging to the specific application or RPM. It is described as:

  • id is natural mandatory read-only
Unique identifier of the issue.
  • kind is string mandatory write-once
Kind of the issue, it describes a source, which the issue has been got from. It is unchangeable.
  • no is string mandatory write-once
Number of code of the issue, in the pair with kind is an unique identifier of the issue in the system. It is unchangeable.
  • status is string mandatory
Status of the issue. Must contain one of new, resolved, assigned, verified, reopened, closed
  • severity is string mandatory
Severity of the issue. Must contain one of normal, critical, major, enhancement, minor, blocker.
  • target_kind is string mandatory
Kind of the issue target, can be one of rpm, app.
  • target is string mandatory
Unique identifier of the issue target, when target_kind is rpm, identifier is the RPM identifier slug in revrb format, which includes epoch, version, release, buildtime of the RPM separated by "-" minus sign. When target_kind is app, identifier is the application slug.
  • reporter_email is string mandatory
Email of the person or bot who is reported the problem / issue.
  • resolution is string optional
Status of the issue resolution. May contain one of fixed, worksforme, notabug, wontfix, duplicate, later, or blank value.
  • description is string optional
Description of the problem. It is formatted as defined in the description_format field.
  • description_title is string optional
Description title, which can contain the single line of description optionally with with maintain URI, which the issue is based on. The URI can be served as an external description URI for the issue. It is formatted also as the description itself, i.e. as defined in the description_format field. Must be presented, when description is also presented.
  • description_format is string optional
Format of the text, which the description of the problem is written in. Can be one of html, markdown, text. Must be blank when description and description_title are also blank.
  • reported_at is datetime optional
The date and time, when the report was acquired from the reporter.
  • resolved_at is datetime optional
The date and time, when the issue was resolved, i.e. get resolved state last time.
  • touched_at is datetime optional
The date and time, when status was updated last time.

Combination of kind, no must be unique for the system.