The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
- Community
- Q&A
- Jira Service Management
- Questions
- Assets: features and limitations of the default Services (SVC) schema
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
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Atlassian Community Events
Copyright © 2026 Atlassian