WHY? JUST WHY?
Hi @Roman_Karabut can you please clarify what you mean or what your feedback is here?
HI, @Roman_Karabut @Marie
Maybe, but arenāt you wondering about this screenshot?
Please let me know if there is a help page for this.
I feel like itās similar to this.
Why did you changed custom field appearence? Everything was ok! Where this idea came from???
Just change it back as it was
Anybody else not pleased with how Custom Fields is now pushed back further and not aligned with the rest of default fields on Tasks? This is such an eyesore. It used to look better and aesthetically pleasing. Now it looks crowded.
Even Priority is not safe from the update
EDIT: after hours of using it it has sink in to me. The only thign i find off about it is thereās a waste of space under the column named āFieldsā.
Same space would be wasted Projects and Dependencies when there are more of them.
I think not utlilising this space makes it more scannable.
Hi folks and thanks for your feedback.
Weāve introduced tables for custom fields to make it easier to scan and use custom fields. We ran an A/B test with 50% of our user base over the last five weeks and got positive results, which is why we decided to roll it out to all customers yesterday. We donāt plan to revert this update right now, but I have shared your feedback with our team and will share an update here if we decide to make any changes in the future.
I was not included in the A/B test, but I like the table layout for custom fields.
Recently these tables have been added to the task info pane. We are not finding it to be particularly helpful and actually somewhat distracting if there are projects with numerous fields being pulled in. If this is a test of the feature, our organization has not seen much use for it and would prefer not to see them.
Iāve merged your post into an existing thread where you can click the title to scroll to the top and vote by clicking the purple Vote button.
Thanks,
Larry
Is there any chance that we could choose the layout that we like - table or previous format of fields? Because table format hinders the ability to carry out normal work duties.
The custom-fields list is shown at the right side of the āFieldsā section and I understand that it is this way to mantain the two-column table aspect, were the āFieldsā title is located inside the first column and the custom-fields are located inside the second column.
I think this two-column table aspect could be changed for the custom-fields in order to use a large area that is been lost in the first column. This can be done making the āFieldsā title ocuppy two columns and the custom-fields list too.
This tiny change could avoid the custom-fieldās line breaks or in software words, word-wrap less, resulting in general shorter scroll size of any Task.
I made some html changes to an Asana task page to show what I meant, side by side in the image below. Left side is the original design and the right side is the changed one:
As we have a topic on this already Iām merging this into it: New grid layout for custom fields