| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
When an admin sorted the tickets view in a different order it would take them to their own tickets list before
|
|
|
|
|
|
|
|
|
|
FlashResponder added a flash before responding. However at the point of responding objects have already been saved. So there is no way to test if they were changed.
Now instead we can call
flash_for resource
before
resource.save
and it will add the flash messages only if the resource was actually changed.
|
|
close and open actions for plain opening and closing the tickets
respond_with so fields are not cleared on invalid update
the custom actions are not strictly restful. But adding a subresource felt like too much overhead and is conceptually hard to grasp (so we destroy the openess of the ticket to close it?).
|
|
|
|
email and regarding user fields can be set to defaults based on
created_by user.
If these fields are emptied by the submitting user they will be set to whereas they are nil if they have not been initialized. In that case we will use meaningful defaults from the user who created the ticket.
|
|
We should respect the users choice. We can still get their email from the user id if we really need to.
|
|
|
|
Feature/api quota support + current_user null pattern
|
|
|
|
Null Pattern for current_user - use it to get rid of some conditionals
|
|
Also renamed help to support so it's harder to confuse it with documentation
|
