119 Commits (ab658220d569a63060199d467329c6695cf7117b)

Author	SHA1	Message	Date
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
ulferts	0cc165c786	have all v3 end points accept zipped params	5 years ago
ulferts	51e7f1f048	adapt specs to altered non writable message	5 years ago
ulferts	e003ad0af7	turn scope and label unwritable	5 years ago
Markus Kahl	ffaffbf4ca	minor indentation fix [ci skip]	5 years ago
Oliver Günther	7a09d8fcdd	delay all jobs	5 years ago
Oliver Günther	a7ed2e9da0	Rewrite jobs to use ActiveJob syntax	5 years ago
ulferts	4e5b9afef5	rename project attributes	5 years ago
ulferts	6c3c7003e2	provide necessary permissions in specs	6 years ago
ulferts	a93ecca5a8	Feature/members api show (#7308) ... * basic members collection response * complete member index end point * document versions#index * remove user association from members There is already a more generic principals association. Having both causes confusion and leads to duplicate loading of models * linting * remove disabled test * add members#show api end point * add project and principal to member representer * replace member.user reference with principal * use principal reference in project members association * modernize roles api * complete member representer rendering * replace remnants of user association * add member schema api endpoint * have dedicated available projects end point for versions * linting * limit roles to assignable ones in schema * rename member to membership in api * remove remnants of user in member * spec fixes * use available_projects endpoint in versions board * add eager loading to memberships#index * members create form api endpoint * ensure role exists for default assignment * extract switch for users/groups to work_packages representer * document membership create form * add l10n expected in specs * strengthen the usage of a delete base service * use base class for set attributes service * fix alias in service * add create endpoint to members api * document members create endpoint * linting * adapt to altered service signature * use default endpoint for wp#get * use CF infused representer [ci skip]	6 years ago
Jens Ulferts	b5226f09e0	all specs mock Setting.cross_project_work_package_relations	6 years ago
Oliver Günther	3807bc4f7f	[28446] Rename due date to finish date ... https://community.openproject.com/wp/28446	6 years ago
Jens Ulferts	c1853a5cdd	fix expected namespace for groups on assignee and responsible property	6 years ago
Oliver Günther	ab5160643e	[27406] Rename responsible to accountable ... https://community.openproject.com/wp/27406	6 years ago
Jens Ulferts	319f33e924	remove textile	6 years ago
Jens Ulferts	773eddccb8	add toc macro fomatter	6 years ago
Jens Ulferts	e58a96515c	allow setting attachments through wp post/patch	7 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
Oliver Günther	0496edb9af	Fix specs	7 years ago
Oliver Günther	a0150fffa0	Remove timelines	7 years ago
Jens Ulferts	690e0ffc60	wp create/update/destroy via services	7 years ago
Jens Ulferts	6fdd122534	merge wp tree and relations into typed_dag ... Instead of having the tree/hierarchy information for work packages and the relations between the work packages separated into two tables all the information is now stored in the relations table. To support this, the typed_dag plugin is used. Notable changes: * relations_to and relations_from are swapped. relations_to has all relations that point to another work package (from_id = work_package.id) and relations_from contains all relations that lead to the work package from another one (to_id = work_package.id). This change is merely in the code. The db information is left untouched. * For follows/precedes to_id and from_id are swapped in the db. Because of that, "follows" is now the canonical name instead of "precedes". This is done so that hierarchy relations and follows relations point into the same direction which allows to easily detect cyclic relationships that would lead to infinit scheduling. * the columns `root_id`, `lft`, `rgt` do no longer exist in the wp table. * the column `relation_type` does no longer exist in the relations table. * For every type of relation a column (integer) does now exist in the relations table (e.g. hierarchy, block, follow) * Separate associations exist for every type of relation into two directions. E.g. Work packages following the current one can be accessed via `work_package.precedes`	7 years ago
Oliver Günther	ac389b869d	Fix other request specs by adding json header	7 years ago
ulferts	0c0b16508b	Fix/bump representable (#5465) ... * bump reform and roar -> bumps representer * adapt to changed validation interface * disable initializer patch for now * adapt to changed representable attr interface * can no longer have private methods inside a representer * private no longer possible for representer * bump reform * wip - restyle validation * remove commented out patch * apply injection as prescribed * reactivate reform error symbols patch * remove patch to Hash superfluous wit ruby 2.3 * remove outdated human_attribute_name patch * whitespace fixes * adapt filter name after removal of human_attribute_name patch * adapt filter specs to no longer rely on human_attribute_name patch * fix version filter name * remove reliance on no longer existing human_attribute_name patch * use correct key in journal formatter * remove private from representer * adapt to altered setter interface * reenable i18n for error messages in contracts * no private methods in representer * defined model for contracts * fix validaton * instantiate correct Object * define model for contract * circumvent now existing render method on reform * replace deprecated constant * patch correct reform class - not the module - via prepend * refactor too complex method * replace deprations * remove remnants of parentId * prevent error symbols from existing twice * adapt user representer to altered setter interface * adapt watcher representer to altered setter interface * remove now unnessary patch * adapt setter to altered interface * adapt spec * fix custom field setters * remove parentId from wp representer As the parent is a wp resource, clients should use the parent link instead * adapt spec to changed valid? interface * remove parentId from wp schema * replace references of parentId in frontend * remove TODO [ci skip]	8 years ago
Jens Ulferts	8a08856748	replace string object by custom option for list custom fields	8 years ago
Markus Kahl	f5a57e3f42	list custom field normalisation and multi select	8 years ago
Jens Ulferts	8eab60380e	embed schemas in work package list	8 years ago
Jens Ulferts	310c5513c1	linting	8 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Jan Sandbrink	0442e95d9b	Extract shared context from spec	8 years ago
Jens Ulferts	de33104d11	add a project independent endpoint for work package creation	9 years ago
Jens Ulferts	c8d1850543	allow setting new custom field values when changing the project	9 years ago
Jens Ulferts	a1d8d483b8	initial request spec for editing project on wp resource	9 years ago
Markus Kahl	498447c91b	set required setting to fix specs	9 years ago
Jan Sandbrink	e9031a38b1	Reintroduce clear statements that were still neccessary	9 years ago
Markus Kahl	4eda276ecb	always clear delivieries so one does not have to worry about it	9 years ago
Jan Sandbrink	ab9d502009	Allow to delete work packages via APIv3	9 years ago
Jan Sandbrink	e6c7a0ce9f	add global WP list endpoint	9 years ago
Jens Ulferts	3aa8a144d6	adapt specs to send mails on self action	9 years ago
Jan Sandbrink	17940bf02c	change validation of WP children ... - do not add error on a symbol called :#123 (123 is the childrens ID) - this is against the semantics of ActiveRecord::Errors - creating symbols in a loop used to be a bad idea (might be better today) - it breaks error messages in the APIv3 (which is due to APIv3 working beyond the borders of AR errors, not the best of ideas...) - use :base instead, the place for unlocatable errors - include the fact that #123 refers to a child element in the error message Basically I feel that this makes the children validation cleaner and better. But somehow I fear, that there is some code out there that depends on the fact that error keys like :#123 existed...	9 years ago
Alex Coles	ce93701029	Fix syntax (w/Rubocop) in specs ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Alexander Bach	66a0554abb	Remove outdated test	10 years ago
Alexander Bach	7c4a8547ec	Remove outdated test	10 years ago
Jan Sandbrink	819468ccba	fix specs to respect new error identifier	10 years ago
Alexander Bach	86dd0e0442	Adjusted tests for "hidden" work packages	10 years ago
Jan Sandbrink	70e7999375	fix parsing of string objects ... - accept them since format has changed - actually revert the URL escaping that has to be performed	10 years ago
Jan Sandbrink	f54781dc6b	use path helper in integration tests ... this should help in avoiding broken links with passing integration tests... after all, the only links a client should use are the ones provided by us, so they should work as intended...	10 years ago
Jan Sandbrink	454c39fbb8	style	10 years ago
Jan Sandbrink	22180a5d88	respond with new custom fields after PATCH-ing WP	10 years ago