Turn your Jira project into a visual asset gallery. Browse issues as image cards, filter by any field, and manage thumbnails — all without leaving Jira.
Asset Vault is a Jira Cloud app that replaces the standard issue list with a visual, card-based gallery. Each issue is represented by its attached image, making it easy to browse, identify and manage visual assets at a glance.
It is built for teams that store visual content — characters, props, environments, screenshots, design assets, or any other attachments — as Jira issues. Instead of scanning rows in a table, your team gets a rich, filterable gallery view directly inside your Jira project.
Asset Vault runs entirely on Atlassian's Forge platform. There are no external servers, no third-party services, and no data leaves the Atlassian infrastructure.
Manage characters, props, environments and screenshots tracked as Jira tickets.
Browse design assets, artwork and deliverables stored as issue attachments.
Visualise production assets, storyboards and reference images across your project.
View UI screenshots, component previews and design mockups alongside issue metadata.
If your team stores images in Jira issues, Asset Vault gives them a home.
Browse issues as image cards instead of rows. Each card shows the issue thumbnail, key, title and your selected fields.
Create separate gallery views with individual JQL queries, field sets and display settings. Switch between views with a tab bar.
Search by issue name and filter by any displayed field — including status, assignee, custom fields and multi-user fields.
Color-code cards using JQL conditions. Define rules with a color and optional label — the first matching rule applies.
Click any card image to view it at full resolution in a lightbox overlay. Full-res image loads automatically in the background.
When an issue has multiple images, authorised users can choose which one represents the card in the gallery.
Restrict thumbnail editing to specific Jira project roles. Configure per view which roles are allowed to make changes.
Optionally show downloadable non-image attachments (zip, 7z, etc.) directly on each card. Can be toggled per view.
Issue data is cached (configurable TTL, default 1 hour). Cache age is shown in the toolbar and can be refreshed on demand.
Use a saved Jira filter as the data source for a view instead of writing JQL manually.
Results are paginated with a configurable page size. Thumbnails load only for the current page to keep performance fast.
Set card aspect ratio, minimum card width, thumbnail dimensions and which fields appear on each card.
Install the app from the Atlassian Marketplace onto your Jira Cloud site. No additional setup is required at the site level.
Navigate to your Jira project, then open Project Settings → Asset Vault. Only project admins can access settings.
Enable Asset Vault for the project and configure at least one view. Set a name, choose a JQL query or saved filter, and select the fields you want displayed on each card.
Go to Project → Asset Vault in the project sidebar. Your issues will appear as image cards, ready to browse and filter.
Each view is a separate gallery tab with its own query, fields and display settings. You can create as many views as needed — for example, one for characters, one for environments and one for UI assets.
Each view can be driven by a JQL query or a saved Jira filter. When using JQL, the query is automatically scoped to the current project — you only need to provide the filtering part, for example: issuetype = Character AND status != Done ORDER BY created DESC.
Select which Jira fields appear on each card. Both system fields (status, assignee, priority, labels) and custom fields are supported, including user picker fields. You can set a custom label per field and mark fields as filterable to expose a dropdown in the gallery toolbar.
Highlight rules let you color-code cards based on JQL conditions. Each rule has a JQL query, a color and an optional label displayed as a banner on the card. Rules are evaluated in order — the first matching rule wins.
When an issue has multiple image attachments, the gallery picks the first one by default. Users with the right role can click the gear icon on a card to pick a different image. Permitted roles are configured per view under the Portrait Editors setting.
Non-image attachments such as zip and 7z files can optionally be shown as download links on each card. This can be toggled on or off per view.
| Setting | Description |
|---|---|
| Card aspect ratio | Controls the height-to-width ratio of the thumbnail area. Default is 3:4 (portrait). |
| Card min width | Minimum width for each card in the grid. Smaller values show more cards per row. |
| Thumbnail dimensions | Width and height used when fetching thumbnails from Jira. Higher values give sharper images but increase load time. |
| Page size | Number of cards displayed per page. Thumbnails only load for the current page. |
| Show issue key | Toggle the issue key link on each card. |
| Show thumbnails | Toggle image thumbnails on or off entirely. |
| Show archives | Toggle downloadable file links on or off. |
| Cache TTL | How long issue data is cached (in minutes). Use 0 to disable caching. Max is 7 days. |
| Permission | Purpose |
|---|---|
read:jira-work |
Read issues, fields, attachments, project roles and saved filters to populate the gallery. The app acts on behalf of the logged-in user and can only access data that user already has permission to see. |
storage:app |
Store thumbnail selections and issue cache within Atlassian's own secure Forge KVS storage. No data is written to Jira itself or stored outside the Atlassian platform. |
Yes. Asset Vault works with both project types on Jira Cloud.
The card will still appear in the gallery with a placeholder instead of a thumbnail. All fields, filters and highlights work regardless of whether images are present.
Yes. Each Jira project has its own independent configuration including views, fields, highlight rules and permissions.
Only Jira project admins can access Project Settings → Asset Vault. Thumbnail editing in the gallery is controlled separately by the Portrait Editors role configuration per view.
Issue data is cached in Forge KVS for the configured TTL (default 1 hour). The cache age is shown in the gallery toolbar next to the issue count. The Refresh button forces a full reload from Jira at any time. Changing the JQL or filter for a view automatically invalidates its cache.
The app fetches all issues matching your JQL query. For very large result sets, pagination keeps the gallery fast by loading thumbnails only for the current page.
For questions, bug reports or feature requests, please contact us at [email protected].
Please include your Jira site URL and a description of the issue or request. We aim to respond within a few business days.