Bumped version to 7.0.6 for a quick test and same issue. 

I'm curious why the priority is so low? It's a serious regression.

I have several support teams, every team is responsible for own application. The applications have own template and tags based on guidelines https://www.zabbix.com/documentation/guidelines/en/thosts/configuration/templates#tags

Now the process is totally broken. The team's dashboards do not show problems. The teams do not get notifications about their applications.

"Applications" was replaced by Tags in 5.4. Now there is no other way to filter something by template.

abyss , my workaround was to go into each trigger prototype and add tags to the trigger . To my surprise it did not crash with the ones you can see inherited from the template. Got to remember to remove them before applying a patch. 

Using the mass update was fine in my case, but maybe you have a bigger use case and using api is more practical. 

gdzias agree. it is workaround, but also I need to add tags to all Trigger prototypes in all Discovery rules in every template. It's possible, but some amount extra work now and after patch.

Also I'm not sure how it influences on the database size and speed of generating problems.

Also found that it is not possible to filter Items by inherited tags. 

If you go to Hosts -> select one host items -> reset query -> and search for tags (that you know hosts inherit) , no result is displayed for items that have inherited tags one is trying to search for. 

Most likely it is all related to the same root cause, at least I hope so. 

Fixed in development branches:

• feature/ZBX-25717-7.0
• feature/ZBX-25717-7.2

gdzias, currently, there is no option to filter by inherited tags. However, we are working on this functionality, and it is likely to be included in the next major release.

It seems that this is still broken if tags should be inherited from host prototype template.

Editing trigger show inherited tags, but tags are not added to problems and are not visible via API.

Any update about this? When we might expect to fix this bug? Our customers which relay on trigger prototypes tags cannot get notifications, because problems don't have proper tags in action condition.

We’ve encountered the same bug, and it’s quite frustrating (even blocking) since our permissions and actions depend on these tags.

This issue is ongoing the testing stage. It will be released ASAP. Stay tuned!

Available in:

• 7.0.11rc1 075bbf45116
• 7.2.5rc1 a00fba4b5e5
• 7.4.0beta1 (master) d5839c2dc57

Hello
I've updated to 7.0.11
I'm still having problems with exposing template tags to problems.

They are not exposed from Triggers prototypes, but exposed from template triggers

I see now that they are inherited

But not exposed to problems

Also I do not understand from where comes `component: mssql-job` It is not seen in Trigger inherited tags.

But I'm pretty sure that it is related to update from 6.4 to 7.0

We are still experiencing the same issue even after upgrading to version 7.2.5.

erik.deneve, Could you please provide more details about the issue?
Are you experiencing it during problem generation, or is it related to how inherited tags are displayed in the trigger configuration form?

Hi Alexander,

I’ve included all the details in a commercial support ticket. Starting from version 7.2.5, the tags displayed in the trigger configuration form are correct. However, the event generation is still not applying these tags to the events. It's odd because it works as expected for some LLD triggers, but not for others (At the moment, we can't determine when it works and when it doesn't). I suspect indeed this issue was introduced during the upgrade from version 6.4 to 7.2.

For more information, including SQL queries and screenshots, please refer to PR-8187.

Best regards,
Erik

abyss, you're describing an issue that occurs during event (problem) generation on the backend side. This ticket is specifically about the display of inherited tags in the trigger prototype form.

To avoid mixing different issues, please create a separate ticket for this.
If that’s inconvenient for you, just let me know — I’ll create the ticket based on your comment.

At the moment, I'm trying to reproduce this issue, but so far without success.

Does it occur consistently for all triggers created via discovery rules, or only for some of them?

I've created a new issue ZBX-26259

abyss, Thank you!

Let’s continue the discussion about problem generation with missing tags in the new issue ZBX-26259.