-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fixed column header on Kanban boards #7105
Labels
for experienced contributor
prio: med
scope: front
Issues that are affecting the frontend side only
size: short
type: design improvement
Comments
Bonapara
added
good first issue
Good for newcomers
scope: front
Issues that are affecting the frontend side only
size: short
type: design improvement
prio: med
labels
Sep 17, 2024
can i work on this ? |
Sure @dilshad-knk, thanks for contributing! |
dilshad-knk
added a commit
to dilshad-knk/twenty
that referenced
this issue
Sep 25, 2024
dilshad-knk
added a commit
to dilshad-knk/twenty
that referenced
this issue
Sep 26, 2024
@Bonapara |
Would be great, thanks @ehconitin! |
This issue is not part of oss.gg hackathon. Please pick a different one or start with a side quest |
ehconitin
added
for experienced contributor
and removed
good first issue
Good for newcomers
labels
Oct 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
for experienced contributor
prio: med
scope: front
Issues that are affecting the frontend side only
size: short
type: design improvement
Current Behavior
Currently, Kanban column headers are not fixed. When the page is scrolled, they disappear.
CleanShot.2024-09-17.at.18.16.57.mp4
Desired Behavior
Change the column header position to fixed so they stay on top while scrolling the page
Video to explain the expected behavior:
CleanShot.2024-09-17.at.18.24.22.mp4
Figma
Introduce a 40px heigh column header container
https://www.figma.com/design/xt8O9mFeLl46C5InWwoMrN/Twenty?node-id=24955-194300&node-type=frame&t=vjg6Ofev4bkaijG1-11
The text was updated successfully, but these errors were encountered: