[Feature] 'Screenshots' | Managers can filter screenshots corresponding to time entries
- Dominant language
- TypeScript
- Stars
- 569
- Forks
- 102
- Avg merge
- 6h 40m
- Merged PRs (30d)
- 12
Description
### Background
Based on the logic of timesheets and tracking, when a user records time the system captures screenshots at different intervals. Managers of team members should have permissions to view these screenshots even when assessing time entries/timesheets. The objective of this task is for managers to be able to filter screenshots that are linked to time entries.
### Requirements
1. On the listing of time entries, managers should be able to see screenshots and apply various filters.
2. Manager can filter to see screenshots for time entries of any particular day, project, team, employee, status and activity level. See below screenshots of Gauzy as examples of these filters
- ***Date**:* to filter time entries recorded on a specific date
- ***Project**:* to filter time entries recorded on a specific project
- ***Task**:* to filter time entries recorded on a specific task
- ***Team***: to filter time entries recorded on a specific team group
- ***Employee***: to filter time entries recorded for a specific employee
- ***Status**:* to filter time entries by the status (Pending Approval, Approved, and Rejected)
- ***Activity level**:* to filter time entries by activity percentage.


3. Manager can also filter on the source of the screenshot
- ***Source**:* to filter screenshots by source type such as Web Timer, Desktop Timer, Mobile App, etc.
4. Manager can multi-select values on each of the filter.
Contributor guide
Research direction
No files or tests are named. Start by locating the time-entry listing and the existing screenshot/time-entry query entry points; then trace how manager permissions and filters are handled. Done means managers can multi-select and filter screenshots by date, project, task, team, employee, status, activity level, and source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100