Is it possible to see all tags added within an Organization? We want to try to control the vocabulary some by seeding the tag roster.
Some answers here: https://www.quora.com/How-can-I-display-all-of-my-tags-in-Asana
Yes, using the API is your best bet for viewing a full list of tags. You may be interested in posting in the Developer category here in the Community for more details.
The Quora answer will work for those who have fewer than 100 tags (I think - or thereabout) and aren’t comfortable working with the API. If you too many tags, you’ll get an error.
At that point, your best bet is the API, but if you’re not sure how to work with the API directly, you can also get this list via our API Explorer.
Here’s a quick walk through:
First, go to https://asana.com/developers/api-reference/tags and click the Explorer tab, right beneath “Tags.”
Next, you’ll need to authorize your Asana account by clicking the purple button at the top of the page (“Click to authorize API explorer”).
From the drop-down menu, select GET /workspaces/:workspace/tags.
Select your Organization or Workspace from the drop-down menu found beneath “Attribute Parameters.”
Increase the limit beneath Paginate parameters to 100. Note that the limit can’t be set to be greater than 100.
If your Organization or Workspace has more than 100 tags, you’ll need to use the “offset” parameter to get your next page of tags. This offset parameter is found at the bottom of each list of tags that’s returned.
You can get each subsequent page by copy/pasting the latest offset parameter into the OFFSET field.
Repeat as needed, until you have all of your tags.
I like to pre-populate the tags list by adding a list of preferred tags to one task created solely for this purpose. This helps me remember my own preferred tags by seeding the list, as you said, and provides a convenient directory that I can use to filter by those tags (just open the task, and click on the desired tag).
Obviously, this provides no control over tags added organically by other users, but it does produce suggestions. You could do this without explanation and let the power of suggestion go to work, or you could, say, assign a special color to let users know these are preferred tags.
Creating a task as a tag directory is also useful for creating distinct taxonomies within yet separate from organically-created tags. For instance, by using
-tagname I can create one or more collections of ‘special’ tags that can co-exist with plain organic tasks (
Example: If I wanted to use tags for assigning the classic Getting Things Done contexts, I might create a task named GTD contexts then tag it with
@waiting and so on. Now, when I tag any another task, I can type @ to see a list of all my GTD specialty tags. Alternatively, I can start typing home, work, or waiting to find the specialty tags as well as any others that include those words.