Problem

Currently, the Confluence Asset macro allows only list view(Horizontal Table) when displaying Assets data on a Confluence page.

Horizontal Table(The column names are side by side)

Column 1 Column 2 Column 3

Vertical Table(The column names are one above the other)

Column 1
Column 2
Column 3

Card(when accessing a single object)

Suggested Solution

Allow to configure different views when displaying the Assets data on the Confluence page: Horizontal Table, Vertical Table, Card

An example can be found in the following 3rd party app: Asset Studio (Confluence Macro) Your Data in Tables & Charts

Video: https://www.youtube.com/watch?v=UApx2t9ba9E

Why This Is Important

1. Improved Information Consumption

• Visual clarity: Card views are more intuitive than tables for quickly scanning through assets.
• Faster recognition: Images, key attributes, and labels displayed in card format help users recognize assets without opening details.
• Less cognitive load: Easier to absorb for business stakeholders who aren't used to database-like tables.

2. Better Collaboration and Communication

• Cross-team accessibility: Non-technical teams (finance, HR, facilities, etc.) can understand asset data more easily.
• Shared context: A card view in Confluence allows embedding assets into project spaces, onboarding pages, or service documentation in a way everyone can consume.
• Storytelling: Assets can be presented in context, e.g. linking assets to services, processes, or knowledge base articles.

3. Enhanced Decision-Making

• Quick overviews: Managers can quickly see available hardware/software licenses or service-related assets without drilling down into Jira.
• Prioritization: Cards can highlight statuses, owners, or SLA relevance visually, supporting faster decisions.
• Portfolio perspective: Assets grouped in cards (by type, status, or project) give a higher-level picture useful for budgeting and planning.

4. Increased Efficiency

• Reduced clicks: Users get asset insights directly in Confluence without switching back to JSM.
• Time savings: Teams spend less time hunting for asset details.
• Context integration: Assets shown alongside documentation, runbooks, or project plans make processes smoother.

5. Stronger Knowledge Management

• Richer documentation: Assets become part of Confluence pages (guides, FAQs, project hubs).
• Centralized view: Confluence acts as a single point where technical and business information is combined.
• Traceability: Easier to link assets to documentation, procedures, or service history.

6. Improved User Experience

• Engagement: Card layouts are visually appealing, encouraging use.
• Ease of onboarding: New employees can understand the asset base faster with visuals and key metadata.
• Accessibility: Different stakeholders (not just IT) can explore asset data in a more human-friendly way.

Workaround

None at the moment.