202 Commits (82e3df434c2645bd89594558772297564d4e44a1)

Author	SHA1	Message	Date
jwollert	ce0574119b	fixes estimated_hours validation on issues by explicitly making it fail on invalid input strings	12 years ago
Martin Linkhorst	c442ecb7d9	remove gantt from core (take the commit as a guide on how to bring it back as a plugin)	12 years ago
Christian Rijke	9be08a767e	Add a method to ensure the correct load order of core model classes with a circular dependency.	12 years ago
Philipp Tessenow	ef9ae5ffa3	use scope instead of named_scope	12 years ago
Philipp Tessenow	1f4f73c1d3	merge upstream changes (1f45cd3 - pull request #5). ... awesome nested set was deleted, so we take only half of the changes	12 years ago
Philipp Tessenow	479086af1a	fix class load order	12 years ago
Philipp Tessenow	3affd94490	Revert "wrap scope in lambdas to let the migrations run again" ... This update repairs rake db:migrate but breaks rails s. I'll look into this This reverts commit 7a405355f4.	12 years ago
Philipp Tessenow	7a405355f4	wrap scope in lambdas to let the migrations run again	12 years ago
Jens Ulferts	0d3be2f958	no longer serializes changes as they will be anyway ... Assigning an already serialized attribute to an attribute that will be serialized by active record is disabled due to security issues (rails 2.3.17)	12 years ago
Jens Ulferts	2c22694e98	eager loads objects associated to the issue's relations	12 years ago
Jens Ulferts	3adca91704	overrides awesome_nested_set methods for issues to allow for fixing the ... root_id The root_id provides the scope for a nested_set tree. The implicit constraint of the Issue implementation is that there is but one tree per scope. Or in other words, the root_id is part of the nested_set attributes for an issue. This is not the case for Project, which is also using nested_set but does not set a scope. Project's are ordered that way. The root_id should always point to the root of an issue tree. awesome_nested_set only looks for nodes without a parent in the provided scope to determine root nodes. For example, if the root_id of an issue should point to the node itself, this issue is considered to be a root node. This is regardless of the value of the parent_id. For such a node, nested_set methods will provide wrong issues when queried for root, ancestors and similar methods. Fixing a missconfigured root_id attribute is achived by traversing up the parent chain (parent_id) till an issue without a parent is found. The parent_id attribute is considered to be correct. The root_id is not really necessary for awesome_nested_set to work. But employing the field should be beneficial performancewise. Updating an issue tree requires less nodes' left/right attribute to be altered when the forrest is scoped.	12 years ago
Jens Ulferts	705200ec33	matches journaled field against regexp to be able to cope with dynamic field names ... Some plugin, e.g. acts_as_attachable and acts_as_customizable, dynamically add associations to a model following a schema, e.g attachments_[n], where n is increased over time.	12 years ago
Gregor Schmidt	9755b931dd	Extending API of recalculate_attributes_for ... This way we may not need to fetch an entry from the DB, where an existing object is already present. This might be of special intrest, when plugins alias-method chain recalculate_attributes_for and want to save a separate save call.	12 years ago
Gregor Schmidt	ccc97fcbfa	Optimization: Avoiding save if nothing changed ... this should avoid more callbacks being triggered and should therefor improve performance	12 years ago
Martin Linkhorst	232fa7d7b0	use a hash for yaml stuff	12 years ago
Philipp Tessenow	84e2729b98	REVIEW: another batch of the renaming effort from Journals#changes to changed_data	12 years ago
Martin Linkhorst	584e592bd4	active records' #attributes=() signature changed. so let's change as well	12 years ago
Martin Linkhorst	52294f5a68	active records' #attributes=() signature changed. so let's change as well	12 years ago
Martin Linkhorst	a89e22e2dc	remove attachments before destroying the issue to avoid getting a Activerecord::StaleObjectError	12 years ago
Martin Linkhorst	c17ffccfe2	REVIEW: update to the new AR api. hint: we need to update all :include => to fix all bugs since only a few of them are testiest	12 years ago
Martin Linkhorst	d9f422e6b0	use #joins instead of #includes since includes does seem to have a bug when combining with #maximum, #sum etc. ... this does an inner join instead of a left outer join so children without a priority at all won't be fetch. this should be fine since they wouldn't affect the maximum position value, which is requested here	12 years ago
Martin Linkhorst	d616d0574e	DEPRECATION FIX: use errors.add(:base, msg) instead of errors.add_to_base(:msg)	12 years ago
Martin Linkhorst	3419564990	DEPRECATION FIX: use save(:validate => false) instead of save(false)	12 years ago
Martin Linkhorst	71fe49e862	DEPRECATION FIX: use validate :method_name instead of overwriting the validate method	12 years ago
Martin Linkhorst	b6b27b904c	DEPRECATION FIX: use after_initialize :method_name instead of overwriting the after_initialize method	12 years ago
Jens Ulferts	d088bbd3ae	resourcifies issue_relations ... * removes rjs	12 years ago
Jens Ulferts	99bc0daaf9	replaces awesome_nested_set#leaf? with a query for whether a parent_issue is present ... #leaf? now returns false if (persisted? && ...) formerly all new_records where considered to be a leaf	12 years ago
Martin Linkhorst	b6aac286d4	take the root Query class rather than active records. also re-allow passing an order to acts_as_nested_set. all to make the tests happy	12 years ago
Martin Linkhorst	b49e0207a5	fix nested issues tests (1 test still fails from time to time :()	12 years ago
Jens Ulferts	3e633fc27e	renames all named_scopes to scopes ... * named_scopes are deprecated in rails 3	12 years ago
Jens Ulferts	0c996d9768	set parent_issue_id to nil if no cross project issue relations are allowed but would result after move	12 years ago
Jens Ulferts	7d76b8f53d	validates an issue with parents in a different project depending on whether cross project relationships are allowed ... * forces mass assignment in tests	12 years ago
Romano Licker	73c087e19c	reset author to current user when copying an issue	13 years ago
Romano Licker	44f48962bf	automatically fill the parent_id field when duplicating an issue	13 years ago
jwollert	d9f6b52029	protect relations to users (assigned_to, author_id etc.) in models, too	13 years ago
Martin Linkhorst	337561261a	some documentation regarding mass assignment, show full stack trace in console	13 years ago
Martin Linkhorst	696ed97dcd	fix: use the old style #force_attributes	13 years ago
Martin Linkhorst	12bb66c264	refactor dealing with mass assignment	13 years ago
Martin Linkhorst	42bc728288	fix to work with protected :project_id	13 years ago
Martin Linkhorst	1fce5b6a8f	added attr_protected calls to protect mass assignment of :project_id through a view	13 years ago
jwollert	934d22ec67	protect relations to users (assigned_to, author_id etc.) in models, too	13 years ago
Martin Linkhorst	4e9c17fca8	some documentation regarding mass assignment, show full stack trace in console	13 years ago
Martin Linkhorst	bfc4a441f4	fix: use the old style #force_attributes	13 years ago
Martin Linkhorst	7b34ebdc47	refactor dealing with mass assignment	13 years ago
Martin Linkhorst	c7e130f010	fix to work with protected :project_id	13 years ago
Martin Linkhorst	cc74c1e998	added attr_protected calls to protect mass assignment of :project_id through a view	13 years ago
Martin Linkhorst	fcac419324	better locking info. issue #25606	13 years ago
Romano Licker	d29112203b	fixes recreating initial journals ... the method now uses the acts_as_journalized methods when recreating the initial journal and tries to use existing journals for rebuilding the history	13 years ago
Romano Licker	3506a0327f	journalize parent_id on issues	13 years ago
Felix Schäfer	12bbcd0966	Allow subtasks to cross project boundaries.	13 years ago