Kelvin Posted July 3, 2018 Share Posted July 3, 2018 We have made some big changes with the structure of teams within Hornbill but in the process users have now lost the ability to search for calls outside of their immediate teams. Teams now only have their respective staff assigned to them instead of assigning all users and using Home > Hornbill Service Manager > Configuration > Service Desk to limit who can have calls assigned to them. None of our services have any supporting teams and this in the past has given us access for all full users to be able to create views of any calls in any teams. Is this possible, have I missed something, how do others get around this Link to comment Share on other sites More sharing options...
Steven Boardman Posted July 3, 2018 Share Posted July 3, 2018 @Kelvin by having no '''supporting teams''' defined against your services, this should actually mean that all teams support the service and as such you should be able to search for requests raised against those services. Could you clarify if it is one or multiple places you are not able to find requests? * Global Search * Advanced Search on the request list Steve Link to comment Share on other sites More sharing options...
Kelvin Posted July 3, 2018 Author Share Posted July 3, 2018 @Steven Boardman It looks like the issue is when you try an advanced search on the request list. Global Searches seem to work Link to comment Share on other sites More sharing options...
Steven Boardman Posted July 3, 2018 Share Posted July 3, 2018 @Kelvin hmmmm i can't seem to replicate on my instance - i have services which are set as Supported by All Teams and the advanced search seems to work as expected to me, strange. Could i ask you to raise this as as support request and we can take a look at this for you Steve Link to comment Share on other sites More sharing options...
Kelvin Posted July 3, 2018 Author Share Posted July 3, 2018 @Steven Boardmanok thank you Link to comment Share on other sites More sharing options...
Victor Posted July 4, 2018 Share Posted July 4, 2018 @Kelvin - I have asked some clarification in this area form our dev team but as far as I understand, when using advances search teh results are limited to requests assigned to teams that the user is a member of... so if the user is part of Team A but not Team B, when using advanced search which do not explicitly have a team or service criterion, then the results will only include requests assigned to Team A. May I ask you to try something... when using advanced search, besides the criteria you (usually or need to) use, can you add one more criterion, something like "Service IS NOT <service>"... For <service> use a service that you don't usually have any requests for, like a test service... do this and let me know if how it looks with the results returned... Link to comment Share on other sites More sharing options...
Lyonel Posted July 4, 2018 Share Posted July 4, 2018 If my understanding of @Kelvin's setup is correct, we are in a similar situation: we never use "Supporting teams" on our services, and therefore everybody can see everything by default. When using the search feature in the request list (advanced search and custom views) however, some sort of "security" applies (like @Victor) mentioned. Indeed, if the filter "team" is not specified in the query then only requests assigned to the teams I belong to will be displayed. The workaround is to add a filter on "team" and add ALL teams. Then you will see everything as per your filters. So practical example: Custom view / search filters are set to: I do not belong to any of the teams who have requests under these services => Returns 0 requests. If I had ALL the teams setup in the system: then I get the records back. Hope this helps? Link to comment Share on other sites More sharing options...
Victor Posted July 4, 2018 Share Posted July 4, 2018 @Lyonel - thanks for this ... an alternative to having this huge criteria would be to use IS NOT instead of IS... Link to comment Share on other sites More sharing options...
Lyonel Posted July 4, 2018 Share Posted July 4, 2018 22 minutes ago, Victor said: an alternative to having this huge criteria would be to use IS NOT instead of IS... That is true It depends on your setup and how you use team assignments I guess. In my case, I cannot use the IS NOT as a request can technically be assigned to any team (and I don't trust humans) 2 Link to comment Share on other sites More sharing options...
Kelvin Posted July 4, 2018 Author Share Posted July 4, 2018 @VictorSo I have used my test account "Kelvin" which belongs to the "TestEnvironment" organisation. I have carried out an advanced search and added a "service" "is not" "User Security" and it only displays 4 requests, I would expect to see 70k+ I know you looked at this before and resolved it by removing a service that still had deleted teams assigned to them. Although we have made some changes to the members of teams I have not added or removed any teams. Link to comment Share on other sites More sharing options...
Kelvin Posted July 6, 2018 Author Share Posted July 6, 2018 @VictorThanks for the email response. 1 question would be if I have to specify a team why does "team" "=" "list of all teams" work but "team" "!=" "1 team" not return any requests. Link to comment Share on other sites More sharing options...
Lyonel Posted July 6, 2018 Share Posted July 6, 2018 44 minutes ago, Kelvin said: 1 question would be if I have to specify a team why does "team" "=" "list of all teams" work but "team" "!=" "1 team" not return any requests. @dwalby because of your setup (probably very similar to mine), securities still apply. Unless you list all the teams, the system will automatically filter on the teams you belong to, then apply the "team != XYZ" to your sub set (or the other way around). But if you specify all teams, then you effectively override the securities. That's my understanding of the system anyway. @Victor can probably confirm. After all, I am just a host 1 Link to comment Share on other sites More sharing options...
davidrb84 Posted July 25, 2018 Share Posted July 25, 2018 I appreciate this is a little old now, but was this ever concluded? When creating views for all changes, or all Problem/KE records we're stuck having to enumerate all teams, this is somewhat onerous as we have 30 teams. Seems like even just having a wildcard option or "All Teams" option would probably suffice as a workaround. The idea that you're completing what amounts to a search query, but the result set is limited based on an invisible criteria seems a little off to me. If people wanted their search results to be limited to their teams it would be easy to add them, much harder to add ALL teams when you don't. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now