Asana Tags API colors new changes causing issues.

[John34]

Hello,

I work at Altosio and we migrate data from other Project management software to Asana, including Asana to Asana projects and portfolios migration.

We are recently having issues with one of our customers migration, where tags have changed names, and the new CreateTag API does not seem to take the name into account.

Two issues here:

First issue:
The Get Tags in a workspace API endpoint is returning Tags color names with the old names (red, blue, green…) instead of the new names provided in the documentation (dark-pink, dark-green, dark-blue…etc).

Second issue:
The create tag API endpoint is creating the tag, but without the color specified in the body of the call. Example:
I am creating a tag with color dark-blue, the call is a success, but it creates a Tag with no color.

Could someone from Asana API team help please?

[John_Baldo]

Hi, sorry about this. A couple things are likely happening.

1. Getting something other than dark-blue back from the API when you set.

This is a bug we will look into. Color names were recently changed. The old names should continue to work and be mapped on read / write. Looks like that is not happening here.

2. Not seeing the color in the web app

This is more nuanced but essentially also a bug we are working on urgently. When you set the color in the API today, you set it only for the API user. A change was made to the web app to show only a “global” color for all users and not just the logged in user. We are working on applying this same behavior to the API. After that, you should see the color along with all other users. A bit more on this.

Apologies for this. I’m making a note to follow up here once the fixes are released (expect the fix for 2 to come very soon).

[John34]

Thanks for the prompt reply, John. I look forward to a fix for this!

[Alex_Laughnan_Asana]

Hey @John34 ! I’m Alex the Tech Lead for our Design System team at Asana and I’ve been making changes that impacted the API honoring color and icon values for projects & tags. I take responsibility for the issue you’ve been experiencing and I appreciate your patience.

We’ve recently deployed changes that should fix icon and color properties on both projects & tags. I’ve tested both myself, but let me know if you’re not seeing the issue resolved on your end.

As we have two discrepancies, I wanted to talk about each one:

1. Fixed, API honoring color values: color and icon properties for PUT requests to projects & tags should now be honored.
2. Not fixed, color value discrepancies: The colors that you send in a PUT request (and get back as part of the response) are still our legacy color strings. The GET response will return the current colors that you see in the product UI. The value in the database will be the current color value (no data changes from your API intent).

We do mapping on PUT requests to translate these legacy colors to current colors, but have not yet gone through the process of making a breaking change to the API to deprecate the legacy colors. This change is in our backlog and we’re continuing to weigh its priority with other feature improvements & bug fixes. We have a mapping of the legacy colors to the new colors here: Color codes in API - #37 by John_Vu

Thanks again for your patience!