When the user is on the main ticket page he can see all the units and groups, even if he don't has permission to access some of them, infact he correctly get access denied in this case.
This is not very good if I would separate my customers giving a personal group each because this way they can see how many customers I have etc..

Maybe a switch with "Hide groups with no permissions" will solve the problem.

Thanks

CommentFileSizeAuthor
#5 ticket-ss.png31.26 KBerrno

Comments

roczei’s picture

roczei commented
Assigned: Unassigned » roczei

Here you can modify the ticketing permissions: ?q=admin/ticket/access

All groups may be related to one or more scopes, which can be setup by the specific permission stucture. The scope can be refer to all units and groups or only one unit and group.

Example on the ticketing demo site:

https://gug.grid.niif.hu/ticketing/index.php?q=admin/ticket/access/edit/5

Username: testuser1 password: testuser1

subcomandante’s picture

subcomandante commented

Yes, I know how set user permissions to ticket groups, but users can see all groups even if they do not have access. I'm going to explain better:
I want to create a group for each customer of mine but I don't want customers view all customers list...

Example
Now the ticketing system work as follow:
Group1 (customer 1 can access this group; customer2 can't access this group but can see it)
Group2 (customer 1 can't access this group but he can see it, customer 2 can access this group)

What I'd like to see:

Group1 (costomer1 can see and can access this group, customer2 don't see this group -> hide it)
Group2 (costomer2 can see and can access this group, customer1 don't see this group -> hide it)

So if I login as customer1 I can see only:
Group1

if I login as customer2 I can see only:
Group2

and so on..

Tnx

roczei’s picture

roczei commented

Here is the good process for this:

Ticket hierarchy:

Unit1
+-- Group1
+-- Group2

Please create a new role and edit it (?q=admin/ticket/access/add):

Role1 = tk_role1:
Add scope:
Scope: Unit1 / Group1

Access:
[x] ticket reader
[x] ticket manager

Please add the user1 to role1

Create role2:

Role2 = tk_role2
Add scope:
Scope: Unit1 / Group2

Access:
[x] ticket reader
[x] ticket manager

Please add the user2 to role2

nexco’s picture

nexco commented

Tried your step by step process, but it did not work for me. Either.

The issue is that when I get to the setting of scope in the new role - the drop down only shows the "All" choice. There is no other choice for Unit or Group even though the Units and Groups have been set up as per your directions. I've tried a lot of things but can't seem to wake up the drop down to show anything but "All"

This could be the central issue then that everyone is talking about.

How can we wake up the drop down so it shows us the choices of scope to choose from?

Thanks

errno’s picture

errno commented
StatusFileSize
new ticket-ss.png31.26 KB

Hi,

I had try your step-by-step recommendations with some luck. In the sidebar menu non-permitted group disappears, but when I click on unit in content area both groups are shown. I will have a look to source code, but your suggestion must better.

screenshot attached

nexco’s picture

nexco commented

I discovered the issue that was causing me not to see all the Units and Groups in the popup.

First, I needed to setup a user with all permissions to see all and do all, including ticket admin. Then - with the admin level permissions I was presented with all the options in the pop up.

I would add that step to your English install instructions to prevent any confusion.

roczei’s picture

roczei commented
Version: 6.x-3.0-rc1 » 6.x-3.0-rc2
Component: Code » Documentation
Assigned: roczei » mr.york

We added this missing "including ticket admin" documentation. Please check the rc2 release's README.txt and reply that it is good for you.

errno’s picture

errno commented

In my opinion, it's clear now. Thanks.

mr.york’s picture

mr.york commented
Status: Active » Closed (fixed)

Thanks!