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

Assets: features and limitations of the default Services (SVC) schema

Jira Assets comes with a default Services schema.

It seems it has some benefits, for instance

  • cross-product integrations (for instance with OpsGenie).
  • nice integration within Jira Service Management

However, there seems to be limitations as well, for instance

  • I'm unable to set a dependency relationship between a Service asset object and an object from another Assets schema / object type.

Is there an official documentation of the features and limitations? 

Why would you use (or NOT use) this Services object type for? 

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events