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

How can I manage several read privilege on one same JIRA ticket board? Edited

I want to manage issues/requirements for out service from several user company on one JIRA ticket board. And I don't want to prepare a few different ticket board for each user company.
How can I achieve the bellows?

- I need to have Read/Update privilege for all tickets
- Member of each user company have Read/Update privilege for tickets which belongs to their own company, and no access privilege for tickets which belongs to other company.

Is the above possible only with standard plan, or do I need to use some 3rd party app with additional budget?


1 answer

0 votes
Jack Community Leader Mar 17, 2021

You could look into Issue Security but to be honest, if I were working with multiple companies I likely would be using separate projects. Of course I don’t know the details of your situation just thinking about keeping company info separate.

If we use "Issue Security", issuer of ticket need to choose security level, which means, ticket issuer of company A can share their company A's confidential information with us and company B, by mistake or intentionally, I guess.
Is there anyway to set this access control automatically (not by ticket issuer) ?
(Sorry if my understanding is wrong)

And as you mentioned, separating ticket board(project) is another option.
I just want to have single point of view for customer service as its a little bit difficult to handle requests/issues from many customers on many different ticket board.

John Funk Community Leader Mar 18, 2021

Hi @yusuke.yonenaga  - Welcome to the Atlassian Community!

How are you identifying Company A Staff and Company B Staff issues? Are they all in the same project? Do you have another field that identifies how the ticket applies to which company? 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Product feedback on Inline Comments

Hello Community members! We have an upcoming research study for Confluence and we’d like to invite you to provide advice and answer questions. We’re developing a new experience for Inline Comment...

85 views 5 4
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