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

Managing access to your service desk - Agent can only edit specific Organization

Snir Ben Yosef

Hello Everyone,
I have a service desk project and inside I have 20-30 Organisations,
we are 3-4 Agents on the team.

I would like to ask if there is a way to give permission to the first agent only to a specific Organizations? the agent should Create/edit/update/view only the organization tickets related to him.

Accepted answers

Vishwas

Hi @Snir Ben Yosef

Well there isn't any straight forward way to block agents to edit other organization tickets in vanilla schemes

This might be possible by defining the Security Level via Issue Security Scheme.

You can create a Issue Security Scheme , define Security level and write an Automation such that for the tickets created with that particular organization gets that security level. And agent to be present in that security level. By achieving this steps you can make sure he will be able to Create/edit/update/view only the organization tickets related to him.

Link about configuring Issue Security Scheme https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Regards,

Vishwas

All comments

Bastian Stehmann

Hi @Snir Ben Yosef ,

Welcome to the community.

I think, you might achieve this using issue security.

You have to define one level per Organisation. Then you have to set the security level according to the organization.

I think, this should be possible with automation

This might help you.

https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Vishwas

Hi @Snir Ben Yosef

Well there isn't any straight forward way to block agents to edit other organization tickets in vanilla schemes

This might be possible by defining the Security Level via Issue Security Scheme.

Link about configuring Issue Security Scheme https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Regards,

Vishwas

Snir Ben Yosef

@Bastian Stehmann @Vishwas
thanks you both.

but i'm not sure how to do it,
i created in automation ->
1. Issue Created ->Condition:issue field, organization="myorganizaition" ->Action: Edit Issue, Securtiy Level.

The security level is empty.
i did create security scheme and security level in the project. but i dont see it on the Rule.
do you know where is the issue ?
Screen Shot 2021-12-21 at 17.33.18.png

Vishwas

Hi @Snir Ben Yosef

You are doing the automation in a right way. Can you confirm by going to project if you have associated the Issue security scheme to the project ?

what options are showed when you click on dropdown ?

Regards,

Vishwas

Snir Ben Yosef

@Vishwas Yes i have associated the Issue security scheme to the project.

there are no options to select, its None.
what am i doing wrong ?

Vishwas

Hi @Snir Ben Yosef

Let me try this once my side and get back soon.

Regards,

Vishwas

Hi @Snir Ben Yosef

I figured out the issue, did you add yourself into the security level. Ideally you should be part of all security levels in Issue Security Scheme so that you can configure automation then only the dropdown in automation shows the options.

Regards,

Welcome!

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

Quick Links

Find more posts tagged with

atl-gruland

jira-service-management-cloud

jira-service-management