Skip to main content
Question

Filtering on Opportunity Tag List in WT Module Broken?

  • February 27, 2026
  • 3 replies
  • 40 views

Forum|alt.badge.img+12

Hey all,

 

I have a ticket list I want to create using an opportunity tag. The tag in question is “2026 Landscaping Contract” which is applied to all of our full service contracts. When I filter for that tag in opportunities, I receive many results. When I filter for that tag in work tickets with no other filters, I receive only a fraction of the tickets I should receive. When I change the filter to “2025 Landscaping Contract”, I receive the rest of the tickets I should receive, and furthermore, drilling into individual opportunities, they do not have the 2025 tag applied, but 2026. 

 

2026 Landscaping Contract Filters + Results
2025 Landscaping Contract Filters + Results
Screenshot of Opportunity shown in 2025 results showing lack of 2025 tag

 

Am I missing something or is this a bug?

3 replies

David_Spiritus
Forum|alt.badge.img+15
  • Participating Frequently
  • February 27, 2026

If there are more than 2500 results click the icon in the upper right that looks like a stack of batteries.....


Forum|alt.badge.img+12
  • Author
  • Inspiring
  • February 27, 2026

That is not what is happening here. Filtering on 2026 Landscaping contract yields ~300 tickets. Filtering on 2025 Landscaping contract yields  > 2,500, yes, and you have to click the pancakes to see them all, but that doesn’t change the fact that opportunities that do not have the tag I’m filtering on showing up in the list, and not showing up when I am filtering on what I am looking for.

In my example, Opportunity 17164 does not have the 2025 landscaping contract tag, yet it shows up in the filtered list for 2025 landscaping contract, and does not show up in the first image, filtering on 2026 contracts, even though it has that tag.


Caren Bueno
Forum|alt.badge.img+8
  • Inspiring
  • March 12, 2026

I may be completely off here, but I would dare to guess that the 2025 tag might have come from the opportunity template level and carried over when the opportunities were created for the following season.

We ran into something similar once where a previous season tag stayed attached in the background because of the template setup.

The good part is that if you can pull the list of those opportunities at the opportunity level, you should be able to bulk add the correct 2026 tag and bulk remove the 2025 tag. Once the opportunity tags are corrected, the work tickets should reflect that properly as well.

Not sure if that is what is happening in your case, but it might be worth checking the template or the original opportunity tags.

Curious to hear if that ends up being the cause.