-
Improvement
-
Resolution: Fixed
-
Minor
-
3.9
-
MOODLE_39_STABLE
-
MOODLE_39_STABLE
-
MDL-67917-master -
-
1
-
International 3.9 - Sprint 6, International 3.9 - Sprint 9
The following is an approximation of the filter language used:
filterset = jointtype (filter *(", " filter))
|
jointype = "All" / "Any" / "None"
|
filter = ([jointype] filterthing ?= filtervalues)
|
filterthing = "Group" / "Role" / "Keyword" / ...
|
filtervalues = filtervalue *("," filtervalue)
|
filtervalue = quoted-string
|
The initial part of the project will be to create a single filter. That is to say:
- A dropdown to select a pre-defined enumerated list for the Join Type (All, Any, None) for the current filter
- A dropdown to select a pre-defined enumerated list for the filterthing (Group, Role, etc.) for the current filter
- A way to select the values
For the initial work:
- we will only be creating a working interface, it will not have any effect on the data. Purely visual.
- I would advise chosing Status as this is a simple, enumerated list, with static values and low complexity;
- We will only create the initial filter. Not a full filterset
The follow-on work will then comprise of:
- Adding the remaining enumerated types (Groups, Roles, Enrolment methods)
- combining multiple filters into a filterset
- Adding the date since type. This is a single value filter ([number] days) and no jointype
- Adding support for non-enumerated types (date since, keyword)
The initial work will not be plumbed in. It will be an isolated interface until the backend is ready to receive it.
- blocks
-
MDL-68169 Add additional participants filter types and the ability to add multiple conditions to a filter set
- Closed
- has a non-specific relationship to
-
MDL-68167 Fix core/form_autocomplete accessibility issues
- Closed
- is blocked by
-
MDL-68286 Update table_sql to support dynamic initials bar
- Closed