Open juokaz opened 12 years ago
We see a rough order of implementation to go:
This statement could use some parentheses:
The client MUST support closing and reopening and SHOULD allow editing of tickets and comments by authorized users.
Does this mean:
(The client MUST support closing and reopening and SHOULD allow editing of tickets and comments) by authorized users.
Or:
(The client MUST support closing and reopening) and (SHOULD allow editing of tickets and comments by authorized users.)
We're thinking the first parenthetical version makes more sense but we wanted to check :)
What functionality is the user management interface supposed to provide?
We're collaborating here: https://github.com/carols10cents/restfest-helpdesk-ruby-client
very cool.
And our progress is up on heroku, lots of stuff is either faked or not working right now ;) https://restfest-ruby-client.herokuapp.com/
+1
Good job guys. The first interpretation of the parentheses was indeed correct.
As far as registration is concerned, the client could allow people to create a new account (if you have the time to implement that; if not, really no big deal).
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.