Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beim Jahreswechsel wird ein geänderter jährlicher Urlaubsanspruch nicht übertragen #3623

Open
honnel opened this issue Jan 24, 2023 · 3 comments
Labels
status: planned This issue is planned in a milestone and won't be touched by stale bot. type: bug Something's wrong
Milestone

Comments

@honnel
Copy link
Contributor

honnel commented Jan 24, 2023

Describe the bug
Der jährliche Urlaubsanspruch wird nicht übertragen, sofern bereits ein Antrag im Folgejahr gemacht wurde. Durch den Antrag wurde bereits ein Account angelegt. Das Feld jährlicher Urlaubsanspruch wird dann aber beim Jahreswechsel nicht aktualisiert.

To Reproduce
Steps to reproduce the behavior:

  1. Mitarbeitende stellt Antrag für 2023 in 2022, dadurch wird ein Account für 2023 anlegt.
  2. Jährlicher Urlaubsanspruch in 2022 wird geändert
  3. Jahreswechsel überträgt offenen Urlaubsanspruch als Resturlaub nicht aber den jährlichen Urlaubsanspruch

Expected behavior
Jährlicher Urlaubsanspruch wird korrekt aus dem Vorjahr übertragen

@honnel honnel added type: bug Something's wrong status: new Initial state for every issue / pullrequest labels Jan 24, 2023
@honnel honnel added this to the 4.59.0 milestone Jan 24, 2023
@github-actions github-actions bot added status: planned This issue is planned in a milestone and won't be touched by stale bot. and removed status: new Initial state for every issue / pullrequest labels Jan 24, 2023
@honnel
Copy link
Contributor Author

honnel commented Jan 24, 2023

Kann es Konstellationen geben, bei denen man nicht möchte, dass der jährliche Urlaubsanspruch ins Folgejahr übertragen wird?

@derTobsch derTobsch modified the milestones: 4.59.0, 4.60.0 Jan 25, 2023
@github-actions github-actions bot added status: new Initial state for every issue / pullrequest status: planned This issue is planned in a milestone and won't be touched by stale bot. and removed status: planned This issue is planned in a milestone and won't be touched by stale bot. status: new Initial state for every issue / pullrequest labels Jan 25, 2023
@derTobsch derTobsch modified the milestones: 4.60.0, 4.61.0 Feb 23, 2023
@github-actions github-actions bot added status: new Initial state for every issue / pullrequest status: planned This issue is planned in a milestone and won't be touched by stale bot. and removed status: planned This issue is planned in a milestone and won't be touched by stale bot. status: new Initial state for every issue / pullrequest labels Feb 23, 2023
@derTobsch derTobsch modified the milestones: 4.65.0, 4.x Apr 5, 2023
@github-actions github-actions bot added status: new Initial state for every issue / pullrequest status: planned This issue is planned in a milestone and won't be touched by stale bot. and removed status: planned This issue is planned in a milestone and won't be touched by stale bot. status: new Initial state for every issue / pullrequest labels Apr 5, 2023
@derTobsch derTobsch modified the milestones: 4.x, 5.x Apr 5, 2023
@github-actions github-actions bot added status: new Initial state for every issue / pullrequest and removed status: planned This issue is planned in a milestone and won't be touched by stale bot. labels Apr 5, 2023
@github-actions github-actions bot added status: planned This issue is planned in a milestone and won't be touched by stale bot. and removed status: new Initial state for every issue / pullrequest labels Apr 5, 2023
@derTobsch derTobsch modified the milestones: 5.x, 5.2.0 Mar 27, 2024
@github-actions github-actions bot added status: new Initial state for every issue / pullrequest status: planned This issue is planned in a milestone and won't be touched by stale bot. and removed status: planned This issue is planned in a milestone and won't be touched by stale bot. status: new Initial state for every issue / pullrequest labels Mar 27, 2024
@derTobsch derTobsch modified the milestones: 5.2.0, 5.0.7 Mar 27, 2024
@github-actions github-actions bot added status: new Initial state for every issue / pullrequest status: planned This issue is planned in a milestone and won't be touched by stale bot. and removed status: planned This issue is planned in a milestone and won't be touched by stale bot. status: new Initial state for every issue / pullrequest labels Mar 27, 2024
@honnel
Copy link
Contributor Author

honnel commented Mar 27, 2024

Gerade nochmal besprochen:

  • Im ersten Schritt wollen wir einen Hinweis hinzufügen, sofern ein Konto für das nächste Jahr existiert und die Änderung nicht übernommen wird
  • Zusätzlich wäre es eine sinnvolle Ergänzung, dass wir in dem Moment, in dem eine Änderung gemacht wird, dem Benutzenden die Möglichkeit geben, die Entscheidung zu treffen, ob die Änderung ins Folgejahr übernommen werden soll (z.B. wird eine zusätzliche Checkbox eingeblendet)

@derTobsch derTobsch modified the milestones: 5.1.0, 5.4.0 Apr 1, 2024
@github-actions github-actions bot added status: new Initial state for every issue / pullrequest status: planned This issue is planned in a milestone and won't be touched by stale bot. and removed status: planned This issue is planned in a milestone and won't be touched by stale bot. status: new Initial state for every issue / pullrequest labels Apr 1, 2024
@honnel
Copy link
Contributor Author

honnel commented Apr 12, 2024

Wurde angefragt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: planned This issue is planned in a milestone and won't be touched by stale bot. type: bug Something's wrong
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants