leap_web.git/engines/support/app/views, branch 0.5.2 [leap_web] destroy_btn helper method 2014-05-28T07:26:17+00:00 Azul azul@leap.se 2014-05-28T07:26:17+00:00 df1c2438fcfe39edfb46546be8fcee5021f95fc3 






add btn helper for link_to with .btn
2014-05-27T14:32:50+00:00

Azul
azul@leap.se

2014-05-27T14:32:50+00:00

cc59ce53e52bf48d97de16d66012e8309bf98fe8

Also translates the first arg if it's a symbol and adds more btn- classes if given as html_options[:type]





Also translates the first arg if it's a symbol and adds more btn- classes if given as html_options[:type]







tickets: structure i18n
2014-05-26T11:00:05+00:00

Azul
azul@leap.se

2014-05-22T12:57:29+00:00

19bce0f114180f355f0df367cf6d21bd957734a6












flash_for with_errors option displays error messages
2014-05-26T10:59:26+00:00

Azul
azul@leap.se

2014-05-20T11:50:32+00:00

560eb039f4778257559395583e1233d052d44127












split up and refactor TicketController#update
2014-05-26T10:59:26+00:00

Azul
azul@leap.se

2014-05-20T10:30:55+00:00

467dd712a19d48fc653cfc0e58201e6657d2c1f9

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





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







Merge pull request #159 from azul/bugfix/5659-fix-ticket-form-submit
2014-05-14T06:41:29+00:00

azul
azul@riseup.net

2014-05-14T06:41:29+00:00

09798683794a5b74cd9cb8801f15d21e093e68b9

open/close toggle and fields in different forms - fixes #5659




open/close toggle and fields in different forms - fixes #5659






open/close toggle and fields in different forms - fixes #5659
2014-05-13T15:10:33+00:00

Azul
azul@leap.se

2014-05-13T15:10:33+00:00

41055098941481611d4b9fa80c769092ed9bd79d












prefill ticket form from the model - fixes #5657
2014-05-13T12:02:15+00:00

Azul
azul@leap.se

2014-05-13T11:52:16+00:00

81a4a0527639fe4b560b8d98f977f6dbac67bb41

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.





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.







move open and close buttons into status display
2014-04-25T10:18:40+00:00

Azul
azul@leap.se

2014-04-23T15:14:30+00:00

615261a6f0d1bae5d999e3014f18191ed1ba1008

They do not save any changes. So i think it's better to keep them separated from the Save button that does save changes.





They do not save any changes. So i think it's better to keep them separated from the Save button that does save changes.







using simple_form for the last form that was not using it.
2014-04-25T10:18:40+00:00

Azul
azul@leap.se

2014-04-23T13:27:40+00:00

6c13d3323c180a333fd0f32d17a62adce9fcf2bb