Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

End-user client #1

Open
juokaz opened this issue Sep 13, 2012 · 8 comments
Open

End-user client #1

juokaz opened this issue Sep 13, 2012 · 8 comments
Assignees
Labels
Milestone

Comments

@juokaz
Copy link

juokaz commented Sep 13, 2012

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.

@carols10cents
Copy link

For a web client written in ruby

We see a rough order of implementation to go:

  • Display tickets
  • Display comments
  • Create tickets
  • Create comments
  • Registration (Not specified anywhere in this ticket??)
  • Authorization
  • Editing/closing/reopening
  • User management interface (related to registration?)

@carols10cents
Copy link

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 :)

@carols10cents
Copy link

What functionality is the user management interface supposed to provide?

@carols10cents
Copy link

We're collaborating here: https://github.com/carols10cents/restfest-helpdesk-ruby-client

@mamund
Copy link
Member

mamund commented Sep 13, 2012

very cool.

@carols10cents
Copy link

And our progress is up on heroku, lots of stuff is either faked or not working right now ;) https://restfest-ruby-client.herokuapp.com/

@mamund
Copy link
Member

mamund commented Sep 13, 2012

+1

@dzuelke
Copy link
Member

dzuelke commented Sep 13, 2012

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants