aoz-003 merge requestshttps://git.panter.ch/open-source/aoz-003/-/merge_requests2018-07-12T16:06:03+02:00https://git.panter.ch/open-source/aoz-003/-/merge_requests/794Resolve "On expenses the 6 month time range should be named "Semester""2018-07-12T16:06:03+02:00Kaspar Vollenweidervok@panter.chResolve "On expenses the 6 month time range should be named "Semester""Closes #435
https://trello.com/c/qQIoTveb/148-on-expenses-the-6-month-time-range-should-be-named-semester
Instead of "1. Dez - 31. Mai 2018" it should be named "1. Semester 2018"
Instead of "1. Juni - 31. November 2018" it should ...Closes #435
https://trello.com/c/qQIoTveb/148-on-expenses-the-6-month-time-range-should-be-named-semester
Instead of "1. Dez - 31. Mai 2018" it should be named "1. Semester 2018"
Instead of "1. Juni - 31. November 2018" it should be named "2. Semester 2018"
This is important for the views but especially relevant for the generated expenses PDF.Kaspar Vollenweidervok@panter.chKaspar Vollenweidervok@panter.chhttps://git.panter.ch/open-source/aoz-003/-/merge_requests/791Resolve "Bestätigung anzeigen auf last_submitted_hours_and_feedback"2018-07-11T16:44:46+02:00Kaspar Vollenweidervok@panter.chResolve "Bestätigung anzeigen auf last_submitted_hours_and_feedback"Closes #433
https://trello.com/c/8Yq13iBA/184-bestätigung-anzeigen-auf-lastsubmittedhoursandfeedback
![image](/uploads/4fbd858ada9b7aaa66b5e38e716ece84/image.png)Closes #433
https://trello.com/c/8Yq13iBA/184-bestätigung-anzeigen-auf-lastsubmittedhoursandfeedback
![image](/uploads/4fbd858ada9b7aaa66b5e38e716ece84/image.png)Kaspar Vollenweidervok@panter.chKaspar Vollenweidervok@panter.chhttps://git.panter.ch/open-source/aoz-003/-/merge_requests/781Resolve "Neue Funktionen für Feedback Eingang"2018-07-06T14:13:36+02:00Kaspar Vollenweidervok@panter.chResolve "Neue Funktionen für Feedback Eingang"Closes #428
https://trello.com/c/oMRXHPke/183-neue-funktionen-für-feedback-eingang
* [ ] Es ist weiterhin möglich, dass ein FW mehrere Feedbacks hinterlegt zu einem Einsatz. Dies wird in einem anderen Ticket bearbeitet:
* [ ...Closes #428
https://trello.com/c/oMRXHPke/183-neue-funktionen-für-feedback-eingang
* [ ] Es ist weiterhin möglich, dass ein FW mehrere Feedbacks hinterlegt zu einem Einsatz. Dies wird in einem anderen Ticket bearbeitet:
* [ ] [Als FW möchte ich mein Feedback editieren können](https://trello.com/c/5VC1BkZu/176-als-fw-möchte-ich-mein-feedback-editieren-können) (MR: !783, Issue: #429)
* [ ] [Auf der last_submitted_hours_and_feedbacks soll es nur möglich sein, einen Feedback Beitrag pro Semester zu erfassen.](https://trello.com/c/43rt6lDv/166-auf-der-lastsubmittedhoursandfeedbacks-soll-es-nur-möglich-sein-einen-feedback-beitrag-pro-semester-zu-erfassen) (MR: !784, Issue: #430)
* [x] Neuer Link zum Journal (mit Journal Icon)
* [x] Angesehen -> auf Quittieren umbenennen (ebenfalls Filter)
* [x] Neuer Button "Übernehmen"
1. Click auf Button Übernehmen
1. Klick setzt neues Feld responsible_id / responsible_at / Falls mit AJAX hier ein Beispiel [/billing_expenses/723](https://staging.aoz-freiwillige.ch/billing_expenses/723)
1. Dann erscheint dort User der feedback uebernommen hat und datum
* [x] Neuer Filter "Übernommen von" -> offen / Alle Admins alphabetisch
Kaspar Vollenweidervok@panter.chKaspar Vollenweidervok@panter.chhttps://git.panter.ch/open-source/aoz-003/-/merge_requests/493Find out if and how to use capybara rack_driver for system tests2018-02-27T15:00:26+01:00Kaspar Vollenweidervok@panter.chFind out if and how to use capybara rack_driver for system testshttps://trello.com/c/qlUmkg4y/54-2h-evaluate-racktest
Implements way to switch to rack test for a whole System test file, or only selectively single runs out of it.
https://trello.com/c/qlUmkg4y/54-2h-evaluate-racktest
Implements way to switch to rack test for a whole System test file, or only selectively single runs out of it.
Kaspar Vollenweidervok@panter.chKaspar Vollenweidervok@panter.chhttps://git.panter.ch/open-source/aoz-003/-/merge_requests/100Models that require Contact or Schedule to be built on them, take care of thi...2017-07-17T11:37:47+02:00Kaspar Vollenweidervok@panter.chModels that require Contact or Schedule to be built on them, take care of this themselvesJust soing something that has always hurt me, when I looked at the thing. SCNR.Just soing something that has always hurt me, when I looked at the thing. SCNR.https://git.panter.ch/open-source/aoz-003/-/merge_requests/103removing concern used only in client and rename the other2017-07-10T10:58:42+02:00Kaspar Vollenweidervok@panter.chremoving concern used only in client and rename the otherremoving concern used only in client and rename the other …
- associate relatives concern was only used in Client, so it
should be dropped and put into the client itself
- renaming the associatable_fields concern to a name that says...removing concern used only in client and rename the other …
- associate relatives concern was only used in Client, so it
should be dropped and put into the client itself
- renaming the associatable_fields concern to a name that says
what the thing actually does
https://git.panter.ch/open-source/aoz-003/-/merge_requests/102remove RequestCollection concern, because it is only used in Client2017-07-10T10:58:16+02:00Kaspar Vollenweidervok@panter.chremove RequestCollection concern, because it is only used in ClientThis concern was only used in one model. So It makes no sense to have it.This concern was only used in one model. So It makes no sense to have it.