Skip to content
Snippets Groups Projects
New look: Off

`ours-end` conflict solution offered in nonsensical scenarios

    • Closed Issue created by Konrad Mohrfeldt @kmohrf

    As far as I understand it ours-end should cut the existing timeslot. Specifically: the end time of the new timeslot will be used as the start time of the existing timeslot.

    Example:

    • an existing slot starts at 06:00 and ends at 07:00
    • a new slot is created which starts at 05:45 and ends at 07:15

    This looks like this in the dashboard conflict view:

    Screenshot_from_2024-04-10_23-14-17

    Steering shouldn’t offer the ours-end solution for this, but it does. Following the description from above the start time of the existing timeslot will be changed to 07:15.

    This creates the following situation:

    • a newly created timeslot from 05:45 - 07:15
    • a modified pre-existing timeslot from 07:15 - 07:00 (negative 15 minutes duration)

    This is also reflected when applying this solution.

    Screenshot_from_2024-04-10_23-33-11

    Note: this triggers two bugs in the dashboard:

    • the default height for events is used because it can’t handle negative durations implying conflicting timeslots in the week view
    • the label is hidden because it is assumed that the "short" duration will not leave enough place to render a label
    Edited

    Designs

      Child items ...

      2. Activity

      Please register or sign in to reply