ActivityWatch / ActivityWatch/activitywatch

Implement reporting

Abierto
#233 8 comentarios 12 reacciones 0 asignados Ver en GitHub
!pinned area: analysis improves: sustainability phase: planning priority: medium type: enhancement
Lenguaje dominante
Python
Estrellas
18.9k
Forks
1k
Merge medio
1 d 4 h
PR fusionados (30 d)
28

Descripción

Reporting is the requested "enterprise feature" that we could provide. Since this is basically only used in a company/consultancy or enterprise environment perhaps there is a way to earn some money by developing it exclusively for paying customers?

## TODO

- [ ] Add a menu item to aw-webui called "Reporting" that just shows a "Coming soon" page with a form to fill out interest.
- Form should contain questions about willingness to pay and number of reportees.

## Problem

ActivityWatch already has usage within companies and is then usually set up as a single server to which many clients report (see for example this [60 client setup](https://forum.activitywatch.net/t/operationalerror-database-is-locked/164)). This has vast privacy issues and is not an acceptable solution in the vast majority of cases as it has a high risk of being misused for involuntary, covert, or straight illegal employee surveillance.

## How it could work

Users could whitelist which activities (or categories of activities) to report, only letting the employee what work-related things were done. This would be a great start.

## You can vote on this feature [on the forum!](https://forum.activitywatch.net/t/reporting-timesheets-enterprise-use/306)

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.