zsigmondrab/time-tracking-portlet

Time tracking portlets

time-tracking-portlet's Issues

Data handling in the portlet class with interacting with the view layer

Validation for the Timesheet module according to the day statuses

The system should be able to allow or deny access to registering work on a specific day based on the current status of the day and the user in question. For example, the system should deny registering work if the day in question is a public holiday and the person is not registered to be on stand-by.

Need to connect to the day-off module

Workflow for vacation requests

The system should provide a way for a person to request a vacation. In the requesting form, it should show the following information that are required:

1. First day of vacation
2. Last day of vacation

Furthermore, it should calculate the overall days a person will take off should they choose to send their request, taking into account special days, like public holidays or moved workdays.

The system should also incorporate a workflow mechanism that sends the request to the parties that can either approve or deny such requests. Upon approval, the system should automatically flag those days as vacations for the requesting person.

Add MVC portlet to Timesheet

Email notification about vacation requests

The system should send an email notification with regards to vacation requests in all of the below scenarios:

1. Request is submitted
2. Request is approved
3. Request is denied

In all cases, the email notification should be sent to the requester, as well as the approver(s).

Notification about inactivity via email

The system should send an email if the user hasn’t added any days in the past n days (n being configurable, preferably). It should also take into consideration if those days are active days for the person, that is, it should not count vacations or other PTOs.

UI for vacation requests

Permission handling in the service layer

We don't need to have scope for our data so we remove the groupId

Print individual summary

The system should be able to print the month’s summary for the individuals. The printed page or document should contain:

1. Days of month
2. Start of work, end of work, lunch length of each day
3. Stand-by time, overtime (on stand-by), vacations
4. Current balance according to amount that should have been worked

Notification about overtime via email

Same as the Notification about overtime on the UI, however, the system should send an email regarding it as well.

Javascript validators for the timesheet table

Implement service method for showing the amount of days a person can take off

The system should show the amount of days a person can take off for the year.

Add data handling to Timesheet UI component

• resource request: userId, companyId, intervalEndDate, intervalStartDate
• add WorkDay remote service: userId, companyId, startTime, endTime, dayOfYearId, pause, serviceContext
• update WorkDay remote service: userId, startTime, endTime, dayOfYearId, pause, serviceContext

Yearly summaries of vacations per team

The system should provide a way for a person with elevated privileges to see their respective team(s) vacations and special days throughout the year.

Integrate unit tests

Data handling in the portlet class interacting with the business and the view layer

This feature should allow users to input three numbers for each individual days:

1. Start of work - time of day
2. Length of lunch break - in minutes
3. End of work - time of day

Data validation in the portlet class

Register special days

The system should allow users with elevated privileges to register special days. In addition, next to the special day, the system should be able to allocate default values to be used for certain days.

The days that should be registered are:

1. Public Holidays
2. Vacations
3. Stand-by
4. Sick leave
5. Paternity leave
6. Family Emergency

Implement permission definitions for all of the moduls

Need to create the action-resource definitions and put the permission checking logic into the remote service methods.

End date with null value should not be handled

Adding Day-offs portlet service layer

Print month’s summary

This feature should be restricted to certain individuals (for example: HR). The system should be able to print out a team’s summary for the month. The printed page or document should contain:

1. Team member
2. Day in question
3. Stand-by time
4. Overtime

TestIssue

valami

Data validation for the timesheet portlet on service level

Please, find examples starting in the portal.properties and searching for ".validator= text". You can find solutions with implementing interfaces and extending abstract classes. We should follow the second one with some basic null and empty string checking on the fields.

The asset.entry.validator can be a good example.

Pre-requisite: #2

Zsigmond

issue#4 Adding Activities portlet service layer

issue#3 Separate service.xml files for the different portlets of the plugin

Notification about overtime on the UI

The User Interface should notify the user if their overtime is higher than what can be “burnt down”. The logic should enable dynamic counting of current overtime versus remaining days of the month.

getWorkDays method contains unnecessary arguments in WorkDay services

Basic timesheet table javascript

Access to monthly summary of team members per role

Based on roles and connecting teams, a user (lead) should be able to view the monthly summary of their direct reports, similarly to how the “Monthly view of daily work” works.

Add "addWorkDay" and "updateWorkDay" methods to WorkDayService

Adding Timesheet portlet service layer

Set individual amount of days a person can take off in a year

The system should provide a way for a person with elevated privileges to set the number of days a person can take off in a year. This should be done for each individual in a team. This should be done manually each year, with the system showing the previous year’s number by default.

Work days are not in the list if the end date is null

Permission handling in the service layer

Connection to the Day off module

The plugin should be able to interface with the Day off module to gather the following information:

1. Number of days a person can take off
2. Days when the person is on vacation
3. Days when the person is on stand-by
4. Public holidays
5. Sick leaves
6. Paternity leaves
7. Family emergency
8. “Moved” working days

Don't need to put a portlet level permission checking to the views