Uploaded image for project: 'Opencast'
  1. MH-12992

Conflict checking in "Edit scheduled events" should only be done when clicking "Next"

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed and reviewed
    • Affects versions: 5.0
    • Fix versions: None

      Description

      Conflict checking can be fairly slow on large systems with lots of scheduled events. Currently, when you select a few of those events and open the "Edit scheduled events" tab, changing a single item, such as the start time, will already trigger a conflict check. If this takes very long then, it's bad for usability.

      It would be better to just check the conflicts when the user is "done editing" and clicks the "Next" button to see the changes that will be made.

        TestRail: Results

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                middendorf Philipp Middendorf
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  TestRail: Cases