This was initially a request in the workplace project but we decided that it will be better to implement it in core first for all core data sources that include user entity: Users, User badges, Course participants, etc.

When it is implemented in core LMS, we will add it also to the Workplace report sources. I just want to avoid doing it twice or implementing it differently and then having inconsistent reports.

Original description by carli.cockrell@moodle.com:

It is a common occurrence that our Workplace clients need more granular grouping than tenant-level grouping, and so cohorts > groups are often utilized for this. However, this is not always done via a profile field; it can be done via direct upload to cohort, user selected cohort, manual cohort assignment, etc. 

Therefore, we have a need to have both a condition and a filter for Report Builder that allows us to specify cohort. 

This need is higher for our clients wishing to not utilize organization structure. These clients are typically selling their content via a tenancy-level agreement with their customers, and thus, management of an organization structure in those instances is too complex for their use cases. 

Need: Report builder condition of cohort. Filter of Cohort.

Who Needs This: Clients not using organization structure. Clients reselling content where the management of an org structure is too complex. Clients needing more granular grouping structures per tenant than tenant-level grouping.

Why: Being able to filter by cohort (as the mechanism cohort > group is often used with bundled plugins) will allow us to help our clients create program, certification, certificate, and course reports for each cohort.

Known Complexities: We understand that cohorts are a site-wide feature, and therefore, a sitewide admin may need to be the role that can create these reports with these conditions and filters for Tenant Admins and other tenant-specific roles.