Correct, columns = sections. Unfortunately thatās fixed; you canāt choose to have Board columns be anything other than sections (and vice versa on Lists).
I donāt recall seeing a request for that to be more flexible, so you might want to create a new post with that suggestion here in the Product Feedback area, so folks can vote on it.
Also FYI, if you want to have a āstatusā custom field thatās automatically kept in sync with a taskās column, you can easily do that using an If-Then Rule in my Flowsana integration.
@Alexis Any word on the progress for this feature request? Just switched to Asana and Iām really surprised this is a two-year old request apparently without progress.
We are new Asana users and can already see the ability to swap view essential, afterall when working across a team we need to adapt to individuals own preferences
@Josh_Garcia, i too became very frustrated about the wait. However, i noticed through this thread what the dev team actually has to accomplish in each customers Asana. They have to export data and re-insert data so that you dont lose anything. Adding the function by flipping a switch would be detrimental to what you have already. So using their diligence, they have decided to handle each customer separately and carefully. I will say that last weekend we were updated and I am very happy with the results. Well worth the wait.
This is good to hear as Iād like to do that to our projects as I am new and the way it was setup prior is confusing to some on staff. We are a little guy though so it may take a while to get to us.
Asana does not share information about roll out speed or progress. You just need to wait I got the feature only a few days ago, some got it months ago.
In my opinion this āswitchingā implementation is totally flawed. Asana has elected to use sections as the board statuses and completely missed the point. This is totally counter-intuitive. Lists and boards are completely different animals. Boards by nature are status driven (ie backlog, doing, waiting, done etc). List view is generally used for a more flexible approach to planning. I know that you can still sort by custom field, but honestly IMO Asana should have implemented an independent mechanism for boards (ie statuses) with the list sections retained. At the very least there should be a choice for each project. (Board column could simply have appeared as a field in list view)
I donāt think anything has been achieved by this update. I still have to create a separate board for kanban status if I want to retain my independent list structure. NOT HAPPY
I literally just had this realization today. I got all excited when I saw the update went live on our Asana account, and then immediately realized, āwaitā¦ how does this really help us?ā
For us, having the ability to change the column heading to a custom field would be huge!
I didnāt do anything. I understand that it went live a month ago for some users. Asana is now in the process of rolling out to everyone. Iām a premium user, but I am under the impression it will a freemium feature.
I finally got it, YAY but I have a questionā¦for some projects, when you switch from board to list, the columns come over as sections. On others, the columns do not come over and the list is a long laundry list. Does that mean Asana is still working on our rollover or is it just not consistent yet?