Now in open beta: Surface your Assets objects in Confluence Cloud!

[#1]

Hello Atlassian Community,

The ability to surface objects from Jira Service Management Assets in Confluence is now available in open beta! After a successful early access program, we're now ready to roll this out to a broader audience.

This means all the Assets data you want can be shared and viewed directly from within a Confluence table - making your workflows more efficient and getting information to the people who need it, when they need it.

To use this feature, you must be a Jira admin and / or have permissions to see the relevant object schema in Assets in Jira Service Management as well as an active Confluence licence in order to see the schema and manage this macro in Confluence.

To embed a table with Assets objects:

1. Navigate to a Confluence page you own.

2. Enter / on your keyboard.

3. Search for Assets (Beta) in the dropdown menu search bar, then select Assets (Beta).

4. Select Insert objects from.

5. Choose the object schema that stores the objects you want to display.

6. Enter an AQL query to filter down the objects you want to be displayed. Learn more about AQL queries.

7. Select Insert objects.

Learn more about displaying Assets in Confluence

We're super excited to bring this feature to you - but we also need your help to make it even better. Please try out the open beta and let us know your thoughts, feedback, or any issues you may encounter. Your input is invaluable to us in refining and enhancing this feature.

Please note that to insert and view the table, you must have a Jira Service Management Premium or Enterprise license. While insert and edit capabilities will remain limited to Jira Service Management users, we’ll be opening up table display to non-Jira Service Management users in a future release.

We’ll begin rolling out the changes from the week commencing 15 January 2024. Because we are releasing this update incrementally, you might not see changes in your experience right away, but we’re expecting to have this update completely rolled out by February.

Our goal is to make your experience with Atlassian products as seamless and productive as possible, and we believe this feature is a significant step in that direction.

Give it a whirl and let us know what you think! We're looking forward to hearing from you.

All the best,

The Jira Service Management Assets team

[Tomislav Tobijas]

Tested the feature in EAP and we're super excited for this! Hoping that

...While insert and edit capabilities will remain limited to Jira Service Management users, we’ll be opening up table display to non-Jira Service Management users in a future release...

will be released soon 😄

[Chris Aldridge]

Thank you @Mohamed Hassan this is fantastic news! 

I have a couple of questions if I may:

- regarding the deployment, is there a logic as to the order of environments this is applied to? (I can now find this macro in our confluence sandbox but not in our prod instance yet.)

- Do you have an ETA as to making the contents visible to users independantly of JSM license?

- As additional features, are there any plans to make this Assets view: 

    - Searchable?

    - Sortable?

    - Filterable?

    - Exportable?

Many thanks for this it is already a super useful tool we've all been longing for!

[Mohamed Hassan]

Hey @Chris Aldridge - Nothing you should do, we are at 100% today so unless you are a release track customer you should be able to see it.

For the Non-JSM license display it's currently in progress, we are aiming to release it in the next quarter to but I don't have a confirmed ETA yet  🤞

I would like to know more information about the additional features, do you mind if I reach out by email (or feel free to email me mhassan@atlassian.com)

Thanks,

Mohamed

[Matt Lane]

Excellent, thanks Mohamed and team!

Just gave it a test and so good so far :-)

[Rune Rasmussen]

We're playing around with the Assets in our Sandbox, and whenever we try to use the /assets macro we just get a big fat message about not having access to this content, and that we should contact our Site admin.

I feel like I talk to myself enough, so I won't do that (I already am site admin).

On that note, wasn't the term "Site admin" retired a while ago, and is now just the Organization admin?
But I digress...

Does the beta feature not work with sandboxes, or do we need to enable something for this to work?

[Carl Belinger]

Glad to see this implemented.  Working well here.

@Mohamed Hassan - Question for you sir. The instructions say to use the / function.  Does this only work using the new page editor?  when modifying pages that were migrated to cloud recently, the / function does not work.  However when we convert the pages to the new editor it does.

Just wanted to confirm that we would have to convert pages to the new editor before we use this.

Thanks in advance

Carl.

[Benjamin Daugherty]

We are testing Assets in Jira and saw this new feature, so we created a page linking to our test assets.  It worked fine for those of us that are Jira Service Management Team members.  However, we want to present a list of approved software to our end users to use as a reference.  When we allow the page to be "public" they do not have access.

Can this be changed for informational purposes only, we don't need those users to add or edit.

[Ivan]

I'm very glad to see this feature being worked on.  It's certainly something we have missed since migrating to cloud.

In addition to the features suggested by Chris above, I would love to see:

1. the ability to resize the table,
2. specify the number of rows and columns to show with an option to show everything,
3. and for the ability to export the full table to Excel,
4. and export the page with all rows to PDF.

Thanks,

Ivan

[Ralf Scheller]

Hello, I have two questions about this feature.

• which Permissions are neede to use this feature? Can any Confluence user user it or do the user need to have certain permissions in Assets?
• is there a possibility to export the table to csv or prf?

Thanks

Ralf

[Hielko Manders]

Hi All,

Even though I am admin in both Jira and Confluence and I am the the Object Schema Manager/Developer/User  I get an error message when trying to use the macro in confluence.

Any ideas?

Thanks,

Hielko

[Rune Rasmussen]

@Hielko Manders I got that same error message, despite being admin of everything and having every permission under the sun.
It sort of just solved itself a day or two later.

[Hielko Manders]

Hi Rune,

Thanks for the update, was kind of expected as they are rolling it out.

Regards,

Hielko

[fastcoder]

In addition to a confluence page showing a table with a list of assets and links to actual assets, Can a single confluence page pull in ONLY ONE asset detail? The confluence page should have ALL the details of an asset object? Is this possible?

Also when an asset gets created for the first time, can a new confluence page be created automatically? if so where should the automation be created?

Thanks a lot.

[Mohamed Hassan]

Hello Team - Apologies for missing all your comments, for some reasons I get only notifications about article likes in my inbox (that doesn't require responding  😊)

@Carl Belinger - I am not super familiar with migrated Confluence pages but this feature is indeed developed on top of the editor component so I guess it's fair assumption that it'll require an upgrade before being able to use it.

@Benjamin Daugherty - we are working on this at the moment, we will create a new viewer role in the schema config where you can add any user in your site with an Atlassian Account regardless of their JSM license.

@Ivan - thanks for providing this list, I'll add it to the post GA backlog.

@Ralf Scheller - at the moment only JSM license can insert and view the information. In the near future, we will allow non-JSM license users to view the information but inserting will be limited to JSM licensed users. At all times we respect Assets permissions when it comes to schema and object views. We have the the ability to export the table on our post GA list.

@Rune Rasmussen / @Hielko Manders - Apologies for the inconvenience, glad that it got resolved, we haven't experienced this issue on non sandbox environments so I guess it's not related to assets, if you are still experiencing the issue please log a support ticket and email it me at mhassan@atlassian.com so I can follow up with the team.

@fastcoder - For the single object display - we have heard this feedback from many and we are prioritising it after GA release. I am not sure about the confluence automation but at the moment unfortunately we don't have the capability that resolves a URL to a confluence table similar to Jira Issues Macro where you can paste a filter URL and it resolves to a table, once we enable this capability to the Assets app this might unlock some automation options, I'll keep this on my list to follow up once we have the URL capability.

[Johannes Nyberg]

Hi! 

This feature is great. Looking forward to when it is released properly. Two questions 

1. When do you think this will be possible to be viewed on the confluence iOS App? When I try on a page I published on my computer I get "Unsupported: blockCard" on my iPhone.

2. Would also be nice to include graphs for visualisation of the data. Is that possible? 

Thank you! 

Johannes 

[Mohamed Hassan]

Hey Team!

Big news! 😊 We're very close to starting the roll out of the new view-only role that will enable the display of Assets information for Atlassian accounts without a JSM license and we’re looking for a select group of customers to have early access to the new feature, this is expected to happen around mid-April!

If anyone is Interested, please shoot me an email at mhassan@atlassian.com with the site details and we will include you in the early access.

Cheers,

Mohamed Hassan 

[Cian Mackle]

@Mohamed Hassan Excited about the view-only role for displaying assets! Can you confirm if displaying assets for Confluence-only users or JSM customers in KB articles, for example, is in scope for this, or will some sort of Jira license be required?

[Mohamed Hassan]

Hi @Cian Mackle - It's going to be be accessible to all holders of an Atlassian Account, regardless of their product license. Once an Atlassian Account is established, these users can be integrated into your schema permissions alongside other roles. Specifically, users of Confluence and Jira can be added since they already have an Atlassian Account and can view the information in Confluence or KB Articles, however it is not going to be available for JSM customers (portal only users). With that said, we are planning to extend this feature to JSM customers in a future update. In the meantime, JSM users can gain access by transitioning to an Atlassian Account, if suitable. For more information on the various account types, please refer to the following pages:

What are service project customers and organizations? 
Migrate a portal-only customer to Atlassian account 

Thanks,

Mohamed

[Guillaume Huard]

Thanks for the update Mohamed, when this is fully released ( non JSM license being able to view Objects ) will there be an announcement or will it be detailed in the cloud release log ?

We had to revert to classic db for our confluence articles linking to Assets, waiting patiently for the roll out :)

[Mohamed Hassan]

Hi @Guillaume Huard - Can you please email me at mhassan@atlassian.com

Thanks,

Mohamed