Infos:
- Used Zammad version: 6.2.0-1711349647.bc0c70d0.bullseye
- Used Zammad installation type: package
- Operating system: debian
- Browser + version: python api-call
Expected behavior:
- identical accounted time values in api-response (accounting log) and in xlsx-export
Actual behavior:
- exporting via web-ui delivers two values per ticket: time units total, time units
- exporting via REST-api delivers only the value time_unit which corresponds to time units total
- this means that the accounted time from the api response in the current month is wrong because it’s the tickets total and not the total in the given month.
Steps to reproduce the behavior:
- have a ticket that is open for over a month with accounted values in the previous and the current month
- download the accounting data via web-ui selected by the previous month
- download the accounting data via web-ui selected by the current month
- compare with the api call to api endpoint your-zammad-domain/api/v1/time_accounting/log/by_ticket/{year}/{month}