ePO query names in reports

[ninov_n]

Hello,

Yesterday I came across interesting issue and most probably it needs to be logged as a product idea but I would like to check if someone can suggest a workaround or additional information.

Creating a custom report with custom queries lists query names above the results (tables, charts and etc.) by default and you do not have an option to hide them - unlike the labels of charts where you can select/deselect checkbox in order to exclude them.

It is a painful issue for Managed Services providers because usually they use same query name convention across different sub-groups for execution and it will result in multiple duplicated items for additional customization.

The above mentioned issue was introduced with the latest 5.10 release and it was not that way in 5.9.1

[Ufoto]

I am affected by the same issue. I didn't pay much attention when I've setup the reporting initially, and now all query names are visible for the end users. I think that this is a cool feature, but there should definitely be an option to enable/disable it.

[cdinet]

Can you be more specific in what you are referring to?  When I click on new report (without actually adding anything yet) in both 5.9.1 and 5.10, I get the same options.

[ninov_n]

Hi,

The thing is that in 5.9 query names seem to be hardcoded while in 5.10 it gets the automatically and it causes issues:

5.95.10

In result if you create a brand new report in both ePOs with same settings, you get different results due to these hardcoded text fields for query names:

5.9 report5.10 report

In my opinion it should give you an option to list query names or remove them in a report. Currently in 5.10 it automatically lists them and it could reveal sensitive information.

[cdinet]

What type of problems is it causing and what type of sensitive information would a query name reveal?

[Ufoto]

@cdinet The problem (at least on our end) is that when all of our queries were created back in the day, they didn't exactly follow a naming convention and some of them have pretty random names which I would not want to be seen by the management who is actually looking at the reports. Tidying up the names is an option (although we will have to go through a lot of queries piled up over the years), however as a technical person I would rather use naming convention not understandable for the management. 

In my opinion the names of the queries should be relevant only for the technical staff, and we should not be forced to make them user-friendly if we already have an established technical naming convention. 

In regards to the sensitive information, maybe others will give a more prime example, but a thing that comes up to my mind is if you have different customers managed by a single ePO, and some of the queries contain company names revealing them for everyone who has access to a report using such query.

In conclusion, I don't see a reason why we should not have a tick box to enable/disable this functionality. 

[cdinet]

Agreed.  Please post an idea per kb60021 and include your reasoning that you gave, as it has some strong arguments for your request.