Because we have so many teams using Asana at the same time, our field names get a bit messy. Example:
Status [MKTG]
Status [OKR]
Status [oCISO]
Status [MOPs]
But when we are creating public views for other teams to reference, we don’t need to be that specific. Or if we are creating projects for View Only licenses for our larger team, we just want to show Status. Would love to have a “friendly” name for fields that can be shown in published links.
As mentioned below, having additional information on the field level:
System Name for unique id naming purposes
Display Name effectively an alias e.g., the same way the AS keyword works in SQL and such.
Ideally where users can set alias values independently by view, etc. e.g., I may want the alias to vary between views to match the context of the people who use those views in the portfolio/project.
@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.
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.
I can get behind this. I’ve wanted it also. In an ideal world users could set:
System Name for unique id naming purposes
Display Name effectively an alias e.g., the same way the AS keyword works in SQL and such.
Ideally where users can set alias values independently by view, etc. e.g., I may want the alias to vary between views to match the context of the people who use those views in the portfolio/project.
