| Age | Commit message (Collapse) | Author |
|---|
|
admins) or stay as a nested resource for a particular user (for normal users and when you visit the tickets list of a particular user).
|
|
localization.
|
|
|
|
|
|
* The APP_CONFIG needs to be initialized in core so that is required from other engines
* paths for load_views need to be relative to the model - not to rails root.
|
|
for unauthenticated ticket access.
|
|
the editing be inline rather than popup.
|
|
|
|
flash that message if the ticket already has a flash[:message] (and thus was saved successfully)
|
|
users.
|
|
|
|
|
|
|
|
Conflicts:
users/app/controllers/users_controller.rb
|
|
Conflicts:
help/app/views/tickets/_comment.html.haml
help/app/views/tickets/_new_comment.html.haml
|
|
is an admin, they should see an alert that the object wasn't found, and be redirected to the current controller.
If the object isn't found and the current user is not an admin, then we will continue to give an error about no access, so as not to leak information about what IDs do and don't exist.
|
|
relevant actions.
|
|
listing the tickets. Give a message if a user has no tickets.
|
|
partials have specific CSS for another use, so we will likely want to tweak this.
|
|
with a ticket.
|
|
|
|
* checking records are actually getting created / destroyed
* simplify creation where possible
|
|
|
|
|
|
|
|
|
|
Client-side validations, including only validating email address format ...
|
|
moving the js for view definitions into separate files
|
|
|
|
|
|
something is input for email address.
|
|
it) of user who created ticket.
|
|
|
|
This way we get syntax highlighting and so on.
|
|
|
|
Only non-comment change is that we will keep an unauthenticated user looking at the same ticket if they have closed it (rather than redirecting to index which they will not be able to access.)
|
|
the order either way.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
