openproject

Commit Graph

Author	SHA1	Message	Date
Oliver Günther	8fa78e4b5a	Fix more specs	7 years ago
Oliver Günther	67b57b8a04	Code style	7 years ago
Oliver Günther	7dc9df3aee	Adapt specs to factory pattern	7 years ago
Jens Ulferts	c61619b6ef	limit custom field filters by cf visibility	7 years ago
Jens Ulferts	b815d730af	move part of allowed_filter calculation to query/filters	7 years ago
Jens Ulferts	403bf905e9	extract custom field filter into shared mixin	7 years ago
Wieland Lindenthal	a7cea140fd	Fixing specs	7 years ago
Wieland Lindenthal	39f53d2a00	Create filters and use query object to replace current state of project list filters	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	e7294110c0	[26392] Don't map value objects to nil (#5955 ) https://community.openproject.com/wp/26392 [ci skip]	7 years ago
Oliver Günther	97f7c3a592	[26298] re-add filtering by mail through special filters (#5915 ) https://community.openproject.com/wp/26298 [ci skip]	7 years ago
Oliver Günther	fdfb41b327	[26069] Allow passing of me-value link for principal filters again The 'me' value is currently automatically normalized to the current user, making it impossible to store queries that reference the current user whenever accessing the query as before.	7 years ago
Oliver Günther	75d2f010ba	[25108][26176] Assigned_to filter returns group values Since 7.0.0, the `assigned_to is <user>` filter also returns work packages assigned to a group that `<user>` belongs to. Since this is misleading and judged a bug by several customers, instead add a new filter that provides exactly this behavior, while using `assigned_to` only for the exact value specified there. https://community.openproject.com/wp/26176 https://community.openproject.com/wp/25108	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
ulferts	daa1a4d4b7	fixes filtering members by group (#5800 ) additionally fixes: * with "all" selected, all members are shown, not only those being active, invited or registered * with "locked" selected, locked users are now displayed. * the Project#members_principals associations lacked the `references` method which lead to the users table being undefined in the resulting query. In order to achive the bug fixes, the member filtering is now based on the query engine also used for users, queries, work_packages, ... As a lot of the members filters are very similar to user filters (in fact, a lot of the members filter work on the users model), those filters are shared via modules. [ci skip]	7 years ago
ulferts	4d95cc815f	Feature/guarded relation columns (#5784 ) * refactor case statement * guard relation columns by enterprise token [ci skip]	7 years ago
ulferts	39bbf082bf	fix author filter for projectless users (#5718 ) As the principals returned by the principals API where limited to those that are members in projects the user can see, users not having any project would not be returned. This is intended in so far as to prevent getting all users easily. But the user herself should be visible in any case. [ci skip]	7 years ago
ulferts	fc139e55df	limit visibility of relations index (#5703 ) [ci skip]	7 years ago
ulferts	55695ed756	adds query columns by relation type (#5625 ) [ci skip]	8 years ago
ulferts	20dd8a6e0a	Feature/work package id filter (#5614 ) * add filter for work packages by id to query * hide the id filter in front end As we do not yet have satisfying means to display the filter values for selection, we hide the filter and use it internally only [ci skip]	8 years ago
ulferts	ace7098eb3	add relations columns to query (#5606 ) * add relations columns to query * refactory query columns * rename QueryColumn to QueryColumn::Property QueryColumn is now only an abstract supertype [ci skip]	8 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	86c2f3d59d	Fix/increase query api robustness (#5574 ) * removes unavailable filters on valid_subset! * remove invalid columns on valid_subset! * cleanup query form and collection * code prettification * add status to spec in order to have valid queries [ci skip]	8 years ago
ulferts	2a71172837	prepare the query before reading results (#5547 ) * prepare the query before reading results * use string for list cf filter value because all other list filter also use a string * handle invalid group, columns, sort on query read [ci skip]	8 years ago
Jens Ulferts	ed7cea0f39	fix relations type filter * specified as type in api documentation whereas the key used to be relation_type * using list type as we have a fixed set of possible values	8 years ago
Jens Ulferts	8aebddb606	splash groups on assignee filter	8 years ago
Jens Ulferts	1fe880ad1b	prevent query filters loosing their context	8 years ago
Jens Ulferts	a4ae0e9b65	allow active, invited and registered users to be filter values	8 years ago
Jens Ulferts	b01681d328	increase custom field filter robustness	8 years ago
Jens Ulferts	8a08856748	replace string object by custom option for list custom fields	8 years ago
Jens Ulferts	33545b9e39	refactor query filter statements into distinct classes	8 years ago
Jens Ulferts	4a571ecf9f	avoid NotFound for invalid principal filter values	8 years ago
Jens Ulferts	d80d8b1ecc	adapt list custom field filter to alterations caused by multi select	8 years ago
Markus Kahl	f5a57e3f42	list custom field normalisation and multi select	8 years ago
Jens Ulferts	c4bef2247d	adding filter instance schemas	8 years ago
Jens Ulferts	27362f785a	embed filters as objects	8 years ago
Jens Ulferts	80c242dd53	embed query results in query representer This is only done when the representer is not embedded itself, e.g. when it is part of a collection.	8 years ago
Carsten Klein	8c1631f4f9	Filter by date and date range. https://community.openproject.com/work_packages/24174	8 years ago
Oliver Günther	7cf11bb689	Update copyright notice	8 years ago
Jens Ulferts	a52c8ee07d	allow for filtering the queries in the API v3 Only implements the `project` filter for now which can be used to differntiate between queries from specific projects and can also be used to specify that the client is only interested in global queries	8 years ago
Markus Kahl	7ba5b261a6	added login filter; fixed status filter	8 years ago
Jens Ulferts	15899a98ba	never override .name - it messes with reloading	8 years ago
Jens Ulferts	c71a675ecd	introduce true/false db representation constants for cf	8 years ago
Jens Ulferts	d4e71fd67e	add user query and enabled it in the users api	8 years ago
Jens Ulferts	1a597e180b	first step towards generalizing the query and its filters	8 years ago
Jens Ulferts	c3013d6272	lazy load query filters and extract them into classes This allows us to only load the values we actually need instead of loading all the values regardless of whether we need them. This is especially usefull in the api where we currently never need those values. Note, that this is a glitch in my opinion as we do not check whether the filter value is valid.	8 years ago
Alex Coles	ce93701029	Fix syntax (w/Rubocop) in specs Signed-off-by: Alex Coles <alex@alexbcoles.com>	9 years ago
Alex Coles	3785fdc9ed	Use #describe, #context with String arg not symbol The semantics of `describe` have changed in RSpec 3: passing a symbol rather than a string will change the value of the described object. See discussion here: https://github.com/rspec/rspec-core/issues/1114 Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Alex Coles	e0191e759c	Update year in copyright header to 2015 [ci skip]	10 years ago
Alex Coles	03978767be	Use 1.9+ Hash syntax in specs Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago

1 2

64 Commits (44c601fbb1e5725c8ffcc3a5bbc00b9c429d679d)