Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Restrict customers to see only specific Request types or Custom Field

Hello - wondering if anyone can give some advice on this.

I have a service desk that has many customers (over 50). However I need to restrict access for a handful of customers (3 max) to only see requests that have the a specific value (i.e NZ) on a custom field (i.e. Business Unit). There are 8 other values for this custom field. This custom field is a mandatory field in every request. 

Alternatively if there isn't a solution to the above, could I restrict so these 3 customers only see requests they are either a reporter or participant of? 

The solution can't affect the remaining users as they are the majority and need to be able to see all requests and reporting is based on the entire service desk. 

Any advice would be greatly appreciated. Thanks

 

2 answers

0 votes

@Centuria Registry 

Welcome to the Community.  You can implement Issue Security solution where you can associate JSM project's issues with security level.  This option allows you to restrict visibility of the issues.

Here is a link reference on Issue Security Scheme - https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Once you have your issue security scheme configured, you can even customize your WF to set security level automatically at issue creation process via post-function call based on your custom field's value that user entered for his/her request.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Thanks Joseph

I've read through the reference and trying to understand. 

Do I need to set a ISS that will apply to ALL my issues and therefore requests types by as a default? And then set another for just customers I want to restrict which requests they see? Or if I set the only restriction for these couple of customers will it affect any other customers?

 

Thanks

@Centuria Registry 

You can setup ISS and assign the security level issue by issue basis if that is appropriate for your end.

If you can identify the issue at issue creation time, then you can set the security level via post-function call in your WF.  This eliminates the need for manual setup.

ISS is simply further control the issue discovery to users/customers.  Once an issue's security level is set, then only the users configured in the ISS security level can see them.  If all other issues are open for everyone, then no security level is needed.

Best, Joseph

0 votes
Dirk Ronsmans Community Leader May 12, 2021

Hi @Centuria Registry  and welcome!

i'm a bit confused about your question, perhaps you can clarify this for me.

You mention you have customers so they will raise their tickets on the Portal right? Now the limitation of the visibility, do you want to limit 

  • what they see on the portal when they are submitting a request OR
  • do you want to limit what they see once submitted?

the first one (limiting what they have access to on the portal for submitting) is not something that is possible out of the box.

The 2nd one, (as a customer) will be by default limited based on who reported it and/or whether the issue is shared within an organization or other customers.

Hi Dirk

I want to limit the submitted requests that a couple of customers see. Everyone else can see all submitted requests (including their own or other customers). But these couple of customers I need to restrict, should only be able to see requests for a particular value of a custom field and maybe a specific request type. 

John Smith = can see all requests submitted

Jane Doe = can only see requests submitted that have the value NZ as the custom field for Business Unit OR if that doesn't work then only see requests they are the reporter or participant of.

Thanks

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

322 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you