Echoing what Ben & Corinne said, the functionality was already in place as the “set for everyone” was already the default and any personal changes did not erase the project color which had been set and I am frankly struggling to see the benefits of removing the personal colors entirely.
Surely, a better idea would’ve been to add a toggle at the company level to enable the “set for myself” option for users’ project color changes. That would’ve allowed organizations where the shared project color was a necessity to implement their system while enabling other organizations to maintain their personalized colors and accommodate their workflows and styles.
Was this not considered? Can it be added as a toggle now? Looking forward to your response
3 Likes
Adding to this thread to add more voices. This reasoning makes no sense - “set for everyone”, which was a feature in the previous setup, would have solved the issue the users you are describing were facing.
Even so, another solution could have been a lock feature for project owners - that way the owner of the project can determine if the color can be changed. I now own several boards in my organization, and people keep changing the colors because there is no way to lock the color to be what I have assigned it.
This entire change has caused chaos because people don’t realize their change is now affecting the whole org. Bring back individualization and add a feature for project owners to lock the color so the issue you described in your reply is resolved and we also all get our personalization back.
4 Likes
I would love to know the status of a resolution for this issue. This is a daily frustration and things I used to manage completely in asana I have had to partially back out because of how I can no longer rely on a consistent coding system. Since our company doesn’t have or need a mandated color coding structure many users can change the color, this means some of my projects change color every other day now as many users ping back and forth to their preferred color not understanding why it has changed. This was not rolled out with an explanation, you had to dig for the why. Especially in conjunction with the new side bar I am truly struggling to operate well in the new UX and nothing can remain organized in a way which is functional for my cognitive processing. I have tried adding portfolios but some projects become lost this way as it is a less frequently used portfolio. I do see both sides, but this broke my workflow and many others and because of how flexy we are on color use as an org (whereas I need a rigid categorization) I cannot regain a standard flow for myself.
4 Likes
I’m assuming our requests have been ignored for restoring the ability to set our own project colors? I find it confusing that you would decide to remove a feature that many found incredibly useful. Like Henry and Christina mentioned, why not allow project owners or account administrators dictate whether or not they would like to allow that feature? Any update on this matter would be greatly appreciated.