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.

Sign up for GitHub

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

Jump to bottom

Final schedule shifts should lay in one line #1665

Closed
Matvey-Kuk opened this issue Mar 30, 2023 · 0 comments
Closed

Final schedule shifts should lay in one line #1665

Matvey-Kuk opened this issue Mar 30, 2023 · 0 comments
Assignees
@maskin25
Labels
feature request New feature or request part:schedules

Comments

@Matvey-Kuk
Copy link
Contributor

OSS & Cloud V1.2.3

Final schedule shifts should lay in one line (except when two users are at the same time slot). Especially valuable for the list of schedules.

image
@Matvey-Kuk Matvey-Kuk added bug Something isn't working part:schedules labels Mar 30, 2023
@joeyorlando joeyorlando mentioned this issue May 15, 2023
Closed
@Matvey-Kuk Matvey-Kuk added feature request New feature or request and removed bug Something isn't working labels Jun 7, 2023
@maskin25 maskin25 mentioned this issue Jul 26, 2023
Merged
3 tasks
github-merge-queue bot pushed a commit that referenced this issue Aug 4, 2023
merge final schedule in as less lines as possible (#2649)
8412282 
# What this PR does

Merge final schedule in less rows

## Which issue(s) this PR fixes

[Final schedule shifts should lay in one
line](#1665)

## Checklist

- [ ] Unit, integration, and e2e (if applicable) tests updated
- [ ] Documentation added (or `pr:no public docs` PR label added if not
required)
- [ ] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not
required)
@matiasb matiasb closed this as completed Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maskin25 maskin25

Labels
feature request New feature or request part:schedules
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@matiasb @maskin25 @Matvey-Kuk