-
Suggestion
-
Resolution: Unresolved
-
383
-
Problem
Currently the services are part of a separate object schema called Services. There is no option to have these in the same schema as other Assets objects. Also, it is not possible to create child object type for Services object type.
Suggested Solution
There should be option to have the services in the same schema as any other Assets objects. Also, the ability to create child object types for Services is important.
Why This Is Important
- Better manageability as one object schema can manage all object types
- A regular object schema offers more granularity than Services schema
- Be able to set permissions based on the Schema Roles, with that, not allowing Agents to create new Objects under Services
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
[JSDCLOUD-10461] Assets: Enhanced capability of Services object schema like regular schemas
I am wondering why this feature request has so few votes. The request seems like a no brainer to me.
Is simply no one working for a bigger company using Assets to manage services or did we (who will probably need to wait for years to have this implemented) miss something here!?
Adding my upvote to this, especially for the point on being able to set permissions on the services so that all agents do not have unchangeable read-all, write-all access to my services as they do right now - unlike regular assets, we cannot configure the system-defined Service schema's permissions; the Configuration option for both the schema & object types within the schema is missing.
For my use case, I only want particular groups to be able to view the Services, and even fewer groups to be able to edit the Services. I can do this with regular asset objects, but not this services schema object.
We are currently trying to sync the builtin service catalog with our own in JSM assets. We will use the Opsgenie API for now but it is not an optimal solution. An easier way to integrate the catalog or extend it with own attributes and relations would be better.
Anybody interested in this feature request might be interested in this as well: JSDCLOUD-13559 Ability to use other Asset Object Schema in Affected Services Field - Create and track feature requests for Atlassian products.
please vote on it 
Insight is a great tool for creating and managing the ITSM Service Catalog, but it is not possible to use it in OpsGenie as the default object schema (Services) is not extendable.
On the other side, this schema (Services) is not useful for using outside OpsGenie.
Would be really useful to be able to create one Object Schema for all use cases - as a complete service catalog, for OpsGenie service list, etc.
Hello Team,
FYI, I just opened a Prio 2 Ticket here: https://support.atlassian.com/requests/CES-62057/
Basically, adding any interface user with an Agent License, can read the Services Schema. That is a big problem when that interface is with an external company (partner or customer) to sync tickets. This feature request or at least the security part is very much needed.
Best regards & thx,
Andreas