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

Hide Raise a Request

Frank Miu_h6dy6y

We're currently working on setting up our Jira Service Desk environment and want to first set up the whole Knowledge base before we actually open up the request button.

Is there a way how we can hide or turn off the raise a request button?

I tried a stripped version of the Permission Scheme, but that only restricts people from sending in requests instead of completely hiding the button.

Accepted answers

Jack Brickey

unfortunately not. I do wish there was a way to easily disable the project before it goes live. But there are options...

consider a restricted temporary permission scheme that doesn’t allow users to create issues
add agents and customers as the last step

All comments

Jack Brickey

unfortunately not. I do wish there was a way to easily disable the project before it goes live. But there are options...

consider a restricted temporary permission scheme that doesn’t allow users to create issues
add agents and customers as the last step

Frank Miu_h6dy6y

That's the 5th thing I was looking into that the cloud platform can't do.

Can't edit css-styling of the pages
Can't sort the articles
Can't assign a custom URL
Can't use Friendly URLs
Can't restrict access.

The Jira / Confluence integration and automation is nice, but for a platform that's been around since 2013 it feels underdeveloped and underwhelming in the basics.

Paul Krueger

Can't you just create the Confluence KB before linking it to the JSD instance?

Frank Miu_h6dy6y

Would this be accessible for customers in the same fashion as a JSD portal?

Cause I haven't found that type of setup yet.

Paul Krueger

Your request suggested neither the KB nor the JSD were ready for use, but now I understand you want to allow KB access through JSD before allowing people to actually use JSD.

Honestly, I'd say the opposite process would work well. Force them to come to the portal to submit/review issues and then expand the value to them by adding the KB.

Frank Miu_h6dy6y

The problem is that we already have most KB articles set up and are working to get it ready,

We just haven't got the backend of JSD working the way we want as you can see from the other 5 things it can't do.

So if tickets get send in it' could potentially create a mess / cause tickets to never be received or picked up.

Nic Brough -Adaptavist-

Well, it can restrict access, but the other four are good reasons people go to Server/DC from Cloud.

Jack Brickey

agree w/ Nic. It seems like you might be better off considering Server/DC if these requirements are musts.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-desk

atl-gruland