Yeah, we totally need this. It seems like a rather arbitrary omission for filtering. I have a landscaping company and they want to flag a deal if it's missing line items but only after gets to a certain point in the pipeline. Any time before that the tag is just cluttering up the pipeline.
I was shocked when I realized I couldn't use deal stage as filter for tags. Why wouldn't this be an option? It should be obvious that some tags will only be relevant on certain stages. And we might want to have a tag use slightly different logic for one stage vs another.
+1. As a previous user said: "It should be obvious that some tags will only be relevant on certain stages. And we might want to have a tag use slightly different logic for one stage vs another."
- Custom property set by workflow to filter on - Use a list as a filter criteria - Printscreen and print your pipeline every day, put them on a whiteboard, and draw a colorful tags
Voting for this feature to be prioritized! We want our tags to appear on any active deals and NOT on closed lost deals. A simple and logical application - please help!
You have got to be kidding me! This is such a, what I call, HubSpotism. If tags we're to be used, Deal Stage is the most obvious property to reference as a filter. UNREALLLLL. GET WORKING ON THIS PLEASE
The most important filter criteria of the specific deal stage are missing. Please, change it, otherwise, the whole feature tag deals is only 10% of possible use.
I was just looking at this for a client. My workaround is to use the date entered/left properties to try and slim it down to the pipeline stage you required. This will work if your pipeline stages typically aren't skipped.
For everyone who is currently trying to accomplish this: If you have predictable pipelines, you can use a combination of the "date entered", "date exited", ... properties to accomplish the same behaviour.
Eg. if a deal is in stage 2/5, it should have a "date exited" stage 1, a "date entered" stage 2, but not a "date entered" stage 3. This should allow you to create the behaviour you want, but takes a lot more work than just seleting a deal stage.
- Look for the "Date entered" properties related to the stage dates you want to filter. For example: If you want to target deals in the "Pitch Stage", then set "Date Entered Pitch Stage" to known. Then, set the property to "unknown" for the next stage. For example: after the "Pitch Stage", comes "Evaluation Stage". So set "Date Entered Evaluation Stage" to unknown. That way the tag will be applied to the deals that are in Pitch Stage and no further.
It requires a little work, but you should be able to get the same results as by filtering by Deal Stage.
Filtering on deal stages seems like the most basic function for deal tags - so why is it still not available? I'm just now beginning to use deal tags and have a few use cases to use them for specific deal stages, but now I'm fumbling around with list filters and hours of testing, which is completely insane.
