A particular files that will be stored with the description of the problem
Number of a particular report problem
Person reporting a problem
Person having an obligation to do analized a given report problem.
List of files that will be stored together with the description of the problem
One-line summary of the problem. This information will be used as the subject of the problem and it should be short, but still descriptive enough to be different from other problem report subjects.
The date on which the Report was submitted.
The date on which the Report was submitted.
The name of the product, component or concept where the problem lies. In order to get the best possible support, please select the category carefully.
Name of the user in the system.
User's password
User's password confirmation
User's security question.
The class of a problem can be one of the following:
The status of a problem can be one of the following:
Is the report considers confidential? If not, the material provided with the bug report can be published. For example, sample code can be used when helping other customers.
Is the report considers private? If not, the material provided with the bug report can be published. For example, sample code can be used when helping other customers.
Precise description of the problem.
Description of the environment where the problem occured: machine architecture, operating system, host and target types, libraries, pathnames, etc. On Unix, in addition to other information, execute the command uname -a and copy the result here.
How soon the solution is required. Accepted values include:
Release or version number of the Eiffel product. Please be as specific as possible. For example, 5.6.0919 is better than 5.6.
The severity of the problem. Accepted values include:
Example code, input, or activities to reproduce the problem. Eiffel Software uses the example code both to reproduce the problem and to test whether the problem is fixed. Include all precondition, inputs, outputs, conditions after the problem, and symptoms. Any additional important information should be included. Include all the details that would be necessary for someone else to recreate the problem reported, however obvious. Sometimes seemingly arbitrary or obvious information can point the way toward a solution.
A list representation of filtered results by the designated (logged-in) user.
A representation of a single report.
Create a new resource
Update an existing resource
The target IRI points to a resource which represents the root.
Defines a search query that can be performed by search clients.
Defines first phase of user registration: user email, password, first name and last name.
Used to send new password to user.
Used to get authorized access, describes the connection established by a user with a Login, until either the user or the system or service to which he connected terminates the connection. A user must only provide Credentials for Authentication at the start of a Login Session. He is then authorized to use some or all of the services offered by the Host System to which he connected.
The act of terminating a login session.
Form to Activate a new user.
Report problem summary
A link template to add a new report interaction problem to the system by the designated (logged-in) user.
A link template to add a new report problem to the system by the designated (logged-in) user.