237 Commits (d0f6c2e76aa194b25b484d0bded3048c85c0b994)

Author	SHA1	Message	Date
Hagen Schink	7609698a0d	Renames and adapts issue version error translation	11 years ago
Jens Ulferts	7130428ff3	unifies activity across work packages ... This also changes back acts_as_activity_provider from using joins to includes. Joins do not eager load which is required for avoiding requests on activity rendering	11 years ago
Martin Czuchra	38098eac5b	Moves methods out of issues into work_packages. ... Moves new_statuses_allowed_to and is_milestone out into parent class.	11 years ago
Hagen Schink	69477d434c	Moves copy/move methods to work package	11 years ago
Hagen Schink	d11c442aa0	Moves up allowed target projects query method	11 years ago
Jens Ulferts	b9590aff9a	patches nested_set to add tree rebuilding methods that are not using ... save The original nested_set implementation uses save on each node (issue, project). With the callbacks defined on issues, this can lead to stale object errors when an issues has been loaded by the rebuilding method but changed by a callback. The rebuild_silently! method can also take root nodes as their parameter. With such provided the method will only fix their trees. This is build upon by the selectively_rebuild_silently! method which first looks for invalid nodes, determines their root node and then calls rebuild_silently! with those root nodes. This should speed up rebuilding on large trees. Additionally, methods where added as a byproduct to retreive nodes who's tree attributes are invalid.	11 years ago
Jens Ulferts	fcc51fa8e2	allow hierarchies between Issues and PlanningElements by moving methods up	11 years ago
Jens Ulferts	ae7e5aae3b	replaces parent_issue_id with parent_id whereever it was to be found	11 years ago
Jens Ulferts	5d3b70928c	moves after save hooks to work_package	11 years ago
Jens Ulferts	247436ca38	moves scoped nested set into own module, applies to WorkPackage	11 years ago
Hagen Schink	fbda734b59	Moves methods from issue to WP	11 years ago
Jens Ulferts	c5f40d84c4	enables logging time on update	11 years ago
Jens Ulferts	36b9870cd6	allows for rendering pdf from work_package#show ... This will break changset rendering on the issue page	11 years ago
Jens Ulferts	293e8a7b7f	changes changeset_issues join table to be changeset_work_packages ... This will enable workpackages (issues and planning elements) to have changesets applied	11 years ago
Martin Czuchra	847a3029a9	Renames Tracker into Type.	11 years ago
Jens Ulferts	a84166c2e0	readds accidentally deleted relation cleanup ... However this needs to be moved to work packages somehow so that relations on planning elements are cleaned up likewise	11 years ago
Jens Ulferts	ceb9156a0b	returns empty allowed_status if the issue currently has none	11 years ago
Jens Ulferts	1174a69db0	adds an early version of having a unified new action/view for issues/planning_elements	11 years ago
Hagen Schink	14f9c847a6	Pull method up refactoring	11 years ago
Hagen Schink	2da6c7a900	Pull method up refactoring for costs	11 years ago
Hagen Schink	89544eb63f	Move relations to work package	11 years ago
Hagen Schink	005115828f	Move to_s to work package	11 years ago
Hagen Schink	a6f83f1d3c	Adapt references to work package	12 years ago
Hagen Schink	05f2f300fc	Introduce work unit permissions	12 years ago
Hagen Schink	8baacde427	Fix tests	12 years ago
Hagen Schink	82d2400cf0	Let issues work via STI	12 years ago
Christian Ratz	303ec4a695	fixed some typos for disabled issue attributes	12 years ago
Christian Ratz	ec5f0dd51c	added cukes for issue#new and issue#edit ... - checking for attributes which are overridden by childs - new step to find disabled elements	12 years ago
Jens Ulferts	21459a384f	provide every possible file with a short copyright notice ... This was done using the rake task: rake copyright:update	12 years ago
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