Request for New Functionality: Freeze Top Row for Better Navigation

Why? I am trying to achieve better navigation and data comprehension when scrolling through large datasets or long lists. Keeping track of column headings (Rows) becomes cumbersome without a fixed top row.

Current Workaround Currently, there is no effective workaround to keep the top row visible while scrolling. Users have to constantly scroll back up to see the headings, which is inefficient and time-consuming.

Suggestion Implement a feature that allows the top row to be frozen. This way, as users scroll up and down, the headings remain visible. This functionality is commonly found in spreadsheet applications and has proven to be very useful. Incorporating it into our system would significantly improve usability and efficiency for all users.

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Tiffany Sands

Hi @Tom Halbert Our top rows in tables and in Data Hub are frozen. Where are you seeing data without a frozen top row?

Basudha Sakshyarika

Hi @Tom Halbert! Welcome to the Community 🙋🏻‍♀️

I have the same question as Tiffany. Can you please share more details about the dataset or list you are referring to where the top row is not frozen? Thank you!

Tom Halbert

It is just a table that is created on a wrike task. I have entered the dataset.
Can you please show me how to freeze the top row headers of a table added into wrike
Cheers

Basudha Sakshyarika

@Tom Halbert: To clarify, are you adding the dataset within the task description? If so, the system doesn't currently support freezing the top row headers in tables created there. Task descriptions are primarily intended for brief text and notes related to the task, so using them to store large datasets can lead to clutter and make data management difficult.

If you could share more details about your needs, I can look into other solutions that might help. 😊

Tom Halbert

Thanks @Basudha Sakshyarika for the information.

It sounds like it is not currently available, and we may not be using the product correctly.

We are currently creating TASKs in Wrike and having all the sub tasks together in that one task. It saves time having them in tables than creating all little individual tasks for the larger project in one. This makes it easier to see all of the tasks all of the notes and steps of the task. We do break them up until smaller tasks for different projects which are more complex but when we have many little steps to be completed by many different staff members it is easier to see it all in one space - or at least the team here thinks so.

Example:

Rather than have 10 tasks in the project we would have one project with a table of the tasks to complete. The simple tasks have the description of the task, the person, the time and who is to complete.

1. Turn on Webserver
2. Allocate Permissions
3. Move Dataset to Position A
4. etc etc

Having it in one Task, rather than lots of little tasks, is easier to see it from a glace and get the important information - it also helps when we are sharing this with third-party vendors.

Another example I personally use is when needing to make updates to my datasets which happens regularly.

I may have 50 subjects I am required to update a specific data point depending on if they are new, old or needing to be updated.
Using a table allows me to keep all the information in one spot but the filtering does not allow for easy viewing. A workaround would be to create this as an excel document and use the functionality of excel rather than what Wrike can offer. It is a little annoying since I would need to create the document, populate it, upload it to Wrike and then delete the file on my computer so I can use just the one on Wrike.

We will continue to work on the solution and increase our ability to use Wrike as intended. I hope my explanation has given you a taste of why it could possibly be useful for your clients.

Thanks,
Tom

Basudha Sakshyarika

Hey @Tom Halbert! 🙋🏻‍♀️ My apologies for the delayed response—your comment was accidentally overlooked. Thank you for sharing your use case; it completely makes sense. I’ve now forwarded it to our product team for consideration. Thanks again! 👍🏽