Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Creating a bug tracker for multiple external partners

I am looking to see if there is a way to create an all in one tracker within JIRA. Currently we partner with multiple other companies. We have our JIRA instance that we track bugs in but then go to each individual partners JIRA instance and basically copy and paste their bugs into our tracker and sync them that way. This is very time consuming and also opens up the opportunity of missing something. 

  I wanted to see about a way of setting up one instance when our external partners can access this instance of JIRA and log their issues.  The thing is we need it so that they only see their issues and none of the other external partners issues. 


Please help

1 answer

Hello @Josh Barnes 

Welcome to the community.

JIRA Service Management would enable you to have a single JIRA project in a single JIRA instance that you could allow external individuals to access. It can be set up so that the external individuals are grouped into organizations and can see the issue created only by members of their organization.

JIRA Service Management is licensed per "agent" - those are the users in your organization who can access the project and manipulate the issues. You can have an unlimited number of external individuals ("customers"). Users in your organization that have access to your JIRA Software product do not automatically get access to your JIRA Service Management project as "agents". Only "agents" and "customers" can interact with the project.

The workflow is organized around providing "service", though, like a help desk. It isn't really set up for tracking software bugs. However, you could create bugs in your JIRA Software project that link to the JIRA Service issues. Your external customers would not be able to see the bugs in your JIRA Software project.

Thank you for the information about this! So may I ask you one more question about how I can go about setting up the different external partners as organizations  and allowing them into a single project as well as only allowing them to see items added by members or their organization.

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

95 views 0 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you