Seperating Customers in one project

[Dan Hartnack]

We would like to set up a Production Support project in JIRA where all our customer can file their issues. We would like to set it up so that each customer cannot see other customers issues. Is this possible with security settings. I have been trying to mess around with some test users to see if this is can be done and so far I can only get it to work if i create custom fields that need to be specifically filled out, but at the same time I do not want these fields to be a required field and the fields leave open the possibility for the customer to create an issue for a different customer. We would like it so we do not have to set up separate projects for each customer. Please advise.

[Adam Saint-Prix · Accepted solution]

I think this question has come up before and there are a few different ways to solve this problem. I think the best example of how this can work is the Atlassian Support site. They have umpteen thousand users that all submit tickets to JIRA, Confluence, etc. projects for support.

I'm not exactly sure how they do it, but you'll notice if you create a ticket, you only see tickets that you have filed. I think one way to do this is to say for the Browse Issues permission (ability to see project and its issues) you only allow the Issue Reporter and any Cc'd users, plus internal employees to see issues.

This means that everyone else is cutoff and other customers can't see each others tickets, which is I think what you said you want. It may take some trial an error, but I'd play with that to see if you can get what you're after.

There's some documentation on the various project specific security configurations by role and group, but I don't think that's what you're after. Try just limiting issues to Reporters, Cc users (if you have this installed) and internal employees to start.

• http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions

[Nic Brough -Adaptavist-]

Not off-the-shelf, but there's a simple setting that enables exactly this facility (Atlassian use it in their support project). See http://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission - it's only disabled because it's possible to break Jira if it's misconfigured, so they disable it to encourage people to check before doing it!