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.
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.
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.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
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