Ubuntu

Hello Christian,

I cannot reproduce that. I've created user group with permissions to two hostgroups one read second write, and tags as you mentioned without any value.
And I can see all problems with and without tags.
Maybe you have some filter enabled in the problem page or dashboard?

And user see all problems fine

I can confirm it works fine if you have "all tags" tag filter permissions for both groups. In my case, I was testing with tag filter permissions with a defined tag name (or tag name AND tag value) for one of the groups, and "all tags" for the other group. In such case, the user will only see those problems either matching the defined tag filter that haves at least a tag name defined or, for the other group, those that have ANY tag defined, but not those without tags.

Check the following screenshots:

01: Here you see all problems currently existing, viewed as Super Admin. Spread over two host groups, two of the three problems have tags defined, one not.

02: Permissions for the group where one user is in, read write permissions for both groups:

03: tag filters for this user group: "all tags" for one group, "defined tag name" for the other group:

04: problems seen by the user being part of that group: missing the problem which has no tag defined:

05: changing the tag filters to be as in your example, both set to "all tags" (which in fact is useless, because it is the same as actually not defining any tag filters at all):

06: now the user sees all three problems

The use case we want to achieve is:

1. see ALL problems for a certain list of groups (those you are responsible for)
2. see SPECIFIC problems, filtered by tags, for some other groups (where you are only responsible for specific parts of functionality)

+++++

Does the above explanation help you to reproduce the bug?

could someone please look into this? This issue is still in "needs info" even though I have supplied exact info on 6th of October!

This happens due to an incorrect condition in the SQL query when there is a combination of a tag filter with specified tags and without them.

In this case, a JOIN is performed with the "problem_tag" table, which contains no records for events without tags.

Replacing the condition with a LEFT JOIN should resolve the issue.

  SELECT DISTINCT p.eventid,p.objectid,p.clock,p.ns,p.name,p.severity,p.cause_eventid
- FROM problem p,functions f,items i,host_hgset hh,permission pp,hosts_groups hg,problem_tag pt
+ FROM problem p LEFT JOIN problem_tag pt WHERE p.eventid=pt.eventid,functions f,items i,host_hgset hh,permission pp,hosts_groups hg
  WHERE p.source=0
      AND p.object=0
      AND p.objectid=f.triggerid
      AND f.itemid=i.itemid
      AND i.hostid=hh.hostid
      AND hh.hgsetid=pp.hgsetid
      AND pp.ugsetid=2
      AND NOT EXISTS (
          SELECT NULL
          FROM functions f1
              JOIN items i1 ON f1.itemid=i1.itemid
              JOIN host_hgset hh1 ON i1.hostid=hh1.hostid
              LEFT JOIN permission pp1 ON hh1.hgsetid=pp1.hgsetid AND pp1.ugsetid=pp.ugsetid
          WHERE p.objectid=f1.triggerid
              AND pp1.permission IS NULL
      )
      AND i.hostid=hg.hostid
-     AND p.eventid=pt.eventid
      AND ((hg.groupid='2' AND pt.tag='component' AND pt.value='system') OR hg.groupid=4)
      AND NOT EXISTS (
          SELECT NULL FROM event_suppress es WHERE es.eventid=p.eventid
      )
      AND p.cause_eventid IS  NULL
      AND (p.r_eventid IS NULL OR p.r_clock>1739257010)
      ORDER BY p.eventid DESC LIMIT 1001

This issue has been forwarded to the development team.