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

This widget could not be displayed.

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.

This widget could not be displayed.

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
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

194 views 1 3
Join discussion

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