Description:
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:
Both approaches are error-prone and add unnecessary friction, especially for teams managing large hardware or infrastructure inventories.
Desired Behavior:
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:
Affected Area:
Jira Service Management Cloud (Premium/Enterprise) β Assets (Insight) module
Environment:
Jira Service Management Cloud
Hello and Welcome to Atlassian Community @Marco Jaussi
The current process for Feature Request is to submit the request through Atlassian Support or the in-product feedback option so Atlassian can create or link the relevant JAC suggestion.
Best,
Arekπ€
Welcome to the community.
You cold look at having attributes like maintenance date set on assets and have an automation rule to find these objects and create related issues for each found item on based on if this date matches todays date or in the future.
The same could be done based on a status or boolean attribute for replacement based on status replacement or yes/no.
On resolving the issue, you could update the realted attribute.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.