Details
-
Improvement
-
Status: Waiting for peer review
-
Major
-
Resolution: Unresolved
-
4.2
-
None
Description
The course participants report source (MDL-74364) introduced some new entities, one of which was the enrolment entity
The entity refers to "User enrolment" data, but also squashes in some elements that really belong in their own entities:
- Enrolment method column and filter should both belong to an 'enrol' entity;
- Role column should belong to a 'role' entity - this would also normalize the JOINs on this column and remove redundancy/duplication on the context table
In doing so, we'll create clearer reporting with more in-depth data on both enrolment methods and/or roles. The 'role' entity specifically is required for MDL-76902
Columns
- Enrolment method
- Plugin
- Name
- Enabled
- Duration
- Start
- End
- Role
- Name
- Short name
- Description
Filters/Conditions
- Enrolment method
- Plugin
- Enabled
- Duration
- Start
- End
- Role
- Name
Note that this issue should also introduce an API to allow for old report elements (columns, filters) to be deprecated
- Existing elements already present should display in the report as normal, and emit debugging;
- They should not be listed in the report editor to allow for selection in new reports
Also discovered MDL-76901 while looking at this - setting it as blocker because it'll make the debugging less noisy and allow for easier debug assertions in tests
Attachments
Issue Links
- blocks
-
MDL-76471 Custom report filter by enrolment name
-
- Waiting for peer review
-
-
MDL-76902 Create "Course categories" custom report source
-
- Waiting for peer review
-
- is blocked by
-
MDL-76901 Custom reports are inefficient in requesting persistent element data
-
- Closed
-
- will help resolve
-
MDL-77122 Participant role view Course Participants screen
-
- Open
-