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

Aktualisierung von Abwesenheitsarten konsumieren #426

Closed
bseber opened this issue Oct 29, 2023 · 0 comments · Fixed by #428
Closed

Aktualisierung von Abwesenheitsarten konsumieren #426

bseber opened this issue Oct 29, 2023 · 0 comments · Fixed by #428
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 Oct 29, 2023

In der Urlaubsverwaltung kann z. B. die Farbe einer Abwesenheitsart geändert werden.
Die Zeiterfassung muss Updates konsumieren und entsprechend übernehmen.

@bseber bseber added the status: new Initial state for every issue / pullrequest label Oct 29, 2023
@github-actions github-actions bot added the status: stale Label for stale bot label Dec 29, 2023
@derTobsch derTobsch added this to the General Backlog milestone Dec 29, 2023
@derTobsch derTobsch removed the status: stale Label for stale bot label Dec 29, 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 Dec 29, 2023
@derTobsch derTobsch modified the milestones: General Backlog, 2.2.0 Apr 23, 2024
@urlaubsverwaltung urlaubsverwaltung deleted a comment from github-actions bot Apr 23, 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 23, 2024
@derTobsch derTobsch modified the milestones: 2.2.0, 2.3.0 Apr 24, 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 24, 2024
@derTobsch derTobsch added the type: enhancement A general enhancement label May 10, 2024
honnel added a commit that referenced this issue May 10, 2024
closes #426 

Here are some things you should have thought about:

**Multi-Tenancy**
- [ ] Extended new entities with `AbstractTenantAwareEntity`?
- [ ] New entity added to `TenantAwareDatabaseConfiguration`?
- [x] Extended new entities with `AdminAware`?
- [x] New entity added to `AdminAwareDatabaseConfiguration`?
- [ ] 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 info@focus-shift.de 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