External use of Jira

GilK

Hi,

We have Jira + GH + confluence + tempo on premise installation.

We use Jira internally for tracking bugs, managing tasks (requirements, stories, etc.), knowledge base and managing releases (to QA, integration and customer).

We're thinking of opening our Jira for external use by our customers and partners.

What would be the best way of doing it?

How do you do it?

What is the relation between the external content and the internal content (i.e. when a customer reports a bug, how it interface with the internal system?).

Thanks,

Janiv Ratson.

SimonS

Hi janiv,

There are a couple ways you could do this. One is to grab an unlimited-user license for JIRA and then open-up JIRA to public signups:

https://confluence.atlassian.com/display/JIRA/Enabling+Public+Signup+and+CAPTCHA

Then your customers and partners could sign up for their own account, submit bugs, etc.

You can also partition JIRA so that user groups do not see projects or issues not related to them:

https://confluence.atlassian.com/display/JIRAKB/How+To+Partition+JIRA+for+Different+Isolated+User+Groups

Alternatively, if you don't want to purchase an unlimited-user license, you could open up your JIRA instance to anonymous access:

https://confluence.atlassian.com/display/JIRA/Allowing+users+to+create+issues+anonymously

You can restrict which issues/projects these users can see, just like any other user group.

At Atlassian, we have public projects for each of our products and internal private projects also. When a user reports a bug in the public project and we verify it, we clone it to the development project and track it there. Both issues are resolved when we release a new version.

-Simon