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

Request Types Groups Permissions?

[Deleted User]

Hello,

I have the need to have different permissions/views in the portal. I have external customers that need to see certain request types groups/actions and then my internal staff have other needs.

I do not want two separate projects as a lot of the SLAs, workflows, etc.. are the same. That also creates a lot of issues when we have to move external clients issues into our internal change management, problems, incidents, etc....

So I basically want to have:

Permissions of user groups to be able to see certain request types within the portal
OR
A secondary view (or portal itself) within a project

Thanks

Brandt Winchell

Accepted answers

Susan Hauth _Jira Queen_

Hi Brandt,

It's currently not possible to add in different permissions within a single service desk. This can be done by an add-on for Server version but I see you are on Cloud.

I would highly recommend you have two different service desks. The SLAs can be copied to the new service desk and a single workflow can be shared among more than one project.

Hope that helps

Susan

All comments

Susan Hauth _Jira Queen_

Hi Brandt,

It's currently not possible to add in different permissions within a single service desk. This can be done by an add-on for Server version but I see you are on Cloud.

I would highly recommend you have two different service desks. The SLAs can be copied to the new service desk and a single workflow can be shared among more than one project.

Hope that helps

Susan

[Deleted User]

I guess it was the answer I was afraid it would be.

Thanks

[Deleted User]

So after spending the day building a new project, I have run into a major issue due to the fact I cannot restrict the portal tasks based on roles.

If I have to have two separate projects just due to this fact, it will complicate things drastically for my team and cause duplicated work. I would have to duplicate a lot of the tasks, SLAs, configure request types & workflows. But most of all, the organization/customer records. I would need to maintain both projects with the exact same customer records. This is not feasible.

Is there a way to automatically transfer an issue created in the external project to my internal project? This way the external project is strictly only used to facilitate the initial request and all further transactions would be from our internal project.

Second thought, this would still be problematic. As the customer would still need access to the portal to see ticket updates, etc....

Not happy. This might be a deal breaker for this product.

Susan Hauth _Jira Queen_

Hi Brandt,

Via the automation you can create linked issues form new requests. See this blog:

https://confluence.atlassian.com/servicedeskcloud/blog/2017/12/automatically-create-linked-issues-from-new-requests

You can also update issues based on a linked issue update via automation.

Hope that helps

Susan

Shreyas Srinivasa

Hi @Susan Hauth _Jira Queen_,

I have a similar issue and you said this must be possible through an addon for the server license. Can you please advise which addon to use?

Thanks.

Shreyas

Susan Hauth _Jira Queen_

Hi Shreyas,

THe app is Extension for Jira Service Desk.

It's under "Visibility" - Request Types that you can specify which groups have visibility to see request types.

Works great

Susan

Shreyas Srinivasa

Hi @Susan Hauth _Jira Queen_

Thank you for the quick response. The Addon worked for our requirement.

Thanks.

Shreyas

Susan Hauth _Jira Queen_

Thanks Shreyas, please "accept the answer"

Marco Augusto Santinho Gonçalves

Extension just work for visibility in server version...not in cloud

Trey Bornmann

Why is this basic functionality missing in Jira? The ability to limit request type by group is pretty standard in this realm. JSD does not seem to be a mature product but they charge more than many full-featured Service desks.

Does Jira have an ETA on these basics being implemented? It would be nice to see the list so customers know if they need to look elsewhere.

Pieter Wouter Hartog

We need this too. Vote for this 'Suggestion' to help elevate the urgency for this issue:

https://jira.atlassian.com/browse/JSDCLOUD-195

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

jira-service-desk-cloud