Unlock Schema Configuration for the System-Managed "Services" Assets Schema - Feature request

[Phoebe Black]

Description: In JSM Cloud, the "Services" schema in Assets is locked and read-only. This creates a significant "feature trade-off" for IT teams.

The Problem:

1. Limited Taxonomy: We are restricted to 4 hardcoded Service Types (Business, IT, Application, Capability). We cannot add more specific types (e.g., SaaS, Managed Service, Infrastructure Layer).

2. No Custom Metadata: We cannot add critical operational attributes (SLA Tier, Cost Center, Security Classification) to the Service objects within this schema.

3. Feature Lock-in: While we can build a custom "Service Catalog" schema, doing so breaks native Cloud features like Change Risk Insights, Service Health Gadgets, and Incident Timeline, which only recognize the system "Affected Service" field.

Suggested Solution: Allow Jira Admins to customize the object types and attributes within the system-managed "Services" schema. If the default fields are required for system logic, they can remain locked, but the ability to extend the schema with new fields is essential for real-world service management.

[Jeroen Poismans]

Hello Phoebe,

This is a public forum, so feature requests are not going to be picked up, read or handled by Atlassian. Your best shot would be to use your support portal (I see you are on Entreprise?) to have Atlassian put this in a feature request.

[Arkadiusz Wroblewski]

@Phoebe Black 

Also to add to Answer from @Jeroen Poismans , Some Enterprise customers have a dedicated Customer Manager, so I would recommend trying that channel first.