🎁 Now available: Showcase your Assets objects in Confluence Cloud!

[#1]

Hello Atlassian Community 🙌

Big news! We’re rolling out an exciting feature that bridges the gap between Jira Service Management and Confluence like never before. Now, all agents with JSM Premium or Enterprise can effortlessly display objects from Assets directly in Confluence using the new ‘smart links list view’ and anyone with the new ‘object viewer’ role (no license required) can view them! A big leap towards making your data more visible across all kinds of teams.

What’s the scoop?

This feature allows agents with access to Assets (Jira Service Management Premium or Enterprise) to build lists of objects and related attributes via a simple macro in Confluence. These lists pull from specified object schemas and can be customized to bring important data about objects for improved reporting and visibility across teams - including those who don’t have access to Jira Service Management.

How can you start using this feature?

Diving into this feature is easy as:

1. Head over to a Confluence page you’re working on.

2. Type ‘/’ on your keyboard.

3. Type and select ‘Assets’ from the dropdown.

4. Select and display the Assets objects of your choice.

What about permissions?

We’re introducing a shiny new role in Assets — the object viewer. This role is designed for those who need to view all object data within a schema from the outside looking in, including from Confluence, but don’t need full access to Jira Service Management. It’s a read-only ticket to the data teams need without extra licenses - ensuring we maintain the integrity and security of your data while providing value for customers across the Atlassian Platform.

A note on licenses:

To insert and view these tables, you'll need a Jira Service Management Premium or Enterprise license. While insert and edit capabilities are tailored for Jira Service Management agents, we're opening up the table display to non-Jira Service Management users in future updates. It's all about inclusivity and making sure everyone's on the same page — quite literally.

We want to hear from you!

This feature is ready for you to explore and we can’t wait to see how it transforms your workflows and collaboration. Give it a whirl, push its limits, and please let us know your thoughts. Your feedback is the compass that guides our ship, helping us refine and perfect the experience for all.

If you have questions, need guidance, or want to share your success stories, our community is your go-to hub. Together, we're not just using tools; we're creating a smarter, more intuitive workspace for everyone.

Cheers to breaking new ground,

The Jira Service Management - Assets team

[Asmath Basha S]

Looking great. Whether this feature should be extended for JSM Standard Users?

[Tomislav Tobijas _Koios_]

We've 'released' this internally just yesterday and had all positive feedback so far! Really glad this finally came out 🎉

[Mohamed Hassan]

Thanks @Asmath Basha S - There are no plans to enable it for the standard tier at this stage.

[Tyler Krzanowski]

Thank you for implementing this!  We were to the point of trying to find a different way to have non-agents view the data.

This is a huge life saver!

Thank you again 

[Rudy Holtkamp]

Hi @Mohamed Hassan ,

It looks really promising, just a few observations:

1. There is no possibility to show objects of two objectschema's in the same table. It would be able to select multiple objectschema's. Use case:  show all objects that are assigned to a user. These objects can be stored in multiple objectschema's.
2. If you have multiple objecttypes that you want to show, you should be able to select the attribute e.g. 'Status'. This should give you the status regardless of the attribute id. All objecttypes could have a status attribute which have different attribute id's. 
   You will get multiple status columns, which is not very nice.
3. When you want to select the attribute as a column, you can't see of which objecttype the attribute is from.

So far my two cents.

Rudy

[Ralf Scheller]

Great feature - is it possible to export the list?

Ralf

[Pedram Mireftekhari]

This is a very convenient function but missing a main function:

Being able to filter the result in the macro table when the page is published, otherwise this is half done feature!

Also I want to know how does that work with anonymous page restriction access in Confluence, do we need to specify users and groups(?) in Asset with object viewer role or can it also give anonymous access in the object viewer roles?

[Dan_Scher]

Without a Search, Filter, and Sort feature, outside of AQL. Not very helpful. Needs work! 

[Ulf Johansson]

This is a very desired feature :-)

• A wish (request): a slimmer top and bottom of view, escpecially bottom is to big
• A dream: some  kind of "dynamic" view when you wish to joint a couple of objecttypes i same view where "table" can show different depening on objecttype but still in the same view

[Frederic Wolf]

Hi @Mohamed Hassan ,

that is very nice.

@Tyler Krzanowski : Thank you for the Idea, we have the Model in a Referenced Object Type, how did you solve this. It doesnt show anything, if i select it.

Kindd regards

Frederic

[Astrid Steindorff]

Hi @Mohamed Hassan ,

This is great. Just two questions:

1. Could it be made possible to choose the option to display the macro vertically? Use case would be if you want to display just one Asset per Confluence page and want to show all info without scrolling horizontally (and thus be able to export all content to PDF).

2. Are there any plans to include Assets into Confluence Databases as well?

Kind Regards,

Astrid

[Anthony Pearson]

Great... but (sorry):

1: Would like to display vertically

2: It forgets column config whenever you update the query, making it really tedious to use when updating 

3: There's a bug with the col config search box - doesn't work until you select/deselect a col

[Yaswanth Vannam]

Great feature, I appreciate this.

Do we have any sorting option or filter by option after the macro is inserted?

[Arnar Símonarson]

It is very unfortunate not being able to vertically display all attributes of a single object. Having to scroll sideways is terrible if you have a lot of attributes (and also no single button to select all attributes!).

[Marko Blagus]

Hello @Mohamed Hassan

But it's still not possible to display Asset fields data in Jira issue macro?

Best regards,

Marko Blagus

[Anna Kurpiela]

It would be helpful to display all table data at once, without requiring scrolling. Not everyone realizes there are more results in the list. Adding filtering, sorting, and search functionalities would also greatly enhance the experience.

[Fong_ Tsie-Ken]

Really happy with this feature, but when will de non-Jira Service Management users be able to view assets within Confluence?

Regards,

Tsie-Ken

[David Kretz]

Thanks for this but it is still not up to the original macros functionality.  People migrating from server need to understand that it does not function at all like the original insight macro.  Please update your description above to ensure those about to migrate know the difference in how their existing server confluence will react. 

The original server macro provided a more lean approach to display.  In our case we need to show one element from multiple schemas on a given client page.  The current design sticks the "Powered by JSM ..."  at the bottom of every single macro on the page.  It is creating a massive visual blot on pages we migrated from server.  In the case of a single element could we default a vertical list without the list footer visible.  Just like a single issue link reacts.  Also the label of the asset should be a clickable target tot he asset in JSM.  Otherwise we need to always display the key.

[Leo von Wyss]

This is really a cool feature. I'd also like to see the option to just show one asset in a vertical way. Actually, being able to simple insert a link to an asset and have it display as a smart link card would be awesome.

Also, It would be very nice to be able to publish the graph of one asset in a Confluence page, very much like to view we get we an asset is referenced from a Jira issue.

[Julia R_]

The Assets macro is quite promising but, at this point, lacking practical functionality.

The ability to present multiple macros in Confluence is ideal. However, as @Anthony Pearson mentioned 3 months ago, "It forgets column config whenever you update the query, making it really tedious to use when updating". 

And, although I agree with Jimi Wickman's assessment that exporting should only be allowed from the schema itself, we are between a 'rock and a hard place' with self-serve-reporting. Our current options are:

1. Fumble with the Confluence macro, re-applying column configs with each edit (pass)
2. Struggle through the native reporting within the schema which, as of today, is still not functioning (another pass)
3. Export the entire list from the schema to Excel, ultimately updating a PivotTable (this will have to do for now and can quickly be achieved by myself, but definitely not for Management's self-service)

Another issue I see is that the AQL varies in syntax between the filtering within the schema and the Confluence macro. In fact, they are opposites:

• Schema AQL:  "Shared_Device" = YES AND "Hardware_Designation" = Faculty AND "Warranty_Expiration_Date" > "01/01/2024"
• Confluence Macro:  ObjectSchema = "Assets" and objectType = "TSS Devices" AND Shared_Device = "YES" AND Hardware_Designation = "Faculty" AND Warranty_Expiration_Date > 01/01/2024

[Mohamed Hassan]

Hello Team 👋

Thanks all for the feedback provided on this post, it's really very valuable to us, and apologies for the delay in response. I would like to take this further and discuss the feedback in details, this will help us shape our future roadmap. Please use this link time to book some time with myself.

Also, please feel free to email me at mhassan@atlassian.com if none of the available times are suitable for your time zone.

Thanks,
Mohamed Hassan | JSM Assets Product Manager