Hide groups on the portal

This question is in reference to Atlassian Documentation: Configuring request types and workflows

Is there a way to have a request type that is hidden from the portal? When I try and have a request type that is not part of a group, it gives me an error saying that at least 1 group is required.

1 answer

1 accepted

1 vote
Steven Behnke Community Champion Jan 08, 2016

Request types must be assigned to a group. It's required as you noticed. Can I ask why you'd like a hidden request type? Maybe we can figure something else out...

We have an operational request type for internal use only. I just wanted to hide it from the customer portal, but retain the request type. I believe this can be accomplished via request type permissions and I just need time to explore it more.

Steven Behnke Community Champion Jan 08, 2016

I don't believe that's possible. It's never been possible to configure permissions by issuetype. I don't think Service Desk gives you any abstraction that allows for additional permissions on requesttypes. If you need separate permissions, you should use a separate project. You can also make an issue type in a project that's not assigned to a request type; this would mean that the only way to create that issuetype would be through the JIRA Create Dialog, not the Portal. That's usually my go-to...

Yes, that was going to be my direction if the perms route did not work. Question though, without the Request Type, does the notification scheme still function correctly? I noticed that when my Incident, Service Request and Operation ISSUE TYPES do not have the proper REQUEST TYPE field filled out within the issue itself, the notifications and workflows can be wonky. Wonky in that they work sometimes and sometimes they don't.

Steven Behnke Community Champion Jan 08, 2016

Yeah, be sure to read the documentation closely. I'll try to be succinct here. An issue is ONLY a request if it has a valid Request Type set. If it's a REQUEST, Service Desk will use the SERVICE DESK notification scheme for the CUSTOMER. If it's NOT a REQUEST, the JIRA Notification Scheme will take over (for licensed users). The JIRA Notification scheme should always be in place for Agents.

Excellent. Thank you for clarification.

Steven Behnke Community Champion Jan 08, 2016

Any time Dan.

Suggest an answer

Log in or Join to answer
Community showcase
Louis De Jaeger
Posted Thursday in Off-topic

Friday fun: your best joke

Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...

189 views 12 3
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot