TeamCal Neo is a web application of a day-based calendar. It's generic purpose is the absence and event management of employees, project teams, music bands and other groups needing a scheduler.
Is your feature request related to a problem? Please describe.
We also have a use case of adding Shift Plans. Since they follow a fixed structure, inputting them is cumbersome. We like to request a new feature, to ease up the User experience.
Describe the solution you'd like
We are aware that this is a major change, since it would need another dedicated configuration page/code/database table for schemas. And maybe you even have a better idea on how to implement this, but let me illustrate the user story first.
Schema Input of User Absences in Calendar
With:
M = Morning Shift
D = Day Shift and
N = Night Shift.
We would like to have a NEW special “Scheme Absence type”, which for now we name “Normal Shift Scheme”.
When a user is in the action=calendaredit
User Input “x” in “Normal Shift Scheme”:
Absence
1
2
3
4
5
6
7
Morning
Day
Night
Normal Shift Scheme
x
User presses “Save” → Rendering to
Users
1
2
3
4
5
6
7
M
M
D
D
N
N
Internal State then is:
Absence
1
2
3
4
5
6
7
Morning
x
x
Day
x
x
Night
x
x
Normal Shift Scheme
Remarks:
Basically one of our “managers” sits down and fills out a plan for a whole year. And sometime big changes need to be done due to sickness / covid etc. Above is just one way of archiving the wanted result. And only at the level of “one shift cycle”.
Maybe thinking bigger, like a year displayed with only this special absence type (using the already available “filter”), would allow to input this for one user for a whole year in one page…
And I hope i made the CR clear. If not, please ask. And if you have an idea to archive this differently, even better.
In case you can not accept this CR, I will have to hack the SQL database, since that really seems to be a strong user story request.
Note
This request was submitted in March 2024 via a different channel. I submitted it here to allow the community to participate.
An Absence Pattern is a weekly combination of existing absences (or no absence)
Editing Absence Patterns is a permission that can be granted to roles
A user can select an Absence Pattern when editing his month calendar (a button "Pattern" next to "Period" and "Recurring"). The pattern is then applied to the month by saving the corresponding absences automatically
When selecting the pattern, a start and end date can be specified to apply the weekly absences over a longer period of time
What version are you referring to? 3.9.3
Is your feature request related to a problem? Please describe. We also have a use case of adding Shift Plans. Since they follow a fixed structure, inputting them is cumbersome. We like to request a new feature, to ease up the User experience.
Describe the solution you'd like We are aware that this is a major change, since it would need another dedicated configuration page/code/database table for schemas. And maybe you even have a better idea on how to implement this, but let me illustrate the user story first.
Schema Input of User Absences in Calendar With:
M = Morning Shift D = Day Shift and N = Night Shift.
We would like to have a NEW special “Scheme Absence type”, which for now we name “Normal Shift Scheme”.
When a user is in the action=calendaredit
Remarks:
And I hope i made the CR clear. If not, please ask. And if you have an idea to archive this differently, even better.
In case you can not accept this CR, I will have to hack the SQL database, since that really seems to be a strong user story request.
Note This request was submitted in March 2024 via a different channel. I submitted it here to allow the community to participate.