I have discovered that I need a Project for each customer that we have, along with a corresponding group. This seems that it will work fine, but, my issue is this - I do not want our registered community users to have a drop down of all our customers(Projects) when submitting a new case via the web page. Is there a way to limit the visible projects when submitting a new case and still keep the functionality of my Community Case List pluging (which requires that projects have public submission enabled)?
|
3
|
|
|||
|
|
|
2
|
I'm the author of the Community Case List plugin. Glad to hear that you find it useful! The plugin does not implement any case input facility. Therefore, it cannot really change the way the public submission works; javascript code to restrict the projects in the project drop-down seems to be quite a hack, but I could maybe try that. What I could do otherwise is to add a per-project override for the project visibility (so that you could force it to be visible in the list even without public submission). Would that solve your problem? In that case, your customers could however only use mails to submit cases, and not the public submission web page, so I guess that this does not really solve your issue. Maybe FogCreek should enhance the public submission to "Enabled for everyone", "Enabled for community users only", and "Disabled"; you could edit your question to make it a feature request. |
|||
|
|
0
|
I think I am going to try to clear out the drop down under Project and fill it with only the Project that they are a member of. Is there a global variable or array of groups that they belong? |
|||
|
