Improvements to Jira Service Management DC's Assets interface

[#1]

We bundled Assets (formerly known as ‘Insight’) with Jira Service Management Data Center in version 4.15, adding core asset and configuration management capabilities to the product. With the release of the 5.4 Long Term Support (LTS) version, we wanted to take a moment to highlight the series of accessibility and user interface improvements we’ve shipped since the previous 4.20 LTS to make Assets feel more at home in the JSM feature set

We’ve completed two major milestones:

1. Uplifting Assets in particular within standards of accessibility and user interface. ✅

2. Rebranding Insight to Assets, to be more representative and descriptive of the feature set’s value. ✅

Milestone 1: Assets uplift

Post-bundling, there was naturally a clear disconnect between the asset and configuration management interface and the wider Jira Service Management product. We wanted to provide a more consistent experience with Assets that was synonymous with Jira Service Management. This project aimed to narrow this disparity, specifically within the standards of accessibility and user interface.

The scope of this uplift focused on the following areas:

1. Issue view (Jira issue view, custom field)

2. Customer Portal (Customer portal, custom field)

3. Object schema view (Assets view)

4. Side panel (Assets view)

5. Asset view (Assets view)

Voluntary Product Accessibility Template

We recently updated JSM DC’s VPAT assessment, using the assessment results to create the backlog of accessibility improvements for this project. We officially resolved 55 (distinct) critical Assets related VPAT issues, which make up ~46% of the total critical product-wide accessibility issues. We have an ongoing commitment to resolve the remaining critical issues in Jira Service Management.

Milestone 2: Rebranding Insight

We rebranded our asset and configuration management feature, Insight, to Assets. We feel the new name is more representative and descriptive of the actual value the feature set provides. We made this change to help you more easily navigate our platform and better understand where to go for specific functionalities.

So, how does Insight Assets look now?

For both projects, we shipped a wide scope of changes. To help capture the true essence of this work, we wanted to share some before and afters belonging to different user journeys.

Customer

1. Create a request associated with an asset.

Before: Create request form with Assets custom field (Customer portal)

After: Create request form with Assets custom field (Customer portal)

Example accessibility change:

Before: Interacting with the Assets custom field when creating a request

After: Interacting with the Assets custom field when creating a request

Admin

1. Navigate to Assets

Before: Navigation to Insight

After: Navigation to Assets

2. Create a new object schema.

Before: Empty state object schema

After: Empty state object schema

3. Populate object schema with data.

Before: Create object types	After: Create object types
Before: Populate schema	After: Populate schema

Example accessibility changes

Objects before/after	Adding search filters before/after
Removing search filters before/after	Comments before/after
Object type tree before/after

Agent

1. Seek more context for an issue by reading the overview of the associated object.

Before: Object overview

After: Object overview

Example accessibility changes

Before: Object overview

After: Object overview

What’s next for Assets?

We hope you’re just as excited as we are about the recent improvements waiting for you in the latest LTS! We continue to work on improving the integration of Assets with Jira Service Management. Stay tuned for additions to auditing events for Assets, security enhancements, and performance and scale optimisations in upcoming releases!