Frequently Asked Questions

Why do I see an error instead of data?

The most common cause is that the page viewer lacks read permissions on the Jira Assets object schema. Even if the page editor configured everything correctly, viewers still need at least read-only access to the relevant Assets schema. Ask your Jira admin to grant the appropriate permissions.

Can I use multiple filters on one page?

Yes. You can add as many filter macros as you need to a single Confluence page. Different macros can reference different filters. Filters can also reference each other using {Filter Name} syntax in advanced mode .

Why can’t I switch back from advanced mode to basic mode?

This is by design. Advanced mode gives you full control over the AQL query, and converting raw AQL back to individual rules is not always possible. If you need to start over, use the “Reset configuration” option on the Basic tab to clear everything and begin with an empty configuration.

Why are some images not showing?

The Image macro only loads images from a specific set of allowed domains . If your image URL points to a domain not on the list, it won’t render. Check that your image URLs use one of the supported domains (Atlassian CDN, Gravatar, Unsplash, or your Confluence instance domain).

The number of items in the object selection dropdown is controlled by an admin setting. Go to Confluence Settings > Apps > Beautiful Assets and adjust the Maximum Dropdown Items value. See Admin Settings for details.

Does the data update automatically?

Yes. Data is fetched live from Jira Assets every time the Confluence page loads. There is no caching between page views, so changes made in Jira Assets are reflected immediately on the next page load.

Can viewers change the filter configuration?

No. Filter and macro configurations can only be changed by editing the Confluence page. Viewers can only interact with the object selection dropdown (if enabled) and cannot modify filter rules or AQL queries.

How many macros can I put on one page?

There is no hard limit, but performance may degrade with a large number of macros, especially if each one triggers separate API calls. For best performance, keep the number of filters reasonable and reuse filters across multiple display macros.

Does Beautiful Assets send my data to external servers?

No. All data stays within the Atlassian platform. The app reads from Jira Assets using Atlassian’s internal APIs and stores settings in Forge’s built-in storage. No data is sent to third-party servers, and there is no analytics or telemetry. See Security & Data Privacy for full details.

Is my asset data safe when using this app?

Yes. The app accesses Jira Assets data as the current user, so it respects your existing Jira Assets permission schemes. Users can only see data they already have permission to view. See Security & Data Privacy for more information.

Can I use the same filter for multiple macros?

Yes, and this is recommended. Multiple display macros (Text, Phone, Email, Image, Hyperlink) can all reference the same filter. This is more efficient than creating separate filters with identical queries, and ensures all macros stay in sync when an object is selected.

Can I display data from multiple object types on one page?

Yes. Create a separate filter for each object type. For example, one filter for “Employee” and another for “Department”. Each display macro references whichever filter provides the data it needs.

What happens if the Jira Assets schema changes?

If an attribute is renamed or removed in Jira Assets, macros referencing that attribute will stop showing data for it. You’ll need to edit the page and update the affected macro configurations to use the new attribute name. Filter rules referencing removed fields may also need updating.

Can I export the data shown by Beautiful Assets?

Beautiful Assets displays data directly from Jira Assets and does not provide its own export functionality. To export asset data, use Jira Assets’ built-in export features.

For more specific issues, see Troubleshooting .