Using components in permission schemes

We have a project that is intended to be used by internal and external customers. External customer tickets are given a component (ie, cust1, cust2) etc. Is there a way of permissioning such that customers can log in and only see the related components?

Is this futile, and best done through groups? If so, how does one ensure that only tickets for that group are visible to that group?

2 answers

1 accepted

Update: Did use an issue security scheme but there were too many wrinkles to deal with on a legacy installation; we did a clean external install instead. Really need better project-based security, preferably by linking projects to directory services exclusively.

0 votes

The best thing to do is to use issue security schemes. Create security levels for each customer group and they will then be able to see only their tickets.

This is my preference; hopefully the client will be happy with that.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,723 views 17 21
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you