Is it possible to restrict SD Members to only certain organisations?

Caroline Worsley
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 4, 2018

We have one Jira SD project setup where the plan is for all customers (assigned to an organisation) can access and raise tickets for their organisation only.

What we'd like to do is setup SD Team Members to view only certain organisations e.g. one SD team member can view/action tickets for OrgA & OrgB, another SD team member can only view/action tickets for OrgA. Is this possible and if so how do I set this up please?

 

 

2 answers

1 vote
Manon Soubies-Camy
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 4, 2018

Hello Caroline,

@M Amineanswer looks good, but since you're on Cloud you may want to use the paid version Automation for Jira rather than the free Automation Lite for Jira.

The free version is limited to 300 rule executions per calendar month, so if you expect more than 300 tickets to be created per month, it can be a problem.

Hope this helps,

- Manon

M Amine
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 4, 2018

Yes you're right @Manon Soubies-Camy. Haven't noticed that it was about the Cloud Version. Thank you.

1 vote
M Amine
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 4, 2018

Hi @Caroline Worsley,

Welcome to the Atlassian community. 

Yes you can do what you want but you will need Automation lite for Jira.

Here are the steps to follow : 

  1. Create an issue security scheme and within it create as many security levels as you want (for example: SECURITY_LEVEL1 for agents who have to have access to OrgA & OrgB, SECURITY_LEVEL2 for agents who have to have access to OrgC ...etc)
  2. Assign this newly created issue security scheme to your project
  3. Go to Automation plugin/app and create a new rule
    • When : Issue Created
    • Add new Condition : JQL query with the filter on "OrgA & OrgB"
    • Add action : Set the appropriate security level that you have defined in step 1
  4. Repeat Step3 (i.e Add another rule) but for this time filter on "OrgC" and set the appropriate security level defined in step 1

Important notices : 

  • Do not allow agents to edit the security level
  • The owner of the rules you defined must have the ability to edit the security level

I have just tested this and it is working fine. 

hope it helps. 

cheers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events