Permission to assign cases

yes - same for setting status. my requirement is for a simple submission form that end users can use to submit support cases. end users don;t get to assign cases and always have status=open

Well, not a dropdown list for users but rather an autocomplete box just like the 'authored by' on node form ... this seems easy and valuable. hope you guys have it inthe plan soon. great work.

Sure .. this would be good to have,

I'd be happy to have several options for defining -

1. Default project or "container" where "semi public" cases will fall in. "Semi public" - is when user can see only his own cases or any case assigned to him and "container" is a default project for all public cases, this gives an opportunity to collect and handle site wide help tickets for any member who has rights to create cases.
2. Assign cases - public users can't assign cases except for themself or to the project owner.

this is it,
T.

With regards to end-users submitting cases: we implemented an XML-RPC based system for letting end-users post from a form on another site, and we allow for setting the authorized "submitting" external site, and the default project to dump new cases into. New cases have an Open status. That works for external sites, but I agree we should also address the simpler internal scenario:

Let certain users have something like a "create cases (limited)" permission, which doesn't let them change the Status.
Let Administrator choose the default Project to dump new cases into, or "Any project" to let the user choose the Project themselves.

With regards to assign permissions, an "assign cases" permission -- without that permission, the assign to autocomplete can only show your own name (and case owner, too, if changing the field in a comment?).

Moshe, does OG automatically limit the users that show in the Assigned To field to only members of the group?

Others, please give me a sanity check on the above, make suggestions, so we can move on this...

@Dave .. +1

Goooooooooood,
.. this is what we all really need, very well, if there is something you need to assist on, please don't hesitate to ask

Greetz,
T.

Submitting patches is welcome. :)

My company is sponsoring the (costly) development right now to keep this moving, but in the spirit of open source the intent is to get all the contributions we can.

A few thoughts ...

XMLRPC isn't really needed if you just want folks to post from an outside form. The regular http pages that we write are fine for that. Even credentials can be passed as regular form posts.

I think 'maintain status' is clearer than 'create cases limited'. If you don't have that permisson, you don't see the field, and upon submission the field will default to whatever status new cases default to. Same for 'assigned to'. You only see it if you have permission. A default assignee should be configured for each project. The project.module model where you assign cases to self if not that generally useful IMO.

We should discuss if we really want to limit assignees to og group subscribers. That is probably a good idea, but I'm not positive.

Now two permissions are are defined in casetracker:-
1) assign_case
2) set_status
Now if a user is given the access to assign_case and set_status then only he can assign case or set status of case while creating a case / editing a case / posting comment on a case. If a user is not given these permissions then he cannot change these case fields as these case fields are readonly for them.

Fixed and committed to CVS.

Fixed and committed to CVS.

Hi,
Did either of these killer permissions make it into 6.x? i have it installed on my deployment and it users creating cases can still pick the status of the case. Am I missing something? Please help!!

Cheers,
Kolossus