When I enable "access client tickets" under User Permissions, it appears that it is duplicating the "administer jobtrack" permission. "Administer jobtrack" is disabled for all roles on my site.

Enabling "access client tickets", gives the same menu on the user's page, that I see when "administer jobtrack" is enabled - Job Tickets - with two underlying menus, "Clients" and "My tickets".

The "Clients" menu presents all of the tickets on the site for every user submission with full editing capability.

The only permissions that I have enabled are "access client tickets" and "create tickets"

Enabling both "access client tickets" and "administer jobtrack" only produces one instance of the Job Tickets menu with the two underlying menus.

If I am misinterpreting the use of "access client tickets", please correct me, but it is the only way that I have found that the users can access their submitted tickets.

Comments

jeremy’s picture

jeremy commented
Version: 6.x-1.0-beta1 » 6.x-1.x-dev
Status: Active » Postponed (maintainer needs more info)

Can you retest with 6.x-1.x-dev? I am unable to duplicate this in my local sandbox so if there was a bug in the beta release it should now be fixed.

jeremy’s picture

jeremy commented

Is this perhaps a duplicate bug report? Please read more about how Drupal permissions works...

leevester’s picture

leevester commented

I have tested with both 6.x-1.x-dev and 6.x-1.0-beta1 and have gotten the same results. Enabling "access tickets" allows the same access to "administer jobtrack".

jeremy’s picture

jeremy commented

Depending on when you downloaded the -dev tarball, you may have downloaded very old cold. It seem I (once again) checked code into the wrong branch. Please try the -beta2 tarball.

I am unable to duplicate, and suspect a misconfiguration based on the other issue you filed. Can you explain how your roles are set up, and how jobtrack permissions are assign to each role?

leevester’s picture

leevester commented

I rechecked how Drupal Permissions is structured and I was misinterpreting how that structure should work. I now understand that the permissions given to the authenticated user are automatically granted to all other created roles. My mistake.

jeremy’s picture

jeremy commented
Status: Postponed (maintainer needs more info) » Fixed

I'm glad to hear you have it working. Marking issue as fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.