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

Globale Einstellung für Feiertagsregelung #516

Closed
bseber opened this issue Jan 5, 2024 · 0 comments · Fixed by #543
Closed

Globale Einstellung für Feiertagsregelung #516

bseber opened this issue Jan 5, 2024 · 0 comments · Fixed by #543
Assignees
Labels
status: planned This issue is planned in a milestone and won't be touched by stale bot. type: enhancement A general enhancement
Milestone

Comments

@bseber
Copy link
Contributor

bseber commented Jan 5, 2024

Aktuell kann nur für jede Person einzeln das Bundesland / die Feiertagsregelung konfiguriert werden.

Ab einer gewissen Anzahl wird das viel und es wäre einfacher einen Standard für sein Unternehmen hinterlegt zu haben.

Es muss global konfiguriert werden können

  • Bundesland / Feiertage
  • ob an Feiertagen gearbeitet wurde oder nicht

Diese globale Einstellung gilt dann als Standard bei den Personen. Kann also individuell überschrieben werden.

@bseber bseber added the status: new Initial state for every issue / pullrequest label Jan 5, 2024
@bseber bseber added this to the 2.1.0 milestone Jan 5, 2024
@derTobsch derTobsch added the type: enhancement A general enhancement label Jan 5, 2024
@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 5, 2024
@derTobsch derTobsch modified the milestones: 2.1.0, 2.2.0 Jan 20, 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 Jan 20, 2024
@bseber bseber self-assigned this Mar 1, 2024
@derTobsch derTobsch modified the milestones: 2.3.0, 2.2.0 Apr 19, 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 19, 2024
derTobsch added a commit that referenced this issue Apr 24, 2024
closes #516 

Here are some things you should have thought about:

**Multi-Tenancy**
- [x] Extended new entities with `AbstractTenantAwareEntity`?
- [x] New entity added to `TenantAwareDatabaseConfiguration`?
- [x] Tested with `dev-multitenant` profile?

<!--

Thanks for contributing to the zeiterfassung.
Please review the following notes before submitting you pull request.

Please look for other issues or pull requests which already work on this
topic. Is somebody already on it? Do you need to synchronize?

# Security Vulnerabilities

🛑 STOP! 🛑 If your contribution fixes a security vulnerability, please do
not submit it.
Instead, please write an E-Mail to [email protected] with all the
information
to recreate the security vulnerability.

# Describing Your Changes

If, having reviewed the notes above, you're ready to submit your pull
request, please
provide a brief description of the proposed changes.

If they:
🐞 fix a bug, please describe the broken behaviour and how the changes
fix it.
    Please label with 'type: bug' and 'status: new'
    
🎁 make an enhancement, please describe the new functionality and why you
believe it's useful.
    Please label with 'type: enhancement' and 'status: new'
 
If your pull request relates to any existing issues,
please reference them by using the issue number prefixed with #.

-->
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: enhancement A general enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants