Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent event menu actions when multiple events are selected #6037

Closed
marciogurka opened this issue Jan 24, 2023 · 0 comments
Closed

Inconsistent event menu actions when multiple events are selected #6037

marciogurka opened this issue Jan 24, 2023 · 0 comments
Assignees
Labels
bug Something isn't working forum Issues from forum large-account Reported by large customer OEM OEM customer premium resolved Fixed but not yet released (available in the nightly builds)
Milestone

Comments

@marciogurka
Copy link

Forum post

"Hello,

I noticed a UX inconsistency between event menu actions when multiple events are selected.
Most actions are triggered on all selected events (cut, copy, paste, delete...), but "unassign" only applies to the event the menu was triggered on.

Could we make "unassign" apply to all selected events as well?
"

Added a video with the behavior on multi-assignment demo

Bryntum.Scheduler.-.Multi.assignment.demo.-.24.January.2023.mp4
@marciogurka marciogurka added bug Something isn't working premium forum Issues from forum large-account Reported by large customer OEM OEM customer labels Jan 24, 2023
@matsbryntse matsbryntse self-assigned this Mar 29, 2023
@matsbryntse matsbryntse added ready for review Issue is fixed, the pull request is being reviewed resolved Fixed but not yet released (available in the nightly builds) and removed ready for review Issue is fixed, the pull request is being reviewed labels Mar 29, 2023
@matsbryntse matsbryntse added this to the 5.3.2 milestone Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working forum Issues from forum large-account Reported by large customer OEM OEM customer premium resolved Fixed but not yet released (available in the nightly builds)
Projects
None yet
Development

No branches or pull requests

2 participants