Get to know Assets
Starting with Jira Service Management 5.3, our asset and configuration management tool is getting a new name: Assets. While we’re moving away from the old name— Insight—Assets will still give you the same great functionality you’re used to. Read on to see what we’re changing and what you can do with Assets.
What is Assets?
Assets, previously known as Insight, is a tool that lets you keep track of everything that makes up your organization—from employees, to keyboards, servers, network adapters, offices, or even services, such as payroll or billing. If you need a place to store information about any person or object, Assets is there to lend a helping hand. It comes bundled with Jira Service Management, so you have everything in one location.
New to asset and configuration management in Jira Service Management? Learn how to get started with Assets.
Insight will automatically change to Assets after you upgrade to Jira Service Management 5.3. You don’t need to do anything to see the new name. Read on to find out what you can expect after the upgrade.
The name Assets will now appear everywhere you used to see Insight—navigation, buttons, role names, settings, Jira automation, and documentation.
What about IQL and my existing queries?
We’re also rebranding Insight Query Language (IQL). IQL is now called Assets Query Language (AQL). In JQL advanced search, the new name of
aqlFunction. Don’t worry about the queries you’ve created in the past, though—
iqlFunction will still work and so will your queries.
Atlassian Marketplace apps will also use the new name, so Insight Integration apps are now becoming Asset Integration apps. But just like the Assets tool, your marketplace apps will still work the same way they always have.
Assets Public REST APIs
Our public REST APIs are part of the rebranding process as well. All existing endpoints and parameters will still work as expected. However, if you have any custom integrations that use the public REST API, we recommend migrating to the new endpoint and parameters and testing your integrations to make sure their behavior hasn’t changed. Here’s what we’re rebranding:
/rest/insight/1.0/....is rebranded into
/rest/insight/1.0/.../iql...endpoints are rebranded into
Any JSON request with an
iqlparameter will now support a
qlQueryparameter that does the same thing. However,
iqlwill still work for backward compatibility.
Any JSON response with an
iqlattribute will still return this attribute, so that existing integrations do not break. However, the JSON response will now also return a
qlQueryattribute alongside the
iqlattribute, with the same value, to encourage the transition.
Was this helpful?Yes Provide feedback about this article