You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal: We would like to allow supervisors/admins to be able to retrieve employees timesheet(s) efficiently with simply querying for their user id(s). All users should be able to retrieve their own timesheets.
Scope: Backend codebase getTimesheet
Shema
Request Data: Should take in one or more uuid(s) as a parameter
Return Data:
employees - (userID, useridTimesheet(s))
admins - list of mapping objects (user id, userid timesheet(s))
supervisors - should get back a list of mappings similar to admins back but with no employee time but all other data.
Conditions of Acceptance:
Associates should not be able to access this new endpoint. Thow 401 unauthorized error if they try to.
If supervisors request timesheets from users they have access to, they should receive all relevant timesheet data (except clock in, clock out of associates).
If supervisors request outside their company, we have two options we should consider. Either throw an error or return valid user ids (this would require having error, valid, and warnings as three separate fields).
Admins can get anyone's user ids, but if they request a user id that does not exist, throw some type of an error or just return nothing.
One or more timesheets requested will get those corresponding mapping objects.
By default we should get all tickets for time period but should add date filtering in the future
The text was updated successfully, but these errors were encountered:
Linked to Story Item 14
Goal: We would like to allow supervisors/admins to be able to retrieve employees timesheet(s) efficiently with simply querying for their user id(s). All users should be able to retrieve their own timesheets.
Scope: Backend codebase
getTimesheet
Shema
Request Data: Should take in one or more
uuid
(s) as a parameterReturn Data:
employees -
(userID, useridTimesheet(s))
admins - list of mapping objects
(user id, userid timesheet(s))
supervisors - should get back a list of mappings similar to admins back but with no employee time but all other data.
Conditions of Acceptance:
Associates should not be able to access this new endpoint. Thow 401 unauthorized error if they try to.
If supervisors request timesheets from users they have access to, they should receive all relevant timesheet data (except clock in, clock out of associates).
If supervisors request outside their company, we have two options we should consider. Either throw an error or return valid user ids (this would require having error, valid, and warnings as three separate fields).
Admins can get anyone's user ids, but if they request a user id that does not exist, throw some type of an error or just return nothing.
One or more timesheets requested will get those corresponding mapping objects.
By default we should get all tickets for time period but should add date filtering in the future
The text was updated successfully, but these errors were encountered: