| Age | Commit message (Collapse) | Author |
|---|
|
We'll use this to clean up after user destruction
|
|
|
|
cases where it is an admin who set it.
|
|
|
|
|
|
* 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.
|
|
Conflicts:
help/app/views/tickets/_comment.html.haml
help/app/views/tickets/_new_comment.html.haml
|
|
with a ticket.
|
|
|
|
|
|
Client-side validations, including only validating email address format ...
|
|
something is input for email address.
|
|
|
|
This way we get syntax highlighting and so on.
|
|
the order either way.
|
|
|
|
|
|
|
|
removes the need for .all call in some tests.
|
|
|
|
have to do more, including allowing user to pick sort order.
|
|
The one remaining is failing because we still build an Array for the admin tickets.
Needs to be implemented so I am leaving that test as is.
|
|
|
|
|
|
|
|
something like https://github.com/spree/spree/issues ), using bootstrap for display.
Still want to use pjax, and have more functionality to add: searching, sorting, pagination, etc..
|
|
|
|
|
|
ID will be the random string for the secret URL.
Tickets created when user was unauthenticated will be viewable by anybody who knows the URL.
|
|
and initial way to close tickets.
|
|
|
|
|
|
|
|
|
|
|
|
ticket comment to a new ticket.
|
|
|
|
|
|
|
|
access from users engine.
|
|
independent engine repo.
|
