Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to configure services schema in Insight


In Jira Service Management - Insight, I am trying to configure a "Services" schema in order to add attributes to the object types, however I am not getting the option to do that. I have jira admin rights and I am able to edit/configure other schemas and their objects/attributes but not the "Services" schema.

Any idea why it is so and how to fix it?


1 answer

1 accepted

0 votes
Answer accepted

This schema is read-only and intended as a reference only. Modify services on the "Services" page in your JSM Service Desk, but you cannot add custom attributes. See

I have got services interacting with another schema, but it only creates "Business Service" objects in the other schema and doesn't update them. Synchronising services across an object schema you can modify would take a couple of rules to do, but it just isn't possible yet with Automation. See

Hi @Alex van Vucht (GLiNTECH) ,

Thanks for your answer. I was hoping to add some key pieces of information regarding the services so it can be used by agents while working a ticket, but that doesn't look so straightforward to do here. I'll try to find a workaround.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events