Product: Jira Service Management - Assets (formerly Insight)

Current Behavior:
When viewing an asset object (e.g., XYZ-1234), there is no built-in action to create a linked Jira work item directly from the asset. Users must either:
• Use a custom URL attribute (e.g., CreateIssueDetails!init.jspa?pid=...&issuetype=...) as a workaround, which does not automatically link the new issue back to the asset.
• Navigate to a Jira project, manually create an issue, and then manually populate the Assets custom field to establish the link.
Both approaches are error-prone and add unnecessary friction, especially for teams managing large hardware or infrastructure inventories.

Desired Behavior:
• A "+" or "Create Work Item" button in the asset object detail view (next to or within the "Linked Issues" / "References" section).
• Clicking it opens the Jira issue creation dialog with:
o The asset reference pre-populated (e.g., the Assets custom field automatically filled with the current object key like XYZ-1234).
o Optionally, a configurable default project and issue type per object schema or object type.
• Upon issue creation, the bidirectional link between the asset and the Jira issue is established automatically.

Use Case:
As an IT asset manager at a media company, I manage hundreds of hardware assets (servers, network equipment). When a device needs maintenance or replacement, I want to create a work order (Jira issue) directly from the asset view with one click — without switching contexts, copying asset IDs, or relying on URL hacks. This would significantly speed up our incident and maintenance workflows.

Workaround in Use:
We currently use a custom attribute (Create_WorkItem) containing a pre-configured URL to the Jira issue creation form. However, this does not auto-link the asset, requires manual configuration per schema, and is not discoverable for new team members.

Impact:
• Reduces manual steps from 5+ to 1 click
• Eliminates risk of orphaned issues (no asset link)
• Improves adoption of Assets for operational workflows
• Aligns with the existing UX pattern in Jira (e.g., creating linked issues from within an issue)

Affected Area:
Jira Service Management Cloud (Premium/Enterprise) — Assets (Insight) module

Environment:
Jira Service Management Cloud