/
Attachments Transfer: Configuration

Attachments Transfer: Configuration

Owned by Gia Jgarkava
Last updated: Feb 19, 2025
6 min read

Configuration

To send the attachments to another instance, the app should be initially configured to access the attachments on the source instance and to enable the target instance to receive the attachments.

Configuration of connection with source instance

To configure a connection with the source instance, go to Settings / Configuration and fill in the following fields:

  1. Email

    1. This user should have a valid JSM agent License and have permission to access the Projects from where the attachments should be transferred.

  2. Atlassian API Token

    1. You can create a Token through the following link.

image-20250130-210005.png

After entering the valid credentials, you will see the connection status:

image-20250130-210359.png

If the connection is not successful, you will see the corresponding notification:

You can further edit or delete the connection by clicking the “Edit configuration“ button:

API Token

To secure the attachments transfer from the source to the target cloud instance, you need to create an API token. To do so, go to the API Tokens section in the left sidebar and click the “Create new API token“ button:

You will need to add a name to the token in a popup:

After clicking the “Create“ button, you can view and copy the token:

The added tokens will be visible in the grid for further use:

You can revoke the tokens individually, by clicking the “Revoke“ button along the token row, or all together by clicking the “Revoke all API tokens“ button. In both cases, the confirmation popup will follow:

URL Endpoint

As a final step, after the connection is successful, and API token is created, you can create a URL endpoint for your target instance. To do so, go to the URL endpoints in the left sidebar and click the “Add new endpoint” button. You can send the attachment to another cloud instance and on Data Center instance.

Configuration for Target Cloud

When you click the “Add new endpoint” button you will need to fill in the following fields:

  1. Name

    1. Give a name to the URL endpoint to further identify it more easily.

  2. Description

    1. Describe what this endpoint is for.

  3. Target instance type

    1. Select “Cloud”.

  4. Target instance URL

    1. URL of the target instance to which the attachment will be transferred. the format for the cloud instance should be: yourcompany.atlassian.net.

  5. Email

    1. This user should have a valid JSM agent License on the target instance and have appropriate permission to projects where the attachments will be sent.

  6. Atlassian API token

    1. API token of the user (email) above You can create a Token through the following link.

After entering the required information, the URL endpoint will be created. You can further view, edit, and delete the URL endpoints by clicking the “Edit“ button along the URL endpoint row in the grid:

You can sort the URL Endpoints alphabetically ascending or descending by clicking any of the three headers (Name, Target instance URL or Instance type).

After the URL Endpoint is added, you can click the endpoint name or the Edit button and further modify the endpoint credentials or copy the URL endpoint:

You cannot change the instance type. When you modify the URL endpoint, the endpoint address remains unchanged.

You will also see the connection status of the endpoint above the endpoint fields:

If you see the “CONNECTION FAILED” message, please recheck the credentials, make sure that Athe Atlassian API token is not expired, regenerate the Atlassian API token (if needed) and click the Refresh status.

When the URL endpoint for the target cloud instance is generated, you can further regenerate the endpoint by clicking the “Regenerate“ button and licking Regenarate in the confirmation popup:

By regenerating the URL endpoint, the old endpoint will become inaccessible. Any existing integrations and automation using the previous endpoint will stop working. Please update the Endpoint URL where they are used.

With this, the configuration is completed and you can use the URL endpoint and the API token to configure Jira automation. Go to the Attachment in a New Tab: User Guide for the instructions.

Configuration for Target Data Center

To add a target Data Center Endpoint, click the “Add new endpoint” button you will need to fill in the following fields:

  1. Name

    1. Give a name to the URL endpoint to further identify it more easily.

  2. Target instance type

    1. Select “Data Center“.

  3. Target instance Base URL

    1. For transferring the attachments, the target Data Center should be accessible from internet!

  4. Atlassian PAT

    1. For the instructions of creating and managing Personal access tokens (PATs) see the following link.

After entering the required information, the URL endpoint will be created. You can further view, edit, and delete the URL endpoints by clicking the “Edit“ button along the URL endpoint row in the grid:

After the URL Endpoint is added, you can click the endpoint name or the Edit button and further modify the endpoint credentials or copy the URL endpoint:

You cannot change the instance type. When you modify the URL endpoint, the endpoint address remains unchanged.

When the URL endpoint for the target cloud instance is generated, you can further regenerate the endpoint by clicking the “Regenerate“ button and licking Regenarate in the confirmation popup:

With this, the configuration is completed and you can use the URL endpoint and the API token to configure Jira automation. Go to the Attachment in a New Tab: User Guide for the instructions.