Vridlo/types/Issue

Issue is a structure that represents an issue beloging to specific Rpm. It is described as:

• id is natural mandatory read-only

Unique internal identifier of the issue.

• kind is string mandatory read-only

Kind of the issue, it describes a source, which the issue has been got from. It is unchangeable.

• no is string mandatory read-only

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.

• app_slug is string mandatory

Unique slug if the application, which the problem belongs to.

• evrb is string mandatory

Epoch, version, release, buildtime of the package separated by "-" minus sing. In pair with the app_slug consists the unique rpm identifier.

• 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

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

• description_uri is string optional

Support or maintain URI, which the issue is based on. Can be served as an external description URI for the issue.

• 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, whe the issue was resolved, i.e. get resolved state last time.

• touched_at is string optional

The date and time, when status was updated last time.