Echoing this! Would be great to have this feature
1 Like
Yes!! Please add this as a feature!!!
1 Like
I might be missing something here, but can it be as simple as adding a task to multiple projects? I want to primarily operate from the My Tasks page and tag accordingly but I think (?) that is accomplished by adding the task to multiple projects. Am I missing something here? Is the problem that you canāt sort by a specific tag across multiple projects? If so, I agree.
1 Like
How does this not have more votes ?? This is critical and I wonder why it wanāt included in the first place.
3 Likes
Agree. There should be tags to allow for things you need but donāt want to add as a custom field on every project. For us, this is billable time. I want to add a billable tag, to run a report on any task to add it to an internal project that our team and clients donāt see. I donāt want to have to buy additional tech to make this happen. For now, skipping the add to project component which limits my reporting capabilities.
Wow, I just had a strong need for this, and realized this isnāt even an option? Thatās nuts.
1 Like
You are be able to move to a section w/o tags. We have a āStageā custom field that we use to move (or set when moved another way) to a section. Not sure if that is more complex than tags or not, just thought Iād let you know.
I can tell you why itās probably not done yet. If you look at how Asana Help refers to tags as quick and ad hoc, they clearly view tags as messy and less structured. Right now I am using a text string in a rule to add a comment (ābug_fixā) to make my own tag work-around. Donāt think thatās very structured!
1 Like
^^^ THIS ^^^
2 Likes
Again, today, I went to create a rule that checks to see if a task has a certain tag or not, and realized I still canāt do that. 
1 Like
I would really like to not have to employ a āCustom Fieldā workaround for something like this that should really have been implemented in rules by default.
The problem with Custom Fields is now they have to be added to every project that needs it. They are also harder to search, as you simply canāt just double-click on a custom field to get all matching selections like you can do with tags.
Thanks!
Bump, this seems simple and can avoid me having to continue to pay to utilize third party options. Please hear us ASANA Dev Team.
1 Like
Here to ask for the same rule.
Iād like to add tags so we can track which team is doing or has done work within a specific task.
Itās easiest with tags that way we can each track our progress.
Must-have feature IMO!
Surprised that this is not in the product yet.
+1 on needing this. I want to use the same rule on multiple projects and donāt want to pollute them with a new custom field just for my purpose
Would also find it beneficial to have rules based on tags. +1 for request
We definitely need Tags to be able to trigger rules!!
We have one tag in particular that would allow an automation that would automate the moving or completion of hundreds of tasks. As things stand, when we apply that tag, someone has to manually recognize the tag and move the item (or mark it complete).
How in the world is the most basic functionality of ātagsā not included as a Rule option? I canāt even create a rule that adds a tagā¦
Tags are an old 
Asana feature that has not aged well in the view of a lot of folks at Asana (I know some of them wish they had never created the tag feature in the first place 
).
The following is a completely unofficial statement, purely my own view, but based on what I know, I think you can assume youāre not going to see any further development involving tags.
(Of course we support them in Flowsana rules. 
)
Unless they support it, thereās no other āgreatā way to reliably trigger a Zap via an Asana Rule, without causing a more āsignificantā action to a task (such as a task completion).
Tagging seems like a very basic and simple method that could have been used in an Asana rule to trigger a Zap. Ideally a POST webhook feature would be implemented as an Asana rule action, but until something is reliably implemented there (been using iDOās for a while, but unfortunately isnāt reliable enough ā possibly due to Cloudfront API errors after infrastructure change), I was hoping to just make use of tagging (since Zapier has the ability to trigger when a specific tag is added).
So, once again, weāll have to rely on 3rd party app integration for a relatively basic āRuleā action of for āDo thisā of āadd tag to taskā.