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

Restrict access to tickets based on the custom field value selection

manikanta ch

Hello Alll,

We want to restrict access to tickets based on the custom field values selection.

For Example - we have a custom field(single select) called Partner and it has options 1,2,3

Tickets will be created in Project by 3rd party partners. there are 3 users of 3rd party partners, each partner has there own value in the Partner field. If 3rd party partner 1 created a ticket with a selection of Partner 1 option, the ticket has to viewable only to him and other partners should not see the other partner tickets.

We have a script runner installed in our instance. Please help me with the script if any one done this before.

Thanks in advance,

Accepted answers

All comments

Marek Soukup_zdtg7e

Is there a reason why you don't want to use security levels (https://confluence.atlassian.com/jirakb/issue-security-levels-locks-issues-from-all-users-636421142.html)? It sounds it is a perfect solution for you.

If you need more info, feel free to ask.

manikanta ch

Hi @Marek Soukup ,

Thanks for reply. Could you please provide me more details, how to set the security level on issues with the URL you shared?

Thanks,

Marek Soukup_zdtg7e

Hi,

sorry, I post wrong link. I didn't find documentation for cloud version, but it is the same https://confluence.atlassian.com/adminjiraserver072/configuring-issue-level-security-829827025.html.

It is another scheme you can create to define permission to individual issue, not only a project.

manikanta ch

I know about the Issue security level scheme. How can we define custom field values in the scheme?

Welcome!

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

Quick Links

Find more posts tagged with

server

scriptrunner

jira

jira-server

groovy

behaviours