Server using an existing ticket storage implementation

[juokaz]

Summary

A server implementation that uses an existing ticket system such as Trac to store and retrieve tickets.

Requirements

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in IETF RFC 2119.

Specification

The server MUST support anyonymous and authenticated users. The server MUST NOT put additional constraints such as email address validation into place for anonymous users unless the underlying ticket system requires this.

The server MUST support retrieval and creation of tickets and comments.

The server MUST support closing and reopening and SHOULD support updating of tickets and comments by appropriately authorized users where supported by the underlying ticket system.

The server MUST support retrieval of information about users.

The server SHOULD support creation and updating of users.

The server SHOULD NOT discard unknown elements in requests upon serialization to the data store.

[caseysoftware]

Possible addition:
"The server SHOULD NOT discard unknown elements in requests upon serialization to the data store."

Source: #3

[dzuelke]

Done, thanks @caseysoftware