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

Your Points Tracker
  • 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
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?
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

How to disable private request option in JIRA Service Desk with Ultimate Theming / JavaScript / CSS? Edited

Hello we run Jira Service Desk and some of our customers are packed within organisational units.

Our problem now is, that our customer doesn't want his employees to be able to raise private requests. All requests they create in the Service Desk portal should be shared with all people within the same organisation.

We also run Ultimate Theming so we are able to use JScript CSS and stuff to manipulate the portal design and behavoir but I'm not really into this kind of coding or webdesign. So is there an option to hide the private request Button or better to change the default in red to "Share with organisation" and remove the Drop Down option?


2 answers


I have the same challenge.

We use automation to group customers in the correct organizations. This overrides any choice they can make and it's very confusing that I can't remove the private request Button. 

The automation feature of service desk or some Addon? So you couldn't find any solution tilll now? We're still on this

Yes, the automation feature in service desk.

It is very strange that there is no option to hide the private request Button....!

I asked another question, if we could solve this using scripts after an issue is created. Maybe this works, I'll keep u on the run.


'We use automation to group customers in the correct organizations' sounds like good idea, but I don't seem to be able to find the IF clause that would check that for me, e.g Organization is EMPTY, because 'is' is not valid in the automation rule set-up for the field Organization.

Thanks for your advice.

Organizations = empty

Above should work

The above does indeed work to select if the automation should run (if org field is empty) but it is still not clear how to then populate the org field from the users pre-set organisation (ie if they select private because there is no way to remove the private option, so looking to over ride that and then populate it regardless).

Suggest an answer

Log in or Sign up to answer

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