Summary
A client application of any kind (web or native) that allows people to interact with a help desk server.
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 client MUST support anonymous and authenticated users. The client MAY put constraints in place for anonymous usage, such as email address validation or CAPTCHAs.
The client MUST support display and creation of tickets and comments.
The client MUST support closing and reopening and SHOULD allow editing of tickets and comments by authorized users.
The client SHOULD provide a user management interface for authorized users.
Summary
A client application of any kind (web or native) that allows people to interact with a help desk server.
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 client MUST support anonymous and authenticated users. The client MAY put constraints in place for anonymous usage, such as email address validation or CAPTCHAs.
The client MUST support display and creation of tickets and comments.
The client MUST support closing and reopening and SHOULD allow editing of tickets and comments by authorized users.
The client SHOULD provide a user management interface for authorized users.