nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Using components in permission schemes

aarnetadmin

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?

Accepted answers

aarnetadmin

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.

All comments

Jobin Kuruvilla [Adaptavist]

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.

https://confluence.atlassian.com/display/JIRA/Configuring+Issue-level+Security

aarnetadmin

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

aarnetadmin

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira