We are having the same issue. Ideally, the tasks should always show as the project color and the tag colors should always show as little boxes, even if the project has no color. Otherwise, if you have a blue project, and a task with a blue tag in a project with no color, it looks like that task belongs to the blue project.
After speaking with a few people on my team I’ve learned that the color you’re seeing is actually correlated to the first addition to your task. So, if the tag was created first, then you’ll see the tag color; whereas if the project was created first, then you’d see the project color. This is something we know is not ideal, so we have a PM exploring possible updates. I’ll keep you posted on what happens next and I encourage you to visit the monthly release notes in the Announcements category for ongoing updates.
I’d love to throw our teams’ weighty behind this critical feature request. We absolutely require the ability to control event color in Calendar view, and like many others, expect the Project color to be primary. For us, custom metadata fields are useful, but secondary. Only our power users would be able to comprehend metadata colorization as primary, we need a default setting that “makes sense” at first glance, to casual users.
Having the same concerns with the task color not being associated with the project color and rather a custom field. Are there any updates to this issue? Really doesn’t create a good visual experience when there are so many different colors in calendar view.
Are there any news? I’m having the exact same issue and can’t seem to find a solution.
+1 for this. A very crucial thread
Big Big Big plus one for us too!
Hello. Plus one here. Is there news about this ? Thank you.
Is there a solution to this yet? I created my cards first @Alexis so technically speaking the cards should be displaying the project default colour, not the tagged colour. The only way Calendar view works even more for me is to remove all the tags I’m associated with so I can understand which project each card is associated with.
Am definitely jumping on the bandwagon on this one. Project default colour in calendar view would be super helpful. Thanks in advance.
Are there any updates on this issue? Like many in the thread, I’d like to prioritize my project colour in my calendar view. Unfortunately, he colour-coding becomes a useless feature if it’s not consistent. Any insight from your team would be greatly appreciated.
Today I found out some solution:
Remove color from project
(set color to the white/grey default color in all involved projects)
Mark the Tasks with one colored Tag (tab+t) - and…
I have multiple tags per task, but I’d still like the task to show up on my task calendar as the Project Color.
I’d still love the ability to choose colors in the calendar view more easily!
I did the color study again and found some interesting conclusions. Would love to have someone else do the same thing to confirm (or not) my findings 🎨 If Van Gogh used Asana: a study about colors on Asana
Is there a fix for this yet? I can’t really keep track of my tasks without this feature fixed.
I would not be so sure this is a bug, why are you?
whether it’s a bug or not, having more control over what color your project is will only further our ability to have asana serve our workflows. being pinned down to the tag colors limits our ability to customize asana to function the way we need it to for our specific workflows.
Like many others have done on this post, I’d like to know what is the latest that Asana is doing (has done?) to address this issue of color-coding by project? I’ve seen a lot of people on here asking, but am not seeing any active responses from Asana here to keep their paying customers informed. Is someone from Asana moderating this thread, and can they please give an update? If I missed the answer somewhere, please kindly point me in the right direction. Thanks!
The way Asana manages the forum is by monitoring the requests and escalate them to the Product team. They do not say if they are working on it or not though.
Thanks. I sort of knew this. It just doesn’t seem like the best way to keep people informed, you know, letting their customers know that they hear us and providing help to resolve challenges we are facing. From as best as I can tell this issue was brought up at least 3 years ago (Nov 2017 according to some posts I have read), yet I haven’t found any solid answers/solutions from Asana, just testing and speculation from its users.