Segregating issues for a separate part of the business

Moshe Japha

We have an existing installation of Jira that is used for traditional development-style bug and issue tracking. It uses many of the default structures (issue types, permission schemes, etc).

We have a part of the business that wants to track requests for action from external customer organizations. We plan to customize the issue types, fields, screen, permission schemes, etc to meet the needs of this business. We also need to ensure that each customer organization only has access to their issues and attachments.

How can we configure the admin features such that we have complete segregation from the existing set up, while implmenting the customizations we need? How do we keep the Development-related issue types and projects, which are in the default schemes, from being presented to the customers?

Further, we had planned to assign individual projects to each Customer. (Often a customer has multiple programs. Each would need its own project). Is this the best way to ensure segregration of each customer's issues & attachments?

Thanks

MJ

Nic Brough -Adaptavist-

You can't separate the admin functions - a Jira Admin is a Jira Admin, there's no way to limit them to projects (because all the stuff they do is effectively global)

But you can do the split at a project level. You set up two sets of projects, one for development and the other for the other stuff. Permissions can be set to grant access to one set and not to the other. I could ramble for ages, but I'd rather advise you to have a look at http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions and then get back to us with more specific questions if you get stuck!