---
language: "en"
---
# CMP Asset Picker Integrations

## CMP Asset Picker Integrations

Knowledge Base Articles CMP Asset Picker IntegrationsApr 23, 2025 • contributed by @User Storyteq CMP Asset PickerApr 02, 2025 • contributed by @User Storyteq C...

### Documentation

*

  #### [Storyteq CMP Asset Picker](https://cmp-integrations.storyteq.com/capi/storyteq-cmp-asset-picker.md)

*

  #### [Storyteq CMP Asset Picker for Jira](https://cmp-integrations.storyteq.com/capi/storyteq-cmp-asset-picker-for-jira.md)

---
language: "en"
---
# Storyteq CMP Asset Picker

## Introduction

A new Storyteq CMP Asset Picker component has been created to enable users of integrated internal or external applications to access assets contained within CMP.

## Asset Picker Functionality

The Asset Picker is designed as follows:  
![image-20250306-181336.png](https://cmp-integrations.storyteq.com/__attachments/a_947bb56c13978310f8c695fe4d08daf7cca31599786d836b78795d97026b1671/image-20250306-181336.png?cb=9aa8f033a49413bea065a42ae46b7974)  

|         **Section**         |                                                              **Purpose**                                                               |
|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
| **Filter Panel**            | Users can filter assets on Luma keywords and by created date                                                                           |
| **Search**                  | Users can search assets using Luma keywords                                                                                            |
| **Sort**                    | Users can sort assets by name, date created and type. They can also filter by domain.                                                  |
| **Asset Information Panel** | When an asset has been selected in the Asset Picker, an asset information panel opens displaying further information about that asset. |

### Internal Storyteq Integrations

The collection of assets that can be seen in an internal Asset Picker integrations (e.g. CA, Deployteq) will be defined using pre-existing functionality in Luma known as a Lens. Lenses are set up in Luma Admin by users with correct privileges.

**Luma Admin**

The person responsible for creating the Lens in Luma will need to do the following:

* Ensure that the Lens contains assets acceptable for their purpose (e.g. if the Asset Picker will be connected to an image field, the Lens should contain only images)

* Make note of the following details from Luma:

  * API Key

  * Lens ID

#### **Asset Validity**

Several of the integrations that have been built for the Asset Picker use URLs to reference assets rather than storing a copy of the asset on their system.

Currently, we are using the Luma Signed URL for each asset. This has a validity period of 7 days. If the system attempts to retrieve an asset with an invalid signed URL, the asset will not display to the user. An error message will be shown to the user explaining that the selected asset is no longer available. The user must reopen the asset picker and reselect the original asset, or select a new asset to use.

Rather than increase the validity period of the signed URL, we have agreed to utilise existing Public URL functionality within Luma. This change is in progress and will be released in the near future (correct as of February 2025).

### External Integrations

The collection of assets that will be seen in an external Asset Picker integration (e.g. Figma, Jira) will be determined by the user's CMP account.

The user will be able to open the CMP Asset Picker directly from the third party application, and they will log in using the required tenant URL and their CMP credentials (username and password). If the credentials are correct, the Asset Picker will then display the assets the user is authorised to see in CMP.

A change will be made in the future to introduce PKCE authentication - the user will be required to enter the desired tenant URL, after which they will be taken to a new tab, where they will be presented with a CMP login page. Once successfully logged in, they will be redirected back to the Asset Picker window where they will see the assets they are authorised to see in CMP.

If a user has access to multiple domains within their CMP account, they will be able to switch between these in the Asset Picker using the Domain Switcher function.

Once one or more assets have been selected, the Asset Picker window will close, and the selected asset(s) will be available to use within the third party application.

---
language: "en"
---
# Storyteq CMP Asset Picker for Jira

## Purpose

Jira is a software product developed by Atlassian that allows bug tracking, issue tracking and agile project management. Once integrated, the CMP Asset Picker will allow Jira users to select assets from CMP (Luma) to use within their tickets.

### Setup - Internal ITG Users

#### Prerequisites

Admin access to Jira

#### Steps for Installation

1. **Log in to Jira**

   * Ensure you have admin privileges.

2. **Get Install link from CMP Asset Picker team**

3. **Follow instructions on screen**

#### Plugin Access and Location for Internal Users

You can find the CMP Asset Picker plugin in the actions toolbar in any Jira issue panel.

See screen shot below:  
![image-20250224-093649.png](https://cmp-integrations.storyteq.com/__attachments/a_278a24e99e312d4ac76cdc874d2f92791fab407d85c0afdd2d04b95bcf5144f9/image-20250224-093649.png?cb=4e62ef9f918f742af662cb2bfaea1727)

#### **Notify Internal Users**

* Inform teams about the new plugin and provide any necessary documentation

## External Installation

### Prerequisites

* Jira Administrator access

* Jira Cloud or Data Center instance

* Access to the Atlassian Marketplace

### Steps for Installation

1. **Log in to Jira**

   * Use an account with admin privileges.

2. **Go to Atlassian Marketplace**

   * Open **Jira Administration** \> **Manage Apps**.

   * Click on **Find new apps** and search for the plugin.

3. **Install the Plugin**

   * Click **Install** and accept the necessary permissions.

   * Wait for Jira to complete the installation.

### Plugin Usage Guide

When the Asset Picker window opens, you need to login using you CMP credentials (username and password), along with your tenant URL.

When logged in successfully, you will be presented with your domain-specific asset library, complete with filtering capabilities and asset selection functionality.

The selected assets automatically integrate into the Jira issue attachments upon completion, and the plugin preserves both user authentication and filter preferences between sessions, eliminating the need for repeated authentication.

### How to Use

**Prerequisite:** A Jira admin user has installed the CMP Asset Picker plugin in the required Jira workspace

* Create a Jira ticket as normal

* Click on the ... menu in the right-hand corner

* Select the "CMP Asset Picker" option from the menu:

![image-20250224-093649.png](https://cmp-integrations.storyteq.com/__attachments/a_278a24e99e312d4ac76cdc874d2f92791fab407d85c0afdd2d04b95bcf5144f9/image-20250224-093649.png?cb=4e62ef9f918f742af662cb2bfaea1727)

* You will see an Asset Picker login screen window open, overlaying Jira:

![image-20250326-153036.png](https://cmp-integrations.storyteq.com/__attachments/a_5aece8a116b8948bbcb836411b38d5474fb2cf8b08a307f901d6f970ed5a305f/image-20250326-153036.png?cb=5ee941c34e2bbe8ca33b25614bf83054)

* Log in using your CMP credentials and desired tenant

<!-- -->

* The Asset Picker will display your CMP assets to you

<!-- -->

* You can filter/search through assets as required

<!-- -->

* You can select/deselect assets as required -- in Jira, multiple assets can be selected at any one time

<!-- -->

* Click the "**Add to Project"** CTA

<!-- -->

* If derivatives are available, an additional menu will appear allowing you to select required derivative(s)

<!-- -->

* If this menu appears, select the required derivatives and confirm your choice

<!-- -->

* The Asset Picker window will then close

<!-- -->

* You will see that the chosen asset(s) are displayed within the Jira ticket, and have also been attached to the ticket itself

<!-- -->

* If any errors occur during attachment, the Asset Picker window will remain open and display relevant errors to you

### Known Issues and Troubleshooting

When using the CMP Asset Picker plugin, there are some common issues you may encounter. Understanding these issues and their solutions will help ensure a smoother experience with the plugin.

#### ++**Attachments not loading after Asset Picker window closes**++

Once the assets have been successfully added to the Jira ticket and the Asset Picker window has closed, Jira is still processing and creating the preview image for the attachment behind the scenes. This can sometimes take a minute depending on the amount and size of the images and in some cases requires a page refresh before seeing the attachments with proper preview image on the ticket.

#### ++**"Too Many Requests" Error**++

You may occasionally see a message indicating "too many requests" (also known as a 429 error). This happens when there are too many requests to our service in a short period. If this is encountered, waiting a few moments and trying the action again should work. The issue typically resolves itself within a few minutes.

#### ++**Authentication Problems**++

Sometimes you may have trouble logging in or staying logged in to the plugin. This can happen if the login details are incorrect or if the login session has expired. In this situation, you should double-check that you are using the correct tenant URL (excluding 'https://') and that your email and password are correct for that specific tenant. If you suddenly get logged out while using the plugin, you should try logging in again. This usually resolves any authentication-related issues.

#### ++**Missing Derivatives**++

Sometimes when selecting an asset, no derivatives (different versions or formats of the asset) are available. This usually means either you don't have the right permissions to access these derivatives, or that no derivatives have been set up for that particular asset. On encountering this issue, you should ensure they have the correct permissions for your account. You should also verify your access levels and make sure the assets are properly configured with the derivatives you need.

