So far, I have only created one "client" group, where users A, B and C are members. If user D wants to create a new ticket, she has to select the client from the drop down menu. Since she is not member of any client groups, she cannot choose any.

But she can still save the new ticket, without selecting any client from this required field. A new node will in fact be created, but read access is immediately denied to her.

Shouldn't only users be able to create a new ticket if they actually belong to at least one client? I think if they don't, they should not even see the "create content -> ticket" page.

Comments

luco’s picture

luco commented

um. I'd like a rather different feature: anonymous users could create tickets, provided they entered their e-mail address.

the difference, of course, would be that they'd only solve their problem via e-mail.

is that too far-fetched? ;) ther than that, this module is great. thank you very much.

luco’s picture

luco commented

I figured something out.

that happens because of permissions.

if you create, say, a Tech Support group then you must provide authenticated users access to that group.

the downside to this is that auth users are granted access to all of Tech Support's tickets - not only their own. that pretty much defeats any privacy they might benefit from.

there should be two permissions then:
1) access tickets from a certain group
eg.: see if anyone's been having the same problem as you have and what was the recommendation from the experts in any given field.

2) assign tickets to a certain group
e.g.: ability to handle tickets over to Sales, Tech Support etc. this permission by default enables an user to see only his own tickets, assigned to any teams they're allowed to.

hope this helps to clear the mess and propose an upgrade to this already great module.

cheers,
Luciano

jeremy’s picture

jeremy commented
Assigned: Unassigned » jeremy

Assigning to myself to review before the next release.

jeremy’s picture

jeremy commented
Status: Active » Fixed

An improper check was being done -- the code now properly validates that a client has been assigned to a ticket when created. Fix committed.

roball’s picture

roball commented

Thank you Jeremy - just tried out your latest dev version and in fact users without the permission to access any client can no more create a ticket. Bug fixed - fine!

I only gave one special role the permissions to access clients and create tickets. However, the link to node/add/jobtrack-ticket is still visible in the navigation menu for all authenticated users and not just for the users with access/create clients/tickets permission. When such an unprivileged user clicks on the link, she gets an "Access denied" error - which is fine - but the perfect way would be to not even show the "forbidden" menu entry at all. How can this be achieved?

Thanks!

Status: Fixed » Closed (fixed)

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

grishker’s picture

grishker commented

My situation is more complex and current version is almost perfect for me. but:
I have many clients. Say 100+. I want to have user could be assigned to 1+ client or NOT assigned.
When such user create new ticket I want:
- if no client assigned - leave client field empty for this ticket
- if 1 client - set this value into ticket with no selection field
- if 2+ clients - show dropdown selection field and allow user to choose.
And... Users should see only tickets of clients they are assigned only.
How make this happen?

Thanks!
Roman

jeremy’s picture

jeremy commented

Use the support module, which replaced jobtrack:
http://drupal.org/project/support

If you run into any issues, please report issues against that project. Jobtrack is not supported/maintained anymore, but there is a clean migration available to the support module.

roball’s picture

roball commented
Project: Jobtrack » Support Ticketing System