openproject

Commit Graph

Author	SHA1	Message	Date
ulferts	3b0f7367fd	move to proper module	4 years ago
ulferts	fdcc89f810	allow freely setting the dates of manually scheduled child work packages	4 years ago
ulferts	0b15db3c9a	rename fixed_version to version	5 years ago
Henriette Dinger	bd7f4e4814	Update copyright notice	5 years ago
ulferts	fd6d707fa8	adapt specs	5 years ago
ulferts	6c4e572f4e	consolidate allowed_* logic in the wp contract	5 years ago
ulferts	bc682f6b01	bail on inexistent related resource * status * type * assignee * priority	5 years ago
Markus Kahl	cb6d28136d	allow editing estimated time for parents, show derived separately	5 years ago
Oliver Günther	016bfc49cb	[30590] Fix switching into closed status with closed version assigned https://community.openproject.com/wp/30396 introduced a blocking of status editing when the version and version is closed. But this blocking also happens when trying to move a status INTO a closed state. https://community.openproject.com/wp/30590	5 years ago
ulferts	cc0145daf6	prevent useless edits to wp status In case the fixed version and the status of a work package are both closed, the status of a work package cannot be altered any more. Attempting it will result in an error. Before the fix, the possible status calculation would not factor in that situation and the status would be marked as writable regardless as well. Therefore, the frontend would display a list of statuses even though selecting one would do nothing at all. Now, the status property is marked as non writable in such a situation and the status list will only contain the current status. As we only fetch the form after a click on the edit field, we can only disable the field after that which is a bit weird.	5 years ago
ulferts	6e9e7a4de4	adapt specs	6 years ago
ulferts	6c3c7003e2	provide necessary permissions in specs	6 years ago
Jens Ulferts	9b99fd4b43	adapt specs	6 years ago
Oliver Günther	ad43a7ea95	Prepare for core integration	6 years ago
Oliver Günther	3ba6913960	Implement read-only work package attributes based on status	6 years ago
Oliver Günther	3807bc4f7f	[28446] Rename due date to finish date https://community.openproject.com/wp/28446	6 years ago
Oliver Günther	059770f533	FactoryGirl => FactoryBot Removes the deprecation	7 years ago
Oliver Günther	ea8daa63af	FactoryGirl => FactoryBot (belongs to opf/openproject#6304 )	7 years ago
Oliver Günther	6ef4211e77	Bump copyright to 2018 (#6171 ) [ci skip]	7 years ago
ulferts	83e605e63c	allow setting parent that has relation via new siblings (#6114 ) [ci skip]	7 years ago
Oliver Günther	3facc5851d	[26829] Patch reform-rails to use activerecord i18n_scope (#6105 ) The validator passed to AM::Error does not use the `i18n_scope` we define on either Reform::Form or the model, but is delegated from the included AM::Translations module. This in turn causes I18n to lookup the scope `:activemodel`, failing the localization. https://github.com/trailblazer/reform-rails/issues/56 https://github.com/trailblazer/reform-rails/pull/35 [ci skip]	7 years ago
ulferts	6b9e7066fd	streamline relation in hierarchy error message (#6056 ) [ci skip]	7 years ago
Jens Ulferts	690e0ffc60	wp create/update/destroy via services	7 years ago
Jens Ulferts	9b4a09f677	adapt to changes in core	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
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
ulferts	21571ac3a2	Fix/add child rescheduling (#5499 ) A work package that is to be added as a child needs to be rescheduled to not validate any constraints posed by relations the parent work package might have [ci skip]	8 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Jens Ulferts	f40d84cc02	move contracts from lib/api to app/contracts	9 years ago
Jens Ulferts	143400629c	use variable in shared context	9 years ago
Jan Sandbrink	b374ebdd7f	store messages alongside error symbols - allows to skip translation part in ErrorBase - allows to have correct translations containing placeholder values	9 years ago
Jan Sandbrink	8f110d8b93	adapt specs to new contract behaviour - also refine specs for done-ratio to check for non-fail when not changed - use shared examples for parent properties also in done ratio specs	9 years ago
Alexander Bach	3ee80e98e8	Correct work_package_contract filename	10 years ago
Alexander Bach	410e483fef	Provide more flexible structure for work package contract validations	10 years ago
Alexander Bach	3bf80ad5c0	Correct work_package_contract filename	10 years ago
Alexander Bach	ea2196e269	Provide more flexible structure for work package contract validations	10 years ago
Alexander Bach	b76b8a5e7d	Added missing specs for new start & due date constraints	10 years ago
Alexander Bach	b650bd1819	Increased spec name consistency	10 years ago
Alexander Bach	dec702c59c	Added contract specs for estimated hours and percentage done	10 years ago

26 Commits (317d90444f7d7ec47b2b9f1e5e62bf85ba4a9410)