Forge App with Asset fields

Forge Forge UI Kit and Custom UI
1

We are currently developing a Forge app using UI Kit that renders a custom grid/table view in the Jira Issue Agent View (Issue Panel). The table is intended to display and manage asset-related data directly within Jira Service Management.

Current State

  • We have successfully built and deployed a Forge UI Kit issue panel that displays a grid/table with calculated values.

  • The app is currently using static data for proof-of-concept purposes.

  • The table is rendered for agents only in the Jira issue view.

Target Requirement

We would like to synchronize Jira Assets (formerly Insight) object data with this Forge-based grid table and enable the following capabilities within the same UI:

  1. View Asset Data

    • Pull asset object attributes (for example: Asset Name, Object Type, Cost, Quantity, Serial Number, etc.)

    • Display these fields as rows/columns in the Forge grid table.

  2. Edit Asset Data

    • Allow agents to edit selected asset attribute values directly from the grid.

    • Persist the updated values back to the corresponding Assets object.

  3. Create Asset Records

    • Provide a way (for example, an “Add row” or “Create asset” action) to create new asset objects from the same table UI.

    • Map the entered values to the appropriate Assets object type and attributes.

  4. Synchronization & Data Consistency

    • Ensure that updates made via the Forge app are reflected in Assets immediately.

    • Ensure that changes made directly in Assets are reflected when the issue panel is reloaded.

Clarifications Requested

We would appreciate guidance on the following points:

  1. Supported APIs

    • Which APIs are officially supported and recommended for Forge apps to:

      • Read Assets object data

      • Update Assets object attributes

      • Create new Assets objects

    • Is the Assets REST API fully supported from Forge using @forge/api?

  2. Authentication & Permissions

    • Are there any additional scopes or permissions required in manifest.yml to interact with Assets data?

    • Are there limitations when accessing Assets from Jira Service Management projects?

  3. UI Kit Limitations

    • Are there known limitations when implementing editable tables or create/update actions for Assets using UI Kit?

    • Would Atlassian recommend Custom UI instead for advanced grid editing scenarios, or is UI Kit sufficient?

  4. Best Practices

    • Recommended patterns for synchronizing Assets data with Forge UI components.

    • Any reference documentation, examples, or sample apps demonstrating Assets + Forge integration.

Objective

Our goal is to provide agents with a single, unified grid view inside the Jira issue, where they can:

  • View related asset data

  • Perform lightweight edits

  • Create new asset entries
    …without navigating away to the Assets interface.

Any guidance, documentation links, or architectural recommendations would be greatly appreciated.

Thank you for your support and time.

Kind regards,
Ravi Teja