Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
How much data can you store in Assets?
As of 16 October 2024, usage limits will apply to Assets and the virtual service agent in Jira Service Management. See our blog article for more details.
Assets in Jira Service Management is a database and so requires a combination of good data modelling and a great deal of processing power to handle large amounts of data. Here are recommendations for how to structure your data for Assets schemas.
See also: How to build an effective ITAM schema structure.
For this reason, there are limitations on how many objects, attributes, and attribute characters can be stored inside schemas within each individual Assets in Jira Service Management site. Exceeding these limits can cause performance and reliability issues, therefore each site cannot create further items once they reach the limit.
Feature usage limits do apply to Assets in Jira Service Management. Premium and Enterprise customers get up to 50,000 Assets objects included as part of their plan. What is feature usage and how it works.
The limitations are as follows:
Feature type | Context | Limit |
|---|---|---|
Maximum number of schema objects across Assets | Global | 3 million |
Total number of schema objects in Services schema | Schema | 20,000 |
Total number of schemas | Global | 100 |
Total attributes per object type | Object type | 200 |
Total TextArea attribute characters | Object | 10,000 |
Total Text attribute characters | Object | 255 |
Maximum cardinality in an attribute | Object | 20,000 |
Maximum import file size | Schema | 250MB |
Was this helpful?
Still need help?
The Atlassian Community is here for you.