17 Commits (8ec67a1b7b190aed1beaa74e5d92353b7dc6a21f)

Author	SHA1	Message	Date
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
ulferts	7d4a4a19e7	use join table for storing activites active in project	5 years ago
ulferts	1850622f20	Feature/versions api update (#7299) ... Feature/versions api update [ci skip]	6 years ago
Jens Ulferts	de2735f797	implement time entries widget	6 years ago
Jens Ulferts	90f2192306	time entries api - link actions and use correct response on delete	6 years ago
Jens Ulferts	05e68f8b27	take heed of activity inheritance	6 years ago
Felix Höffken	1e4c565449	write tests correctly	6 years ago
Felix Höffken	38b68b1083	try to write correct tests	6 years ago
Felix Höffken	95ceb257f6	resolve ulferts requested changes	6 years ago
Felix Höffken	9eed759cd0	[29029] DELETE option for TimeEntries	6 years ago
Oliver Günther	c7e9239212	[29003] Add PATCH api/v3/time_entries/:id endpoint ... Adds updating time entries to APIv3. https://community.openproject.com/wp/29003	6 years ago
Jens Ulferts	08a7ee52b3	introduce time entry create endpoint in api v3 ... The endpoint allows creation of time entries with the fixed attributes project, activities, ... as well as with custom fields that might be configured for time entries. There is no endpoint for form and schema, yet which micht make it difficult for clients to figure out the correct parameters.	6 years ago
Oliver Günther	059770f533	FactoryGirl => FactoryBot ... Removes the deprecation	7 years ago
Oliver Günther	6ef4211e77	Bump copyright to 2018 (#6171) ... [ci skip]	7 years ago
Jens Ulferts	417e2a1467	fix flickering spec by introducing order for time_entries api	7 years ago
Oliver Günther	c525c97e8d	Clear the cache in the time entry resource spec ... [ci skip]	7 years ago
ulferts	9c8f7f3ca1	read operations for time_entries via api v3 (#5776) ... * read operations for time_entries via api v3 Introduces the endpoints: * GET /api/v3/time_entries * GET /api/v3/time_entries/:id * GET /api/v3/time_entries/activities/:id The index action for time entries can be queried by the following filters: * project_id * user_id * work_package_id The implementation is exposing the database structure mostly one to one with the exception of some renaming and the hiding of the activities' complexity, where only the activity used systemwide is referenced regardless of whether a project specific override exists or not. * allow custom values for time entries [ci skip]	7 years ago