Because we have so many teams using Asana at the same time, our field names get a bit messy. Example:
But when we are publishing views for other teams to reference, we don’t need to be that specific. We just want to show Status. Would love to have a “friendly” name for fields that can be shown in published links.
Hi @Rachel_Hazen ,
Public links do not show any fields at all, so I’m confused about what you are requesting exactly so that others can vote for?
@Rachel_Hazen is suggesting another optional field is available for every custom field definition in which you can specify the visible field name (wherever that field appears, like in a List view column header) so that it could just appear as “Status” even though the precise, unique, actual, internal custom field name might be “Status [MKTG].”
I had voted for this, think it’s a good idea, and happened to note a while ago that it’s available in an Asana competitor’s product.
Thanks,
Larry
Oh ok, interesting idea, voted!
However, I still don’t understand how it is related to public links that don’t support custom fields 
Not sure!
I’m not sure where I mentioned the connection between public links and custom fields within the context of this feedback. I simply want a “friendly” name that shows up on shared/published views. Exactly as @lpb noted.
Hi @Rachel_Hazen. In your screenshot, you have highlighted ‘Create a public link’ within the Export and Sync menu, so I understood by ‘published links’ you meant these public links.
Your other screenshot is of your status custom field.
So you are requesting that in Asana, the headers of custom fields will appear as they are, but in public links they would appear with a friendly name, right?
My point is that custom fields don’t appear in public links. 
