owner:jennifer@painless-security.com resolution_fixed type_defect | by rjsparks@nostrum.com
Right now, the session request views and the drag-drop scheduler have the notion of 3 constraint types (which until recently meant 1st, 2nd, and 3rd order conflicts) hard-coded.
Instead, the constraints to collect information on, and to display in the drag-drop scheduler should be part of a meeting's configuration.
The hack put in in response to #2754 should be reworked so that new constraints are used to reflect the three new constraint types. Data from ietf106 (and hopefully not future meetings past that) will need to be migrated to use the new constraint types.
The drag-drop scheduler should be adjusted to deal with an arbitrary number of constraints.
Issue migrated from trac:2770 at 2022-03-04 07:14:46 +0000
owner:jennifer@painless-security.comresolution_fixedtype_defect| by rjsparks@nostrum.comRight now, the session request views and the drag-drop scheduler have the notion of 3 constraint types (which until recently meant 1st, 2nd, and 3rd order conflicts) hard-coded.
Instead, the constraints to collect information on, and to display in the drag-drop scheduler should be part of a meeting's configuration.
The hack put in in response to #2754 should be reworked so that new constraints are used to reflect the three new constraint types. Data from ietf106 (and hopefully not future meetings past that) will need to be migrated to use the new constraint types.
The drag-drop scheduler should be adjusted to deal with an arbitrary number of constraints.
Issue migrated from trac:2770 at 2022-03-04 07:14:46 +0000