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; } } }

One JIRA service project - how to keep clients separated

Joost Canters

Hi, we want to use one JIRA project for all post-project service issues (50+ clients, would be too much work making separate projects for every one of them)

What is, with regards to time/issue reporting to our financial administration, the best way to keep clients issues separated? A custom field for client id? different components for different clients?

thanks!

Accepted answers

darylchuah

Hi there

Basically, you can create Issue-level security for each different individual client.

Issue security levels allow you to control who can see individual issues within a project (subject to the project's permissions).

Quote from this documentation: Configuring Issue-level Security

Hope it helps

Cheers

All comments

darylchuah

Hi there

Basically, you can create Issue-level security for each different individual client.

Issue security levels allow you to control who can see individual issues within a project (subject to the project's permissions).

Quote from this documentation: Configuring Issue-level Security

Hope it helps

Cheers

Joost Canters

Thanks

I've read about that, but I basicly want all developers to be able to see all issues. I just want to keep the issue clients apart for reporting reasons, it's not so much a security thing.

Joost Canters

I should add that we don't have one software product, every client has own website /application etc