Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-80941

Delegate to customfield instances themselves how they should be used in reports

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 4.4
    • Report builder
    • MOODLE_404_STABLE

      Allow custom field types to define how they should be used/displayed in custom reports - specifically:

      1. Their column type
      2. Supported column aggregation
      3. Their filter type

      This is a legacy hangover from Report builder in Workplace, and isn't sustainable now that more customfield types are proposed in both LMS (MDL-80858) and as third party plugins

      It also breaks our own rules regarding inter-component communication rules: https://moodledev.io/general/development/policies/component-communication#general-rules-for-inter-component-communications (because of said hardcoding of different types):

      1. Column type;
      2. Filter type

      While the above provide sensible defaults, they aren't a good long-term solution because the behaviour is removed from the customfield and is hardcoded

            Unassigned Unassigned
            pholden Paul Holden
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.