# Overview

**Atlassian Cloud Apps**

{% content-ref url="/pages/PQbMVoTt30ziBUIz4Mu0" %}
[Asana Integration for Confluence](/atlassian-cloud/asana-integration-for-confluence)
{% endcontent-ref %}


# Asana Integration for Confluence


# Administrator Guide


# Configure Connection Types

Asana for Confluence provide two types of connection:

* Each user login with their own Asana account
* Centralised Asana account

In order to configure connection types, click **Configure** on the **Manage apps** page.

<figure><img src="/files/MKOofpiUi4Bnc3GwwrMx" alt=""><figcaption></figcaption></figure>

### Each user login with their own Asana account

In the **Configure** Page, select the first option for each Confluence user to login with their own account.

<figure><img src="/files/b1QmZqbjMkw8NQXsiffG" alt=""><figcaption></figcaption></figure>

### Centralised Asana account

To configure a centralised service account, login by clicking **Setup Asana Connection with a Service Account**.

<figure><img src="/files/G6sSoFGfYqr0tK1irA4l" alt=""><figcaption></figcaption></figure>

A new window will pop up. Enter your login details and proceed to Allow permission.

<div align="left"><figure><img src="/files/SpgeYAoZA0U93lD4Ayth" alt="" width="375"><figcaption></figcaption></figure></div>

Select the second option after you are authenticated.

<figure><img src="/files/93GAA92KoC8FPAoZ5uKG" alt=""><figcaption></figcaption></figure>

### Manage Connection Permissions

You can limit users that can access the centralised connection.

Please take a look at [Configure Connection Permissions](/atlassian-cloud/asana-integration-for-confluence/administrator-guide/configure-connection-permissions).


# Configure Connection Permissions

By default, all Confluence users can see macros. However, administrators can restrict access to specific groups by enabling the "**Limit User Groups that can access this connection**" option and configuring authorized Confluence groups to view Asana Macros.

**Step-by-Step Guide**

Go to **Manage apps > Asana Integration for Confluence**,  click **Configure.**

In the **Configure** Page, toggle **Limit User Groups that can access this connection**

<figure><img src="/files/fUnrWjp9bQLcrduHwqbe" alt=""><figcaption></figcaption></figure>

Click on **Limit User Groups** to add Confluence group.

Search desired group from the **Groups** dropdown menu.&#x20;

Click **Add Group** to add the group to the authorized access list.

<figure><img src="/files/hsQKVRvSgCBekNUB2VMk" alt=""><figcaption></figcaption></figure>

Click **Save** to apply the changes.


# Enable Edit Mode for Task Modifications

Edit mode is automatically enabled for individual user logins

<figure><img src="/files/mLvUYI0abiym97BNqIkR" alt=""><figcaption></figcaption></figure>

To activate this feature for centralised service account logins, please toggle the corresponding button.

<figure><img src="/files/TrAYCZVMmvDjjQ6cQMBO" alt=""><figcaption></figcaption></figure>


# User Guide


# Connecting Asana account

### User defined Connection

Before you can integrate Asana to Confluence, you need to connect your Asana account.

Go to Edit page and type **/asana**.

<div align="left"><figure><img src="/files/gI6UsdSUAVLh2Je2lVhT" alt="" width="375"><figcaption></figcaption></figure></div>

Select **Asana Task Link**. Click on **Connect your Asana account**.

<div align="left"><figure><img src="/files/ko9OAWZ71K70rOzo8dyx" alt=""><figcaption></figcaption></figure></div>

Enter your Asana credentials.

<div align="left"><figure><img src="/files/YFL2VvvQ4fMyFzwGBNsj" alt="" width="375"><figcaption></figcaption></figure></div>

Click on Allow when Granting Permission.

You are now authenticated and ready to use the macro.

### Centralised Connection

Alternatively, instead of logging in using your own Asana account, you can also ask your Admin to setup a centralised account. Please check [Configure Connection Types](/atlassian-cloud/asana-integration-for-confluence/administrator-guide/configuring-connection-types).


# Asana Task Link Macro

To setup **Asana Task Link** macro, go to your desired task in Asana.

Click on the task and copy the link.

<figure><img src="/files/nXzuBikNWvP5OTNlLn6d" alt=""><figcaption></figcaption></figure>

Paste the link in Confluence and it will be automatically converted to a macro.

<div align="left"><figure><img src="/files/nPnOaalQ6HmBkku7Zc8P" alt="" width="375"><figcaption></figcaption></figure></div>

You can also insert the macro manually by typing **/asana**.&#x20;

Select **Asana Task Link**.

<div align="left"><figure><img src="/files/iVIplnAxaaBFto1Jq6Jv" alt="" width="375"><figcaption></figcaption></figure></div>

Insert the copied url in the Asana Link text box and click Insert.

<div align="left"><figure><img src="/files/U3QQL8XZYfI3gsASwR86" alt=""><figcaption></figcaption></figure></div>


# Asana Task Card Macro

To setup **Asana Task Card** macro, go to your desired task in Asana.

Click on the task and copy the link.

<figure><img src="/files/C960fmlPvpfOiRrDM0Ob" alt=""><figcaption></figcaption></figure>

Go to edit page in Confluence. Type **/asana**.&#x20;

Then, select **Asana Task Card**.

<figure><img src="/files/kn3s4hkuBkZx5BiPPGtk" alt="" width="375"><figcaption></figcaption></figure>

​​​In the dialog, insert your copied url to the Asana Link textbox.​

<figure><img src="/files/JKnk8a11GmtPsgZYB5cv" alt=""><figcaption></figcaption></figure>

You can configure custom fields to be shown in the **Select Field** dropdown.

Click Add after selecting the field.​

<figure><img src="/files/GCbv5r0w7qodsMco0wOd" alt=""><figcaption></figcaption></figure>

Once you are done, click Insert to save the macro.

<figure><img src="/files/iUzS6BcpFnzH7ZFPwyA5" alt=""><figcaption></figcaption></figure>


# Asana Embedded Project

To setup **Asana Embedded Project** macro, type **/asana** in Edit Page in Confluence.

Select **Asana Embedded Project**.

<figure><img src="/files/q1xmYE0F0t2Tp1Gzq0KK" alt="" width="375"><figcaption></figcaption></figure>

In the Workspace list, select your desired Workspace.

<figure><img src="/files/74WmsG1RYoSuPuDAI78Z" alt=""><figcaption></figcaption></figure>

After selecting your Workspace, search Projects that you want to display.

<figure><img src="/files/TZ4tCogV3R1SHSYsmgOi" alt=""><figcaption></figcaption></figure>

### Displaying Project without sections

To show all tasks in the Project without showing sections, leave the Sections option empty.

<figure><img src="/files/MqCQvPvJx9L9aW2VrXaa" alt=""><figcaption></figcaption></figure>

You can configure fields to be displayed in the table.

<figure><img src="/files/JsF7h3ubv1sL9YQovcrb" alt=""><figcaption></figcaption></figure>

Click Add to add fields to table columns.

<figure><img src="/files/ZRThgAcs2ql8YJJIIzsP" alt=""><figcaption></figcaption></figure>

Click **Insert** to display the project macro.

<figure><img src="/files/42MBLDUjRYAHuFlx1oeR" alt=""><figcaption></figcaption></figure>

### Displaying Project with sections

To display project with sections, select your desired sections

<figure><img src="/files/MyzlogUCpYFAaLE2s7Cu" alt=""><figcaption></figcaption></figure>

Click **Save** to display the project macro.

<figure><img src="/files/ZF2QoDEF3hexcWg4TVzZ" alt=""><figcaption></figcaption></figure>


# Asana Embedded Tasks

To setup **Asana Embedded Tasks** macro, type **/asana** in Confluence Edit Page.

<figure><img src="/files/gpQEqZaQJxqWpON0kffr" alt=""><figcaption></figcaption></figure>

Select **Asana Embedded Tasks**.

In the Workspace list, select your desired Workspace.

<figure><img src="/files/i6GEbLr4LUUsNT9bwxhm" alt=""><figcaption></figcaption></figure>

After selecting your workspace, search for the Tag you want to filter tasks with.

<figure><img src="/files/cqTSTlku2UUIxpIjvfdL" alt=""><figcaption></figcaption></figure>

You can configure a list of fields to display in the table columns.&#x20;

Please take a look at this documentation [Fields in Asana Embedded Tasks](/atlassian-cloud/asana-integration-for-confluence/user-guide/asana-embedded-tasks/fields-in-asana-embedded-tasks).

<figure><img src="/files/xdTMWYQoo8Zjiblc6CUf" alt=""><figcaption></figcaption></figure>

Click **Insert** to display the project macro.

## Advanced Search

If you would like to filter asana tasks based on different criteria, please take a look at [Advanced Search](/atlassian-cloud/asana-integration-for-confluence/user-guide/asana-embedded-tasks/advanced-search)


# Advanced Search

{% hint style="info" %}
Please note this feature is only available for Asana Premium users.

A user is premium if any of the following is true:

* The workspace in which the search is being performed is a premium workspace
* The user is a member of a premium team inside the workspace
  {% endhint %}

To filter tasks in Asana based on different criteria, you can use the advanced search feature.&#x20;

To enable advanced search, select the corresponding checkbox.

<figure><img src="/files/wZGG7lkNnn8GAduhZmkg" alt=""><figcaption></figcaption></figure>

The advanced search filters will appear.&#x20;

Select and configure your preferred filters based on your needs.

<figure><img src="/files/TAnoJMRgz7armRISe0cn" alt=""><figcaption></figcaption></figure>

Once you have configured the filters, click on "Save" to save the macro.&#x20;

This will display results based on the configured filters.

<figure><img src="/files/7rQ0V1365eDVAeFmC8cQ" alt=""><figcaption></figcaption></figure>

Note: We will continue to enhance this feature by adding more filters over time to better serve your needs.


# Fields in Asana Embedded Tasks

You can configure custom fields to be displayed in the Asana Embedded Tasks table.

<figure><img src="/files/1RJdFZJp7FGZeOXm3JNI" alt=""><figcaption></figcaption></figure>

In order for custom fields to be displayed, please make sure the customfield is available to the Workspace.&#x20;

To do that, add your customfield to the field library.

<figure><img src="/files/qF40Di9izZQIGv59cJyI" alt=""><figcaption></figcaption></figure>


# Update your Asana Task directly in Confluence

### Modify Asana Task

To modify Asana Task, hover over the macro and click the Edit icon.

<figure><img src="/files/1zae4ef19QOJ79dDdIjH" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/nd1rQmU5bqNHgF4HF0It" alt=""><figcaption></figcaption></figure>

After clicking the edit icon, a dialog box will appear.

<figure><img src="/files/8nzxe486FCm09SO77cVG" alt=""><figcaption></figcaption></figure>

Once you have edited your Asana task, click "Update Task" to save the changes.

### Modification Disabled

<figure><img src="/files/9sOw6b3h7uo0QArz2guV" alt=""><figcaption></figcaption></figure>

Edit mode is enabled by default for individual user logins.&#x20;

For centralised logins, it is disabled by default. Please contact your administrator to enable this feature.


# Stripe for Jira Service Management

{% content-ref url="/pages/PpllAo2XWMazuneTglJ4" %}
[Administrator Guide](/atlassian-cloud/stripe-for-jira-service-management/administrator-guide)
{% endcontent-ref %}

{% content-ref url="/pages/8F33KqF2JlAmPeurW5vh" %}
[User Guide](/atlassian-cloud/stripe-for-jira-service-management/user-guide)
{% endcontent-ref %}


# Administrator Guide

{% content-ref url="/pages/mZ6tbsnXxZog2IRuYeut" %}
[Configure Stripe Connection](/atlassian-cloud/stripe-for-jira-service-management/administrator-guide/configure-stripe-connection)
{% endcontent-ref %}


# Configure Stripe Connection

To Configure Stripe Connection, click on `Configure` in the Manage Apps page.

<figure><img src="/files/pZeVIBJ0cTI6zY0mDCJo" alt=""><figcaption></figcaption></figure>

In the Configure page, you need to provide your Stripe API Key.

<figure><img src="/files/nArGEtm5HADZrsiLpGxw" alt=""><figcaption></figcaption></figure>

### Finding your Stripe API Key

Navigate to Stripe [dashboard](https://dashboard.stripe.com/apikeys).

Copy Secret key into the API key text box and press Connect to Stripe.

Alternatively, you can also create a new secret key

<figure><img src="/files/VulGiWr6D65QMWoyHGxA" alt=""><figcaption></figcaption></figure>

### Creating Restricted API Key

Stripe for Jira Service Management is a read only add on. It doesn't write any data to your Stripe instance.

To make sure this is the case, you can create a restricted API Key.

Navigate to Stripe [dashboard](https://dashboard.stripe.com/apikeys). Click on **Create restricted key**.

<figure><img src="/files/X4CuIkHRtNFdkU11eqUr" alt=""><figcaption></figcaption></figure>

Select Read for all Permissions or None if Read options is not available.

<figure><img src="/files/gLCvQZS4mdu53H0L7hGN" alt=""><figcaption></figcaption></figure>

Copy the created key into the text box in Configure page. Click on Connect to Stripe.

<figure><img src="/files/NQlq0cHMtN1ptdvwzAMr" alt=""><figcaption></figcaption></figure>


# User Guide


# Stripe for Jira in JSM Issues

Please make sure you have a Stripe connection. Otherwise, ask your admin to [Configure Stripe Connection](/atlassian-cloud/stripe-for-jira-service-management/administrator-guide/configure-stripe-connection)

When an agent views a Jira Service Management (JSM) issue, they will see the matching Stripe Customer on the right sidebar panel.

<figure><img src="/files/bF8H930r2ixZWkdNHjpU" alt=""><figcaption></figcaption></figure>

The add on will attempt to match Stripe Customers based on the reporter email. The associated subscriptions, payments, and invoices will also be shown.


# Linear for Confluence


# Administrator Guide


# Configuring Linear Connection

Linear for Confluence provide a centralised Connection per Workspace.

To configure connections, locate **Linear** on the left side of the Admin page menu.&#x20;

Click **Connections**.

<figure><img src="/files/dIa2OEPkzhVs5mwKh16D" alt=""><figcaption></figcaption></figure>

Alternatively, you can also Click **Configure** on the Manage apps page.

<figure><img src="/files/xuwDaCA5WfOLqTG8YdoI" alt=""><figcaption></figcaption></figure>

Before authorizing, please make sure you are **logged in** to your Linear account.

Click on **Authorize Connection**.

<figure><img src="/files/MJEg0NkyvL9g3RjfDVVx" alt=""><figcaption></figcaption></figure>

Select your desired Workspace and click **Authorize**.

<figure><img src="/files/i2Et4UHpwk8Rltk1ugbY" alt=""><figcaption></figcaption></figure>

You should see the Authorized connection in the table.

<figure><img src="/files/jvXGsliGLK2FWNpnPcyM" alt=""><figcaption></figcaption></figure>


# Configuring Connection Permissions

To limit users that can access the addon macro, you can define access control for each Connection.

Navigate to **Connections** page. Click **Manage Permissions**.

<figure><img src="/files/wcPloRleMFSpez8DzX6y" alt=""><figcaption></figcaption></figure>

Select your desired groups.

Click **Add Group** and **Save**.

<figure><img src="/files/OXIVaVM1Ysj52ctXNL6R" alt=""><figcaption></figcaption></figure>


# Changing Linear Workspace Name and URL

Linear for Confluence saves your previous workspace URL.

Changing your Workspace Name and URL will not break existing macros that has been configured.

To see **Previous URL** for a Connection. Go to **Connections** Page.

Click More (...) options. Select Previous URL Keys.

<figure><img src="/files/38mPScE5Dqv45LSNgl2K" alt=""><figcaption></figcaption></figure>

A popup will appear.

<figure><img src="/files/cDF1NJRR9hyTHT8sfjjC" alt=""><figcaption></figcaption></figure>


# User Guide


# Linear Issue Link

Please make sure your Connection is configured. Otherwise, see [Configuring Linear Connection](/atlassian-cloud/linear-for-confluence/administrator-guide/configuring-linear-connection).

To setup **Linear Issue Link,** go to your desired Linear Issue.

Click the **Copy Issue URL** button.

<figure><img src="/files/Tmw9YpEReQzz3mJvja9s" alt=""><figcaption></figcaption></figure>

Paste your issue link to a Confluence page.

<figure><img src="/files/VwazzYCITvvaBYqwZRH1" alt=""><figcaption></figcaption></figure>

Alternatively, you can also configure the macro manually.

Type **/linear**.

<figure><img src="/files/MWz1ud9EnGILfHEGqGjS" alt=""><figcaption></figcaption></figure>

Select **Linear Issue Link.**

Paste the link in the text box.

<figure><img src="/files/eluK3dvpK9Ig5zmsWjTF" alt=""><figcaption></figcaption></figure>

Click **Insert.**

<figure><img src="/files/axginXkPUvpX44YZ53Ah" alt=""><figcaption></figcaption></figure>

You should see the added link macro.

<figure><img src="/files/oxeZr24Fo3eWaf3smOrA" alt=""><figcaption></figcaption></figure>


# Linear Issue Card

Please make sure your Connection is configured. Otherwise, see [Configuring Linear Connection](/atlassian-cloud/linear-for-confluence/administrator-guide/configuring-linear-connection).

To setup **Linear Issue Card,** go to your desired Linear Issue.

Click the **Copy Issue URL** button.

<figure><img src="/files/dvoWiRBu927ICVKamATb" alt=""><figcaption></figcaption></figure>

Type **/linear**.

Select **Linear Issue Card**.

<figure><img src="/files/Hv2kvYKeO2QE3KqMz15b" alt=""><figcaption></figcaption></figure>

Paste the URL in the textbox.

<figure><img src="/files/xv6BayDLvnD2rZ8FMn36" alt=""><figcaption></figcaption></figure>

Click Insert.

<figure><img src="/files/ZzW9ahWO2ocsTvZKyJFV" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/y6l46IGUMzbZmiuVRpG7" alt=""><figcaption></figcaption></figure>


# Linear Issue Table

Please make sure your Connection is configured. Otherwise, see [Configuring Linear Connection](/atlassian-cloud/linear-for-confluence/administrator-guide/configuring-linear-connection).

Linear Issue Table allows you to display list of Linear issues.

To configure, type **/linear**.

Select **Linear Issue Table**.

<figure><img src="/files/uVe3f8bx2VU2sTh4MIBf" alt=""><figcaption></figcaption></figure>

Select your desired Workspace.

<figure><img src="/files/ragahuP5WSYAX7nPu7pZ" alt=""><figcaption></figcaption></figure>

After selecting workspace, you can search issues to be displayed.

You can search issues by title/name/description.

<figure><img src="/files/AF0rAiek33DLuBOACrVb" alt=""><figcaption></figcaption></figure>

Search issues by url

<figure><img src="/files/Y5eNIZORC8NummXRPquL" alt=""><figcaption></figcaption></figure>

To find issues from a project, type the issue id. For example,

<figure><img src="/files/FJ4t1apYOxeNlXxxVPhW" alt=""><figcaption></figcaption></figure>

Select list of issues to be added by clicking the left checkbox.

Then, click **Add to table**.

<figure><img src="/files/x1K29M4Kr8SD7HnjyIDs" alt=""><figcaption></figcaption></figure>

Selected Issues will be displayed on the table below.

<figure><img src="/files/NQLtiRYGAeuf5rYElHsz" alt=""><figcaption></figcaption></figure>

You can configure list of fields to be displayed as table columns.

<figure><img src="/files/DIEThpGwcxsFznSerDoY" alt=""><figcaption></figcaption></figure>

Click Insert to save the table.

<figure><img src="/files/axs2fpuNdO1vLWSRntmV" alt=""><figcaption></figcaption></figure>


# Advanced Search

To filter issue in Linear based on different criteria, you can use the advance search feature.

To enable advanced search, select the corresponding checkbox.

<figure><img src="/files/sfaq6uZDsxWNcWeLFB8a" alt=""><figcaption></figcaption></figure>

The advanced search filters will appear.

Select and configure your preferred filters based on your needs.

<figure><img src="/files/DgjQlClNpdebSaRccTF3" alt=""><figcaption></figcaption></figure>

Once you have configured the filters, click on "Save" to save the macro.

This will display results based on the configured filters.

<figure><img src="/files/Wlxtt6qAClRCpim0aE5y" alt=""><figcaption></figcaption></figure>


# Linear Project Issues Table

Please make sure your Connection is configured. Otherwise, see [Configuring Linear Connection](/atlassian-cloud/linear-for-confluence/administrator-guide/configuring-linear-connection).

Linear Project Issues Table allows you to display list of Linear issues of a selected project.

To configure, type **/linear**.

Select **Linear Project Issues Table**.

<figure><img src="/files/TWDdDae6ENjGx6T518hX" alt=""><figcaption></figcaption></figure>

Select your desired Workspace.

<figure><img src="/files/ragahuP5WSYAX7nPu7pZ" alt=""><figcaption></figcaption></figure>

After selecting workspace, you can search issues to be displayed.

You can search issues by project title.

<figure><img src="/files/0glpwVSikjwCfwne6mpr" alt=""><figcaption></figcaption></figure>

Click Insert to save the table.

<figure><img src="/files/ln2SjWs2tqKCP1GBzqc9" alt=""><figcaption></figcaption></figure>


# Security Statement

## Overview <a href="#securitystatement-overview" id="securitystatement-overview"></a>

This Security Statement explains how our data is stored and what informations are collected from you.

## Data and Access <a href="#securitystatement-data" id="securitystatement-data"></a>

* We use AWS to host our cloud apps. Daily backups are performed every 24 hours.
* We do not track any private/sensitive information.
* We never store any Confluence/Linear data on our servers or database. The only thing we store is OAuth details. Linear data may be cached in memory for optimisation purposes, but it will expire once time to live reaches zero.
* Application uses HTTPS and JWT as a validation.

## Billing, Licensing and Privacy Policy

We rely on Atlassian for billing and licensing. Therefor, any personal information is collected and processed by Atlassian, governed by the Atlassian Marketplace Terms of Use and the Atlassian Privacy Policy.&#x20;

We collect information to provide better services to our customers. The types of personal information or personal data we may collect about you include:

* your name;
* your contact details, including email address, mailing address and/or telephone number;&#x20;
* your demographic information, such as postcode;
* your preferences and/or opinions;
* details of the services we have provided to you and/or that you have enquired about, and our response to you;
* your browser session and geo-location data, device and network information, statistics on page views and sessions, acquisition sources, search queries and/or browsing behavior;
* information about your access and use of our services, including through the use of Internet cookies, your communications with our services, the type of browser you are using, the type of operating system you are using and the domain name of your Internet service provider;
* additional personal information that you provide to us, directly or indirectly, through your use of our services, associated applications, associated social media platforms and/or accounts from which you permit us to collect information; and
* any other personal information requested by us and/or provided by you or a third party.

## Customer Support

When you contact us for support, we will do our best to respond within 24 business hours from the time of your request. As we are a small company, we appreciate your patience.

## Contact

If you have any questions, please do not hesitate to contact us at **<atlassian@mybytes.tech>**


# Zoho Desk for Jira


# Overview

Zoho Desk for Jira provides the following feature:

* Enhanced Visibility and Collaboration\
  Seamlessly integrates Zoho Desk and Jira to enhance visibility and collaboration between support and development teams. Access Ticket details and issue information directly within Zoho Desk or Jira.\
  ![](/files/FnV4n6RVp0S3a4sGSfXH)\
  ![](/files/UGMFoKSZBN6YrxSxBIZX)<br>

* Seamless Bidirectional Sync (Zoho Desk companion app is coming soon!)\
  Automatic bidirectional synchronization to keep all issues and tickets updated.\
  Note: Automatic Pull from Zoho only works once you have the companion app installed.<br>

* Advanced Field Mapping\
  Customize data mappings to fit your organization’s specific needs, including custom fields and object-specific mappings. See [Mapping Jira Assignee to Ticket Owner](/atlassian-cloud/zoho-desk-for-jira/administrator-guide/mapping-jira-assignee-to-ticket-owner) for an advanced use case.\ <br>

  <figure><img src="/files/6IqbPvYRsUmmBP835IWZ" alt=""><figcaption></figcaption></figure>

  <br>

  <figure><img src="/files/by4v9FL18Bjb9MvYjkz4" alt=""><figcaption></figcaption></figure>

* Connect to multiple Zoho Organisations\
  This feature enables efficient handling of multiple Zoho Desk setups within a single Jira instance.<br>

  <figure><img src="/files/vGklCEn7R9xmjUB4FvqY" alt=""><figcaption></figcaption></figure>


# Quick Start

If you are a Jira Administrator, please follow [Getting Started](/atlassian-cloud/zoho-desk-for-jira/administrator-guide/getting-started)

If you are a Jira User, please take a look at [Using Zoho Desk for Jira](/atlassian-cloud/zoho-desk-for-jira/user-guide/using-zoho-desk-for-jira)


# Administrator Guide


# Getting Started

Welcome to Zoho Desk for Jira! This guide will walk you through the steps to set up and configure the add-on. Follow the instructions below to ensure a smooth and efficient setup.

## Quick Setup Guide

Watch the video below for a quick setup guide. For more details, refer to the step-by-step documentation and [Using Zoho Desk for Jira](/atlassian-cloud/zoho-desk-for-jira/user-guide/using-zoho-desk-for-jira), as the video does not cover all functionalities.

{% embed url="<https://youtu.be/FXf2Q_Ch15U>" %}

### Step One: **Add Connection**

1. Navigate to Configuration page\
   \ <img src="/files/SdCBue6iSNlrtmmXUg23" alt="" data-size="original">
2. Add a new Connection\
   \
   Click on the Add Connection Button<br>

   <figure><img src="/files/Asv5GFKjGtAZRgkhq5vS" alt=""><figcaption></figcaption></figure>

   Enter your desired Connection Name and click `Add Connection`<br>

   <figure><img src="/files/Ho57wps84tOsXptoPupD" alt=""><figcaption></figcaption></figure>

### Step Two: **Authorize Connection**

{% hint style="info" %}
Connect with a **Zoho Admin** user

To ensure seamless functionality, it is essential to connect with a **Zoho Admin** user.
{% endhint %}

1. Click `Connect` to proceed with authenticating your Zoho credentials.<br>

   <figure><img src="/files/1kYG3wJIPs1Sl7CibMPJ" alt=""><figcaption></figcaption></figure>

2. Be sure to accept the authorization dialog when prompted.\ <br>

   <figure><img src="/files/Cgu3nrbUJjY6Ib3gqj9E" alt=""><figcaption></figcaption></figure>

3. If authentication is successful, you will see the connection details.<br>

   <figure><img src="/files/jKVzVtCtVpTVJln8zPzn" alt=""><figcaption></figcaption></figure>

### Step Three: Link Jira Project to Zoho Desk Department

To start linking and synchronising Jira Issues with Zoho Desk Modules (Tickets, Accounts, Contacts) in the Issue Context Panel, you must link a Jira Project to a Zoho Desk Department. Keep in mind that each Jira Project can only be linked to a single Zoho Desk Department.

1. Click `Link Jira Project`\ <br>

   <figure><img src="/files/0IG0Ltdmf277yS87hTga" alt=""><figcaption></figcaption></figure>

2. Enter Jira Project and Zoho Desk department. Click `Add Link`\
   \ <br>

   <figure><img src="/files/J3CRRR6OZtk05XfqXSXX" alt=""><figcaption></figcaption></figure>

3. Upon successful addition, the Module mapping table will be displayed.<br>

   <figure><img src="/files/AzJO4WoxvhjKJEm1Rx1K" alt=""><figcaption></figcaption></figure>

### Step Four: Define your Module Mappings

Module Mappings establish the relationship between Jira Issue types and Zoho Modules. Within each module mapping, you can specify a list of fields for synchronisation.

Without a Module Mapping, you won't be able to push and pull. However, you can still link modules for viewing purposes only. Currently, only Tickets can be synchronized (Push/Pull). Other modules, such as Accounts and Contacts , are view-only.

<br>

1. Click Add Module<br>

   <figure><img src="/files/hEFUSK2SwySBG3irN0wm" alt=""><figcaption></figcaption></figure>

2. Select Jira Issue type and Zoho Module to map. Then, Click `Add Module.`

<figure><img src="/files/2yrIseEsou0ySLpO6BUP" alt=""><figcaption></figcaption></figure>

3. If the addition is successful, the mapping will be displayed in the table<br>

   <figure><img src="/files/O6gC1FzfufqNw1W9DPdj" alt=""><figcaption></figcaption></figure>

### Step Five: Configure Field Mappings

Field mappings determine which fields will be synchronised between Jira and Zoho.

1. Click `Field Mapping` in the Module Mapping table<br>

   <figure><img src="/files/QIqpwPUgPB7MVNQPDBz9" alt=""><figcaption></figcaption></figure>

2. Select list of fields to be synchronised. For each field, you can specify whether to synchronise inbound, outbound, or both.<br>

   <figure><img src="/files/6Z5sXGZiDpbQrs0Iqjk2" alt=""><figcaption></figcaption></figure>

3. (Optional) Configure Value Mapping\
   \
   You can configure value mapping for each field. Value mapping translates incoming values to outgoing values (vice versa). \
   \
   For example, if you would like to assign issue based on the Ticket Owner. You can define an inbound Value Mapping. In this case, the Ticket Owner with the value of `1001021000000139001` will be translated as account id `5cce9b6d254e450fd8d1c45a` in Jira. <br>

Finally, Click **`Save`** once you are done.

<figure><img src="/files/iRaFwlFSYjgtXqjXevPy" alt=""><figcaption></figcaption></figure>

### Optional: Manage Fields displayed in Details dialog

In Issue Context Panel, user can view `Details` of each Module Item.

<figure><img src="/files/2FQZbUQssoItGXAAU4UN" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ybR4M6Xh8wx90iiTh6PF" alt=""><figcaption></figcaption></figure>

To configure list of fields shown in the dialog, click the `Available Modules` tab.

<figure><img src="/files/AP0GXe18df60iiz0FdhU" alt=""><figcaption></figcaption></figure>

Click `Manage Fields in Details Dialog`.<br>

<figure><img src="/files/ygJsnCCm4cKdDPjRpIPs" alt=""><figcaption></figcaption></figure>

Modify the fields and click `Save` when you are finished.

#### Additional Resources

If you need further assistance, don’t hesitate to contact our support team at **<atlassian@mybytes.tech>**. We’re here to help!

Thank you for using Zoho Desk for Jira!


# Connection API Token

Connection API Token is used to authenticate your credentials in Zoho Desk add-on.\
\
For more details, please follow the steps in [Getting Started](/zoho-desk/jira-connector-for-zoho-desk/administrator-guide/getting-started)


# Mapping Jira Assignee to Ticket Owner

If you would like to automatically assign issues in Jira based on Ticket Owner in Zoho Desk, you can utilize Value Mapping.

**Value Mapping** is a Mapping feature that allows you to define how specific values from one system are translated into another system during synchronization.\
\
Follow these steps below:<br>

### Navigate to Configuration page

* Navigate to the Configuration settings.
* Locate the "Field Mapping" section.

<figure><img src="/files/bCHgo4tVDGfDx6RVK7JH" alt=""><figcaption></figcaption></figure>

### Configure Field Mapping

* Set up inbound mappings for Assignee (Jira) and Ticket Owner (Zoho Desk) fields.

<figure><img src="/files/Agm9zIf7baDQ5nBB09og" alt=""><figcaption></figcaption></figure>

### Set Value Mapping

* Click on "Configure" to access the value mapping settings.
* Define the value mappings to translate the ticket owner in Zoho Desk to the assignee in Jira.
* Search for the desired Jira user and Zoho agent.
* In the example below, the Zoho agent will be translated to Jira user.

<figure><img src="/files/pwhZkYnm7Elq7hZQyADe" alt=""><figcaption></figcaption></figure>

### Save Configuration

* After setting the Value Mapping, click "Save" to apply the changes.

In this configuration, the Ticket Owner value from Zoho Desk will be automatically translated to the configured Assignee value in Jira. This automation enhances efficiency in managing tasks across both platforms.


# Mapping Multiple Zoho Desk Departments to a Single Jira Space

This plugin supports mapping multiple Zoho Desk Departments to a single Jira Space. This allows different departments to share the same Jira space while maintaining their own separate configurations.

Each department–space mapping is treated as an independent setup. This means field mappings and module mappings are configured separately for every department, even if they point to the same Jira space.

### Step by Step Guide

1. Navigate to the Connection settings and go to the mapping section

<figure><img src="/files/oi2acNNBDKefBwoXI9MS" alt=""><figcaption></figcaption></figure>

2. Click **Link Jira Space**. Then, Select Jira Space and Zoho Desk Department you want to link
   * Choose the Jira Space you want to link.
   * Select the Zoho Desk Department to be mapped to this space.

<figure><img src="/files/zOl2YHJLVBnK6Cbxrsq2" alt=""><figcaption></figcaption></figure>

3. Map Multiple Zoho Desk Departments to the same Jira Space

* Repeat the process:
  * Click **Link Jira Space** again.
  * Select the same Jira space.
  * Choose a different department.
  * You can map the same Jira space to multiple departments.

<figure><img src="/files/2tt3RmaornisgvxHiGId" alt=""><figcaption></figcaption></figure>

4. Configure Mappings Separately\
   Each Jira Space - Zoho Desk Department pair is treated as a unique configuration. Field mapping and Module mapping must be configured separately for:

* Jira Space A → Department 1
* Jira Space A → Department 2

**Note:** If you are using Jira Connector for Zoho Desk, please ensure that the Zoho Desk plugin is enabled for all the required departments.

<figure><img src="/files/vy1hBBcLWQPrZaoProqS" alt=""><figcaption></figcaption></figure>


# JQL on Associations Data

To use Associations data in JQL, you need to sync the associations data into a field in Jira.

<figure><img src="/files/WIqMYm2ttztnWbKnZ9qk" alt=""><figcaption></figcaption></figure>

Step by step guide:

1. Locate the Dropdown for Field Synchronization in Global Settings\
   \
   ![](/files/67PueJiL5ddED1NxCbLj)
2. Create custom field:\
   To mirror the Number of Associations, you need to create a custom field of the type "Number."\
   ![](/files/RcfMauQEAXFtkipfONCb)\
   For Association IDs: You will need to create a Paragraph custom field.\
   ![](/files/kluTTLhU1ojBMjZeWllx)

{% hint style="info" %}
Please make sure to add the custom fields to Edit Issue Screen. \
If the fields are not added to the **Edit Issue Screen**, they cannot be updated.

If the fields are present on the **View Issue Screen**, they become editable and can be updated manually. To prevent manual updates, it is recommended to remove these fields from the View Issue Screen.
{% endhint %}

3. Select Field to mirror Association data\
   ![](/files/O0ZR5uBN3Yo1Fnnkuvz6)
4. Save Changes.\
   Please note that the field association data will update whenever the associations are updated.
5. Use JQL for Queries\
   You can now use JQL to query issues based on the synced association data in Jira. For example, run JQL queries to filter or report on issues with specific associations.


# Configuring Connection Settings

This guide will walk you through the process of configuring connection settings in Jira.

Before enabling **"Publish an Internal Comment to Jira Issue"** or "**Push Attachments from Zoho to Jira"** feature, you must first ensure that **Enable** **Auto Sync** is enabled in the Zoho Desk Companion App. To do this, follow these steps:

1. Upgrade to the latest version of the Companion App.
2. Go to the **Preferences** page in the Zoho Desk Companion App.
3. Click on **Enable Auto Sync**.

<figure><img src="/files/lTH0WjOLiRVKtfJewOqy" alt=""><figcaption></figcaption></figure>

Once Enable Auto Sync setting is enabled, proceed to Jira to update the connection settings.

<figure><img src="/files/mkbamtNtizP3VLosHZQs" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/E6Ooa986euNICQxnNsMz" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/sLsW5D2aJ6VB4HQh4mJx" alt=""><figcaption></figcaption></figure>


# Comments Panel Configuration

This section allows administrators to control how Zoho Desk comments are displayed inside the Jira issue.

<figure><img src="/files/o3sa34XfMsFfi1UPEA69" alt=""><figcaption></figcaption></figure>

### Enable Zoho Desk Comments Panel

Controls whether the Zoho Desk comments panel is enabled in the Jira issue view.

* When enabled, Zoho Desk ticket comments will be rendered inside Jira.
* When disabled, the panel will be disabled.&#x20;

<figure><img src="/files/9zyQUPYiGhwCHB3EpZG2" alt=""><figcaption></figcaption></figure>

### Comment Privacy Filter

Determines which Zoho Desk comments are displayed based on their privacy level:

* **All** – Displays both public and private Zoho Desk comments.
* **Public** – Displays only public Zoho Desk comments.
* **Private** – Displays only private Zoho Desk comments.

### Comment Tag Filter

Allows filtering of Zoho Desk comments by tags included in the comment body.

* Enter a **space-separated list of tags** (e.g. `#jira #jira-service-desk`).
* If configured, only Zoho Desk comments containing **at least one** of the specified tags will be displayed in Jira.
* If left empty, no tag filtering is applied.


# Enable Attachment Synchronization

The attachment sync feature allows synchronization of file attachments between Jira and Zoho Desk. Administrators can enable attachment sync in the Connection Settings to allow attachments to be transferred from Jira to Zoho Desk and vice versa.

Follow these steps below:

### 1. Configure Jira Connector for Zoho Desk (Companion app)

Make sure that Connection is configured as per [Getting Started](/zoho-desk/jira-connector-for-zoho-desk/administrator-guide/getting-started) page

### 2. Ensure that you are on the latest version of the Jira Connector for Zoho Desk (Companion app)

Navigate to the Jira Extension for Zoho Desk app in the Marketplace. Check if the **Update** button is visible in the top right corner. If the button is not present, you are already on the latest version. If the button is available, proceed to update to the latest version.\ <br>

<figure><img src="/files/oMpIa4IgDloHR9ZmRoJg" alt=""><figcaption></figcaption></figure>

### 3. Ensure that Auto Sync is enabled in the Zoho Desk Companion app <a href="#id-3.-ensure-that-auto-sync-is-enabled" id="id-3.-ensure-that-auto-sync-is-enabled"></a>

<figure><img src="/files/ZjPuJXXjPZQdzrbkR9Of" alt=""><figcaption></figcaption></figure>

### 4. Navigate to Jira and enable the options in the **Connection Settings**

<figure><img src="/files/ZWavAUq5QEc4XVaYEZ25" alt=""><figcaption></figcaption></figure>

**Please take note that:**

1. Attachment **larger than 20MB can not be synced** due to Zoho's file size limit.
2. Only up to 100 attachments can be synced
3. Attachment sync follows the **Association Auto-Sync** setting. If association auto-sync is turned off, attachments will **not** be be synced.


# Field Mapping: Multiple Jira Status to a Single Zoho Desk Status

This feature allows you to map **multiple statuses to a single status** in a one way sync setup.

It is useful when one system has more granular statuses than the other and you want to normalize them into a simpler workflow.

This configuration works only for **one-way mappings**, such as:

* Jira → Zoho
* Jira ← Zoho

Bi-directional mapping is not supported for many to one status mapping because it would create ambiguity during synchronization.

### How Many to One Mapping Works

You can map multiple statuses depending on the direction:

#### Outbound Mapping (Jira → Zoho)

* You **cannot** use the same Jira status more than once.
* You **can** map multiple Jira statuses to the **same Zoho status**.

Example:

| **Jira Status (Outbound)** | **Zoho Status** |
| -------------------------- | --------------- |
| In Progress                | Working         |
| Pending Review             | Working         |
| QA Testing                 | Working         |

#### Inbound Mapping (Jira ← Zoho)

* You **cannot** use the same Zoho status more than once.
* You **can** map multiple Zoho statuses to the **same Jira status**.

Example:

| **Jira Status** | **Zoho Status (Inbound)** |
| --------------- | ------------------------- |
| In Progress     | Working                   |
| In Progress     | On Hold                   |
| In Progress     | Waiting Approval          |

***

### Step by Step Guide

#### 1. Go to the Connection Settings Page

Go to connection settings and navigate to the **Mapping** section.

#### 2. Click on Field Mapping

Select the module you want to configure, then click on **Field Mapping**.

<figure><img src="/files/iuqQLsPRBKnwg7s6dmz7" alt=""><figcaption></figcaption></figure>

#### 3. Set One Way Mapping

Choose either:

* Outbound (Jira → Zoho) or
* Inbound (Jira ← Zoho)

This must be a one-way configuration.<br>

<figure><img src="/files/UgLjY65I73OPzfB3TsoO" alt=""><figcaption></figcaption></figure>

#### 4. Click Configure Mapping

Find the status field and click **Configure**.

#### 5. Add Status Values

Add your mappings

* For outbound:
  * Each Jira status can appear only once.
  * Multiple Jira statuses can map to the same Zoho Desk status.<br>

    <figure><img src="/files/aUyAlEk2MDMoA2QLzvX6" alt=""><figcaption></figcaption></figure>
* For inbound:
  * Each Zoho Desk status can appear only once.
  * Multiple Zoho Desk statuses can map to the same Jira status.<br>

    <figure><img src="/files/O7EXmHSSSZNx0Rnry5V8" alt=""><figcaption></figcaption></figure>

#### 6. Click Save

Save the configuration.


# Publish Comments to Zoho Desk

This section explains how to publish Jira issue comments to a linked Zoho Desk ticket.

You can configure:

* Which Jira comments (Public/Private/All) are published to Zoho Desk
* Whether only comments with specific tags should be published

When a comment is added to a Jira issue, it can automatically be published to the linked Zoho Desk ticket.

#### Navigate to Connection Settings

<figure><img src="/files/D8tgqDPmzu6N3aJ09ECk" alt=""><figcaption></figcaption></figure>

### Comment Privacy

Choose which type of Jira comments should be published to Zoho Desk:

* **All** – Both Public and Private Jira comments will be published to Zoho Desk.
* **Public** – Only Public Jira comments will be published to Zoho Desk.
* **Private** – Only Private Jira comments will be published to Zoho Desk.

Please note that this setting applies **only to Jira Service Management (JSM) projects**.

For all other Jira project types, comments will be synced regardless of the selected comment privacy setting.

### Comment Tag Filter

Comment Tag Filter allows you to further restrict which comments are published to Zoho Desk based on tags included in the comment body.

* Enter a space separated list of tags
* Only Jira comments containing **at least one** of the specified tags will be published to Zoho Desk
* If left empty, all comments (based on Privacy setting) will sync

#### Example

```
#zoho
```

Only Jira comments containing `#zoho` will be synced.

Multiple tags example:

```
#zoho #zohodesk #support
```

Comment containing at least one of these tags will be published.


# Copying a Field Value Mapping to Other Issue Types

Instead of configuring the same value mapping for every issue type, you can copy an existing field value mapping to other issue type mappings with just a few clicks.

### Before You Begin

* The source field must already have a value mapping configured.
* The target issue types must already contain a mapping for the same field. This feature copies **only the value mapping** and does **not** create new field mappings.

### Copy a Value Mapping

1. Open the **Mapping** page and click on Field Mapping<br>

   <figure><img src="/files/iNwWw9gl9WkgKy5tnvsM" alt=""><figcaption></figcaption></figure>
2. Locate the field whose value mapping you want to copy (for example, **Assignee <-> Ticket Owner**).<br>

   <figure><img src="/files/tAgXQifyLbxGJGClfLA0" alt=""><figcaption></figcaption></figure>
3. Click **Copy** on the field.
4. In the dialog, select the issue types you want to copy the value mapping to.
   * Issue types that are greyed out do not have a mapping for this field and cannot be selected.<br>

     <figure><img src="/files/2vrfso4rJcGlGpX6WWl8" alt=""><figcaption></figcaption></figure>
   * If you have unsaved changes to your field mappings or value mappings, save them first. The **Copy** button is only available when there are no pending changes.<br>

     <figure><img src="/files/fAx1Yre5ht2ZEE96taYG" alt=""><figcaption></figcaption></figure>
5. Click **Copy**.

### Undo a Copy

If you copied a value mapping by mistake, click **Undo** in the confirmation message to revert the copy.

> **Note:** Undo is only available immediately after the copy operation. Once you leave the page or perform another action, the copy cannot be automatically undone.

<figure><img src="/files/MpHqdzOXbSFcsDcle4bi" alt=""><figcaption></figcaption></figure>

### Important Notes

* Only the **field's value mapping** is copied.
* Existing field mappings are **not** created or modified.
* If a target issue type already has a value mapping for the field, it will be **overwritten**.
* If the **Copy** button is disabled, configure a value mapping for the source field first.


# Re-Installing add-on

To re install the add-on, please follow these steps:\
\
1\. Click on Stop Trial

<figure><img src="/files/qF1RXgfYoB1YCohoOk6d" alt=""><figcaption></figcaption></figure>

2. Unsubscribe from app

<figure><img src="/files/svx9kwZ943WnmsP8Hr6J" alt=""><figcaption></figcaption></figure>

3. Uninstall application

\ <br>

3. Install the add-on again\
   Go to <https://marketplace.atlassian.com/apps/1234529/zoho-desk-for-jira?hosting=cloud&tab=overview> and install the application


# User Guide


# Using Zoho Desk for Jira

This guide will take you through the steps to effectively use Zoho Desk for Jira add-on.

Before proceeding with this guide, please ensure that the Jira project mapping is configured. If it is not, contact your administrator for assistance.

### Accessing the Zoho Desk add on

Open an issue within your Jira Project.&#x20;

The panel will be located at the right hand side of the issue view.

<figure><img src="/files/MRjPPoraBzJbOIysi7EB" alt=""><figcaption></figcaption></figure>

### Linking Modules

Click on the "Link Module" button within the widget.

<figure><img src="/files/PqAcsYjHAqwjiEwFawJ7" alt=""><figcaption></figcaption></figure>

Select the Zoho module you want to link.

Then, search the module by name or pasting the URL.

<figure><img src="/files/oyYKKJGE64iN01QzboWz" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/OMvnTvzeIuggbMO9jr3A" alt=""><figcaption></figcaption></figure>

When configuring Tickets synchronization, you have two options to choose from:

* Auto Sync\
  Enable this option to automatically sync tickets between Jira and Zoho Desk. When this option is active, any updates made to tickets in one system will be automatically reflected in the other, ensuring data consistency and up-to-date information across both platforms.<br>

  **Coming Soon: Auto Pull from Zoho Desk!**

  This upcoming feature will enable automatic pulling of ticket updates from Zoho Desk to Jira, further enhancing the synchronisation process.<br>
* View Only\
  Enable this option to set the tickets to read-only mode. With this setting, the push and pull functionalities will be disabled, meaning updates will not be automatically synchronized between Jira and Zoho Desk. This option is useful if you need to restrict editing and maintain a view-only status for the tickets.

**Please Note:**&#x20;

* Contacts and Accounts is View Only at the moment.
* If there is no Module Mapping available for the current issue type, the synchronisation is set to View Only

### Configure Synchronisation

You can modify synchronisation settings by clicking `Configure` in the linked module section.

<figure><img src="/files/FsefAZJyaYSbhsGvz7hr" alt=""><figcaption></figcaption></figure>

In the settings, you can adjust synchronisation options.

Click `Save` when you are done.

<figure><img src="/files/OeKAL5ymNBMEmVGLkJvG" alt=""><figcaption></figcaption></figure>

### Push / Pull Modules

To push and pull modules, locate the `Push` or `Pull` button within the panel.

Pushing modules will update the corresponding Tickets with the latest data from Jira issue.

Pulling modules will update Jira issue with the latest data from Zoho Desk Tickets.

<figure><img src="/files/orEy46fKfurMuwI6WsRj" alt=""><figcaption></figcaption></figure>

### Details

Details dialog displays the fields and information related to the selected module. It provides a comprehensive view of the module's details, allowing users to quickly access and review important information.

<figure><img src="/files/bOIPFPIIoCzQYdZwkAKG" alt=""><figcaption></figcaption></figure>

The fields in the details panel can be configured according to your preferences. This means you can choose which fields to display. Please ask your administrator for assistance.

<figure><img src="/files/7P9aURYOCd1uXxmWm4z2" alt=""><figcaption></figcaption></figure>

**Need Help?**

If you encounter any issues or have questions, please contact our support team at **<atlassian@mybytes.tech>**. We're here to assist you!


# Searching associated tickets with JQL

You can search for issues linked to a Zoho module by using `zohoDeskAssociatedObjectIds`.&#x20;

This allows you to quickly find issues associated with specific Zoho Desk objects within Jira.

For example, to search for issues linked to Ticket with id "999975000000299001"

<figure><img src="/files/ZnUOYSth2NhF19QlqNhp" alt=""><figcaption></figcaption></figure>


# View Zoho Desk Comments in Jira

To view Zoho Desk comments in Jira, navigate to the Issue Details page.

Locate the Activity Panels and click on the Zoho Desk Comments panel.

<figure><img src="/files/IAzT7NEcAmaMRhNTI6iX" alt=""><figcaption></figcaption></figure>

The Zoho Desk Comments panel will display comments from Zoho Desk and Jira, ordered by the latest creation time.&#x20;

To view comments for a different ticket, select the desired ticket from the dropdown menu.

Please note: Comments from Zoho Desk are labeled with Zoho Desk icon before the commenter’s name.


# JQL on Associations Data

To use Associations data in JQL, you need to sync the associations data into a field in Jira.

<figure><img src="/files/WIqMYm2ttztnWbKnZ9qk" alt=""><figcaption></figcaption></figure>

Step by step guide:

1. Locate the Dropdown for Field Synchronization in Global Settings\
   \
   ![](/files/67PueJiL5ddED1NxCbLj)
2. Create custom field:\
   To mirror the Number of Associations, you need to create a custom field of the type "Number."\
   ![](/files/RcfMauQEAXFtkipfONCb)\
   For Association IDs: You will need to create a Paragraph custom field.\
   ![](/files/kluTTLhU1ojBMjZeWllx)

{% hint style="info" %}
Please make sure to add the custom fields to Edit Issue Screen. \
If the fields are not added to the **Edit Issue Screen**, they cannot be updated.

If the fields are present on the **View Issue Screen**, they become editable and can be updated manually. To prevent manual updates, it is recommended to remove these fields from the View Issue Screen.
{% endhint %}

3. Select Field to mirror Association data\
   ![](/files/O0ZR5uBN3Yo1Fnnkuvz6)
4. Save Changes.\
   Please note that the field association data will update whenever the associations are updated.
5. Use JQL for Queries\
   You can now use JQL to query issues based on the synced association data in Jira. For example, run JQL queries to filter or report on issues with specific associations.


# Security Statement

## Overview <a href="#securitystatement-overview" id="securitystatement-overview"></a>

This Security Statement explains how our data is stored and what informations are collected from you.

## Data and Access <a href="#securitystatement-data" id="securitystatement-data"></a>

* Apps are deployed using Forge, which is hosted within the Atlassian infrastructure. This ensures that the app adheres to Atlassian's standard guidelines.
* We use AWS to host our cloud backend apps. Daily backups are performed every 24 hours.
* We do not track any private/sensitive information.
* We never store any Zoho Desk data on our servers or database.
* Application uses HTTPS and JWT as a validation.

## Billing, Licensing and Privacy Policy

We rely on Atlassian for billing and licensing. Therefor, any personal information is collected and processed by Atlassian, governed by the Atlassian Marketplace Terms of Use and the Atlassian Privacy Policy.&#x20;

We collect information to provide better services to our customers. The types of personal information or personal data we may collect about you include:

* your name;
* your contact details, including email address, mailing address and/or telephone number;&#x20;
* your demographic information, such as postcode;
* your preferences and/or opinions;
* details of the services we have provided to you and/or that you have enquired about, and our response to you;
* your browser session and geo-location data, device and network information, statistics on page views and sessions, acquisition sources, search queries and/or browsing behavior;
* information about your access and use of our services, including through the use of Internet cookies, your communications with our services, the type of browser you are using, the type of operating system you are using and the domain name of your Internet service provider;
* additional personal information that you provide to us, directly or indirectly, through your use of our services, associated applications, associated social media platforms and/or accounts from which you permit us to collect information; and
* any other personal information requested by us and/or provided by you or a third party.

## Customer Support

When you contact us for support, we will do our best to respond within 24 business hours from the time of your request. As we are a small company, we appreciate your patience.

## Contact

If you have any questions, please do not hesitate to contact us at **<atlassian@mybytes.tech>**


# Jira Connector for Zoho Desk


# Overview

Jira Connector for Zoho Desk is the companion app to [Zoho Desk for Jira in the Atlassian Marketplace](https://marketplace.atlassian.com/apps/1234529/zoho-desk-for-jira?hosting=cloud\&tab=overview).

{% hint style="info" %}
Download [Jira Connector for Zoho Desk](/zoho-desk/jira-connector-for-zoho-desk/installation) in Zoho Desk Marketplace
{% endhint %}

This add-on, together with Zoho Desk for Jira provides full integration on both sides, achieving bidirectional synchronization, seamless integration and easy setup.

**Key Benefits:**

* **Comprehensive Integration**: Sync issues and tickets effortlessly between Jira and Zoho Desk.
* **User-Friendly Interface**: Experience a smooth and intuitive UI.
* **Easy Setup**: Quick and simple installation and configuration.
* **Real-Time Updates**: Keep data up-to-date with automatic synchronisation.
* **Enhanced Collaboration**: View Jira Issue Details and Ticket Details on both platform.
* **Simplified Workflows**: Streamline your processes, reducing manual effort and errors.

Discover the power of seamless integration, streamlined workflows, and enhanced productivity with Jira Connector for Zoho Desk. Unlock efficiency and collaboration like never before!


# Administrator Guide


# Getting Started

{% hint style="info" %}
**Please Note: To use this add on, an installation of** [**Zoho Desk for Jira**](https://marketplace.atlassian.com/apps/1234529/zoho-desk-for-jira?hosting=cloud\&tab=overview) **in the Atlassian marketplace is required.**
{% endhint %}

Welcome! This section will guide you through the initial setup and features of our application, ensuring a smooth start to your journey.

### Prerequisite

To use this add-on effectively, make sure Zoho Desk for Jira is installed from the Atlassian Marketplace.

You will also need to have Connection and Mappings configured in Jira.

Please follow the steps in [Getting Started](/atlassian-cloud/zoho-desk-for-jira/administrator-guide/getting-started) to setup the add on Jira.

If you need further assistance, don’t hesitate to contact our support team at **<support@mybytes.tech>**

### Quick Setup Guide

Watch the video below for a quick setup guide. For more details, refer to the step-by-step documentation and [Using the add on](/zoho-desk/jira-connector-for-zoho-desk/user-guide/using-the-add-on), as the video does not cover all functionalities.

{% embed url="<https://youtu.be/FXf2Q_Ch15U>" %}

### Installing the add on

Ensure you install the add-on from the Zoho Marketplace.

Once the add-on is installed, you will need to authorize the connection through Zoho OAuth.

Click Authorize located on the top right.

<div align="left"><figure><img src="/files/uNV1kNDV2x0tPhZoaZ5A" alt="" width="375"><figcaption></figcaption></figure></div>

Click **Accept** when prompted.

<figure><img src="/files/Xs6B4BK4e4iWHP5CZb1u" alt=""><figcaption></figcaption></figure>

### Configuring API Token

After the OAuth connection is authorized, you'll need to configure API Token.

<figure><img src="/files/xxelRR1QhFVbK02GdLIb" alt=""><figcaption></figcaption></figure>

To get the API Token, you will need to have Zoho Desk for Jira installed and configured in Atlassian Marketplace.&#x20;

Navigate to your Jira instance and follow the steps in [Getting Started](/atlassian-cloud/zoho-desk-for-jira/administrator-guide/getting-started#step-two-authorize-connection)to make sure your Jira connection is set up properly.

Once you have the Connection configured in Jira, click **Copy Token**

<figure><img src="/files/u5W4FC6QDLLeeIIrVcvJ" alt=""><figcaption></figcaption></figure>

**NOTE: Please make sure that the Portal Name is correct!**

Paste the copied token into the textbox.

### Enabling Auto Update for Tickets

Once you have configured the API Token, please Navigate to **Preference** tab.

Make sure the status shows as Connected.

Verify that the Connection Name and Jira Base Url are correct.

<figure><img src="/files/TkP2LOgdLDfjEW6YzoPO" alt=""><figcaption></figcaption></figure>

To enable Auto Sync, click the toggle button.

This feature ensures that Tickets and Jira Issues remain up-to-date with the latest changes. Synchronisation is based on the field mappings you’ve configured in Jira.&#x20;

This ensures seamless communication and up-to-date information flow between Zoho Desk and Jira!

### Manage Field Mapping

Field Mapping defines which fields are synchronised when you Push or Pull Tickets. To manage these fields, follow the steps in [Getting Started](/atlassian-cloud/zoho-desk-for-jira/administrator-guide/getting-started#step-five-configure-field-mappings).

### Support

If you need further assistance, don’t hesitate to contact our support team at **<support@mybytes.tech>**. We’re here to help!

Thank you for using Jira Connector for Zoho Desk!


# Configure Jira Comments Panel

This section allows administrators to control how Jira comments are displayed inside the Zoho Desk ticket.

<figure><img src="/files/FyClkWetUA2BVWRh0eIx" alt=""><figcaption></figcaption></figure>

### Enable Jira Comments Panel

Controls whether the Jira comments panel is visible in the Zoho Desk ticket view.

* When enabled, Jira issue comments will be rendered inside Zoho Desk.
* When disabled, the panel will show: *"This panel has been disabled by your Jira administrator."*

### Comment Privacy Filter

Determines which Jira comments are displayed for **Jira Service Management** tickets based on their privacy level:

* **All** – Displays both public and internal comments.
* **Public** – Displays only public comments.
* **Internal** – Displays only internal comments.

For other Jira project types, all comments are shown and this setting is ignored.

### Comment Tag Filter

Allows filtering of Jira comments by tags included in the comment body.

* Enter a space-separated list of tags (e.g., `#zoho #jira-service-desk`).
* If configured, only Jira comments containing at least one of the specified tags will be displayed in Zoho Desk.
* If left empty, no tag filtering is applied.


# Publish Comments to Jira

To enable publishing Zoho Desk ticket comments as private Jira issue comments, follow these steps:

### 1. Configure Jira Extension for Zoho Desk

Make sure that Connection is configured as per [Getting Started](/zoho-desk/jira-connector-for-zoho-desk/administrator-guide/getting-started) page

### 2. Ensure that you are on the latest version of the Jira Extension for Zoho Desk

Navigate to the Jira Extension for Zoho Desk app in the Marketplace. Check if the **Update** button is visible in the top right corner. If the button is not present, you are already on the latest version. If the button is available, proceed to update to the latest version.\
\ <img src="/files/oMpIa4IgDloHR9ZmRoJg" alt="" data-size="original"><br>

### 3. Ensure that Auto Sync is enabled

<figure><img src="/files/No0ZH3Cbo2q3CbyfsNhh" alt=""><figcaption></figcaption></figure>

### 4. Navigate to Jira and enable the options in the **Connection Settings**

<figure><img src="/files/9HBAyPI4SPQC5RWhqBdQ" alt=""><figcaption></figcaption></figure>

### 5. Verify that comments are published

{% hint style="info" %}
Please take note of the following: Comments will be published if it is not a view only association.
{% endhint %}

Given the Ticket private comment below

![](/files/WApk4pddnqhqMROdxTiq)<br>

it will be published as an internal comment in Jira.

![](/files/WVxS4sMW7K4vv220rAc1)

### Configure Which Zoho Desk Comments Are Synced to Jira

This section guides you through configuring exactly which Zoho Desk comments are published to Jira. You can control:

* Whether **Public**, **Private**, or **All** comments are synced
* Whether only comments with specific **tags** should be published<br>

Navigate to Extension Settings.

Locate the setting: **Publish Zoho Desk Comments to Jira Issue**

<figure><img src="/files/fiZaLsj6IFeAp5gP8D6M" alt=""><figcaption></figcaption></figure>

**Comment Privacy**

You can control which type of Zoho Desk comments are published to Jira.

| Option      | Description                                        |
| ----------- | -------------------------------------------------- |
| **All**     | Publishes both **Public** and **Private** comments |
| **Public**  | Publishes only **Public** comments                 |
| **Private** | Publishes only **Private** comments                |

* Select the option that matches your workflow.
* Once saved, only the selected comment types will be pushed to the linked Jira issue.

**Comment Tag Filter**

The Comment Tag Filter allows you to further restrict which comments are published to Jira based on tags included in the comment body.

#### What It Does

* Only comments containing at least **one of the specified tags** will be synced.
* If no tags are configured, all comments (based on the Privacy setting) will be eligible for syncing.

#### How to Configure

1. Locate the **Comment Tag Filter** field.
2. Enter a **space separated list** of tags.
3. Save your settings.

#### Example

```
#jira
```

With the example above:

* Only comments that contain `#jira` in the comment body will be synced to Jira.
* Comments without this tag will NOT be published.

You may also configure multiple tags:

```
#jira #sync #dev
```

In this case, any comment containing **at least one** of these tags will be synced.


# Limit Jira Projects for Issue Creation in Zoho

This feature allows administrators to control **which bound Jira projects** are available when users access the **"Create Jira Issue"** screen in Zoho. You can choose to show:

* All bound projects, or
* Only allow specific projects

## 1. Configure Jira Extension for Zoho Desk

Make sure that Connection is configured as per [Getting Started](https://docs.mybytes.tech/zoho-desk/jira-connector-for-zoho-desk/administrator-guide/getting-started) page

## 2. Ensure that you are on the latest version of the Jira Extension for Zoho Desk

Navigate to the Jira Extension for Zoho Desk app in the Marketplace. Check if the **Update** button is visible in the top right corner. If the button is not present, you are already on the latest version. If the button is available, proceed to update to the latest version.&#x20;

![](https://docs.mybytes.tech/~gitbook/image?url=https%3A%2F%2F4112598543-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FBHvod0TlmybkT2IeKnoL%252Fuploads%252FvyYtHmoNfAGsW7VrAmBG%252Fpublish-comments-1.png%3Falt%3Dmedia%26token%3D21bcdef8-0cb7-49b9-8f3f-ef6792c320bb\&width=300\&dpr=4\&quality=100\&sign=bf12fae6\&sv=2)

## 3. Configure Create Jira Issue Settings

You’ll see two options under **"**&#x43;reate Jira Issue Setting&#x73;**"**:

* Allow all projects: When selected, **all Jira projects** that have been bound will be shown in the "Create Jira Issue" screen.
* Only allow specific projects: When selected, you can manually choose which Jira projects should appear in the "Create Jira Issue" screen.

<div align="left"><figure><img src="/files/kr1vNKCS4BIh0keuTMih" alt="" width="375"><figcaption></figcaption></figure></div>

## 4. Select Specific Projects (if applicable)

If you chose "Only allow specific projects":

* A dropdown list of all currently bound Jira projects will appear.
* Use the dropdown to **select one or more** projects to allow for the "Create Jira Issue" screen.

<div align="left"><figure><img src="/files/tPmIUlkcaLNWvdkHxojs" alt="" width="375"><figcaption></figcaption></figure></div>


# Jira Product Discovery Integration

This guide outlines the steps to integrate with **Jira Product Discovery (JPD).**

{% hint style="info" %}
Due to current Jira limitations, account-level apps **cannot create JPD issues**. To enable issue creation for Jira Product Discovery issues, **you must authenticate using your Jira user account**.\
\
Ensure your Jira account has:

* Access to the target JPD project
* Permission to create and update issues
  {% endhint %}

Use this guide to set up integration with **Jira Product Discovery (JPD).**

## Authorize to Jira

Go to **Preference** in Extension Settings.\
\
![](/files/4A7IgKE0vc0AGGmrESBs)

Scroll to the **JPD Integration** section.

<figure><img src="/files/t42aUwAefvMcGuGwJhMJ" alt=""><figcaption></figcaption></figure>

Click **Authorize to Jira.**

In the dialog, **select the site** that matches your Jira base URL\
⚠️ *This is important for the integration to work correctly*

<figure><img src="/files/HjPSnMLGrf4fJ37UCfO8" alt=""><figcaption></figcaption></figure>

Wait a few seconds and confirm that the connection status is **connected**

<figure><img src="/files/ZrtX1GXIe2wGyr4HaasP" alt=""><figcaption></figcaption></figure>

## Configure Custom fields to store association data

Since JPD does not support UI panels, you need to store association data in custom fields.

In Jira, go to **Custom Fields**

**Create the following fields**:<br>

* A **Short text** field to store ticket list \
  \
  ![](/files/uQsfjsJSRD96QJgLxPrG)
* A **Number** field to store number of associated tickets  (optional) \
  \
  ![](/files/ZyH0e8AdMl1htV1Zqg7F)

\
Navigate to your JPD project Settings. Click on Fields.\
Then, Add these fields to your **JPD project.**

Select Add global field.

<figure><img src="/files/o4v6DOtRCoXhpEWa29dm" alt=""><figcaption></figcaption></figure>

Select fields and click on Add.\
\
![](/files/0OXAcQ6FVNIWKDi3kFHd)

Once the fields are created, go back to the Zoho Desk extension Preference.

**Select the created fields** under the JPD Integration section.

<figure><img src="/files/vSf9w8SHZHlVTZ7RhOJT" alt=""><figcaption></figcaption></figure>

Click **Save Fields.**

Ensure the custom fields are properly populated with association data when new issues are created.

#### Additional Resources

If you need further assistance, don’t hesitate to contact our support team at **<support@mybytes.tech>**. We’re here to help!


# Configure Jira Workflow Automation

This step-by-step guide explains how to configure the **Create Jira Issue** workflow automation in Zoho Desk.

This feature allows you to automatically create a Jira issue from Zoho Desk using workflow rules.

{% hint style="info" %}
Ensure your extension is updated to the **latest version** before proceeding.
{% endhint %}

### Step 1: Enable Workflow Custom Action setting

* Navigate to the Settings page.
* Toggle **Enable Workflows Custom Action**.\
  This setting controls whether the workflow custom action is allowed to run. When disabled, the action may still be visible, but it will not execute.<br>

  <figure><img src="/files/uVBvDBGn9Jq5HiDnUYCu" alt=""><figcaption></figcaption></figure>

### Step 2: Create workflow

* In Zoho Desk, navigate to the **Workflows** page.
* Create a new workflow or edit an existing one.<br>

  <figure><img src="/files/6gHdNm4rKMZNPk2zq2AU" alt=""><figcaption></figcaption></figure>
* Set up the workflow conditions based on your business needs.
* Configure the appropriate trigger for when the workflow should run.<br>

  <figure><img src="/files/GyiZDebD9n36zdRxoxqN" alt=""><figcaption></figcaption></figure>

### Step 3: Add the Create Jira Issue Action

* In the workflow actions, select **Create Jira Issue**.<br>

  <figure><img src="/files/Jjfp2XD7o4kFs18uyva9" alt=""><figcaption></figcaption></figure>

* Enter the following required values:
  * **Jira Space ID**
  * **Jira Issue Type ID**<br>

    <figure><img src="/files/4nTS2sV3eaPi58kisEko" alt=""><figcaption></figcaption></figure>

* **Important Notes**
  * The **Jira Space ID** and **Jira Issue Type ID** must match your configured **object mappings**.
  * The Jira issue will be created based on your configured **field mappings**.
  * Make sure your object mappings and field mappings are set up correctly before enabling the workflow.

* Click Save once you are done

After completing the steps above, the workflow will automatically create Jira issues when the configured conditions are met.

### Find Your Jira Space ID and Issue Type ID

Follow these steps to quickly find your **Jira Space ID** and **Issue Type ID**:

1. Open the Zoho Desk for Jira configuration page in Jira.
2. Select the Space and Department mapping.<br>

   <figure><img src="/files/BAJ4TQP7aq2iwStYCoSp" alt=""><figcaption></figcaption></figure>
3. To find the Issue Type ID, hover over the corresponding Module Mapping row. The Issue Type ID will appear in the tooltip.<br>

   <figure><img src="/files/R9c6RI35H7RuMGVJGByy" alt=""><figcaption></figcaption></figure>

#### Additional Resources

If you need further assistance, don’t hesitate to contact our support team at **<support@mybytes.tech>**. We’re here to help!


# User Guide


# Using the add on

### Locating Issue Panel

{% hint style="info" %}
Try the **New Left Panel**. With all existing features plus Review Fields to preview before creating issues.\
For more details: [Jira Connector Left Panel](/zoho-desk/jira-connector-for-zoho-desk/user-guide/jira-connector-left-panel)
{% endhint %}

Locate the panel on the right-hand side of the screen.&#x20;

This panel provides a detailed view of Jira issue, displaying key information such as status, priority, assignee, and other relevant details. Use this panel to quickly access and review all essential aspects of the issue at a glance, ensuring you have all the information you need.

<figure><img src="/files/bvjuYtkvcWFAeqeBwmTl" alt=""><figcaption></figcaption></figure>

### Create Issue

Create a Jira issue directly from Zoho Desk without leaving the Zoho Desk environment.&#x20;

Follow these steps to create a Jira issue:

1. **Locate and Click the Create Issue Button**\
   In the Zoho Desk panel, find the "Create Issue" button and click on it.\
   \
   ![](/files/yXvHELNaiOEKClMaq6AQ)<br>
2. **Select Jira Project and Issue Type**\
   The list of available projects and issue types is based on the configurations and mappings that have been set up in Jira.
3. **Configure association types**\
   When integrating Zoho Desk with Jira, you can choose from three types of associations to manage how tickets and issues are synchronized.\
   \
   **Auto Sync On**:\
   This mode ensures that tickets in Zoho Desk and issues in Jira are automatically synchronized in real-time. Any changes made in one platform will be reflected in the other without manual intervention.\
   \
   **Auto Sync Off**:\
   In this mode, tickets and issues are linked, but synchronization does not occur automatically. You can manually push or pull updates as needed.\
   \
   **View Only**:\
   This mode allows you to link tickets and issues for viewing purposes only. No synchronization occurs, Push and Pull will be disabled. Suitable for cases where you need to monitor related issues without altering the data.
4. **Create the Issue**:\
   Click "Create" to finalize the issue creation.\
   The new Jira issue will now be linked with the corresponding Zoho Desk ticket, ensuring synchronized data and improved issue management.

<figure><img src="/files/kYPV0FJFz4nOiSeEHV6N" alt="" width="315"><figcaption></figcaption></figure>

### Link Issue

Linking an existing Jira issue directly from Zoho Desk without leaving Zoho Desk environment.

1. **Click Link Issue**\
   In the Jira integration panel, click the "Link Issue" button to begin the linking process.\
   \
   ![](/files/jdHshQ430N42uk9KSEKt)<br>
2. **Search Jira Issue**\
   In the search textbox, type the summary of the Jira issue you want to link. Select the issue you want from the list of search results.
3. **Configure association types**\
   When integrating Zoho Desk with Jira, you can choose from three types of associations to manage how tickets and issues are synchronized.\
   \
   **Auto Sync On**:\
   This mode ensures that tickets in Zoho Desk and issues in Jira are automatically synchronized in real-time. Any changes made in one platform will be reflected in the other without manual intervention.\
   \
   **Auto Sync Off**:\
   In this mode, tickets and issues are linked, but synchronization does not occur automatically. You can manually push or pull updates as needed.\
   \
   **View Only**:\
   This mode allows you to link tickets and issues for viewing purposes only. No synchronization occurs, Push and Pull will be disabled. Suitable for cases where you need to monitor related issues without altering the data.
4. **Link the Issue**\
   Once you have selected the Jira issue, click **Link**.<br>

<figure><img src="/files/wI2kCioZpHoT0NOitpBb" alt="" width="309"><figcaption></figcaption></figure>

### Configure Association

Select the appropriate association type from the dropdown list. After selecting the desired association type, changes will be automatically applied.&#x20;

\
By selecting the appropriate association type, you can control how tickets and issues are managed between Zoho Desk and Jira, ensuring the integration fits your workflow requirements.

<figure><img src="/files/ZFjIIr4XMQcsaSoPsR9X" alt="" width="292"><figcaption></figcaption></figure>

### Synchronise Tickets

This guide provides instructions for manually synchronizing tickets between Zoho Desk and Jira. It covers how to push updates, pull updates, and unlink tickets.\
\
**Push Tickets**

Pushing tickets involves sending updates from Zoho Desk to Jira. When you push a ticket, the latest information in Zoho Desk is transferred to the corresponding issue in Jira (based on the configured Field mappings).\
\
Click the "Push" button to send the updated information from Zoho Desk to Jira.&#x20;

<figure><img src="/files/qNQwzyA7w3LogKmRevH2" alt="" width="295"><figcaption></figcaption></figure>

**Pull Tickets**\
\
Pulling tickets involves retrieving updates from Jira to Zoho Desk. When you pull a ticket, the latest information in Jira is fetched and updated in the corresponding ticket in Zoho Desk.\
\
Click the "Pull" button to retrieve the updated information from Jira to Zoho Desk.

<figure><img src="/files/B5MXSabkXA1gqdo2oNNG" alt="" width="295"><figcaption></figcaption></figure>

**Unlink Tickets**

Unlinking a ticket disconnects the association between the Zoho Desk ticket and the Jira issue, stopping any further synchronization.\
\
Click on the button below to Unlink Tickets.<br>

<figure><img src="/files/lIvHQIy9Cv8Avf6kcPyn" alt="" width="306"><figcaption></figcaption></figure>

#### Additional Resources

If you need further assistance, don’t hesitate to contact our support team at **<support@mybytes.tech>**. We’re here to help!

Thank you for using Jira Connector for Zoho Desk!


# View Jira Issue Details

To view the details of a Jira issue, click the `Details` button associated with the issue.&#x20;

<div align="left"><figure><img src="/files/Itn5QRYNGulb6Kvhp1Tk" alt=""><figcaption></figcaption></figure></div>

A pop-up window will appear displaying the issue information.

<figure><img src="/files/57h9r0uMcPqHFe9OBOd8" alt=""><figcaption></figcaption></figure>


# Jira Connector Left Panel

We’re excited to announce the **Jira Connector Left Panel**, that enhances the Jira integration experience.&#x20;

This panel replaces the previous interface and brings **all existing features** from the earlier version, **plus  new capabilities** designed to boost productivity and collaboration.

The new **Jira Connector Left Panel** retains all the functionality described in [Using the add on](/zoho-desk/jira-connector-for-zoho-desk/user-guide/using-the-add-on), including:

* Viewing linked Jira issues
* Creating new Jira issues
* Link existing Jira issues
* Real-time issue syncing
* Push/Pull features

### New: Review Fields before Creating Issues

We’ve added a major enhancement: **Review Fields**, which allows you to preview and customize issue fields before creation.

With **Review Fields**, you can:

* Modify field values before creating a Jira issue.
* Select and fill in mandatory fields.
* Preview all values and ensure accuracy before issue creation.

To check and use **Review Fields** before creating a Jira issue:

1. **Click** *Create Issue* in the Jira panel.\
   \
   ![](/files/b8yzTsbPb1EtwLR8M3QN)
2. **Select** the Jira **project** and **issue type**.
3. **Click** *Review Fields* to preview and fill in required fields before submission.\
   \
   ![](/files/ANw8InIu3NprIHKuheuc)
4. **Click** *Create Issue* when you're finished.

#### Additional Resources

If you need further assistance, don’t hesitate to contact our support team at **<support@mybytes.tech>**. We’re here to help!

Thank you for using Jira Connector for Zoho Desk!


# Review Fields

The fields shown in the **Review Fields** are rendered based on your **Jira project's Create Issue screen**.&#x20;

{% hint style="info" %}
To manage which fields appear on the Create Issue screen, refer to Atlassian’s guide:  [Manage screen schemes](https://support.atlassian.com/jira-cloud-administration/docs/manage-screen-schemes/)
{% endhint %}

#### ✅ Currently Supported Fields:

We currently support the following field types:

* **Summary** (Text)
* **Description** (Text area)
* **Priority** (Dropdown)
* **Assignee** (User picker)
* **Custom fields** – limited to the following types:
  * Single-line text
  * Multi-line text
  * Select List (Single choice)
  * Number field

#### ⚠️ Missing Fields?

* If a field configured in your Jira Create Issue screen is not shown here, it may not be supported yet.
* To request support for additional field types, please email us at **<support@mybytes.tech>** with the field name and type.


# End User License Agreement

**This End-User License Agreement (EULA)** is a binding legal agreement between **MYBytes**(the «**Licensor**»), a provider of cloud-based and downloadable applications including related documentation and services (the «**Software**») through the Zoho Marketplace or any other means that interoperate with applicable products and services by ZOHO Corporation Pty Ltd («ZOHO»), and you (either an individual or a single legal entity, the «**Licensee**») whose details are provided to the Licensor when you order or receive the Software from the Licensor or a Reseller (the «**Purchase**»).

The Licensee agrees to be bound by the terms of this EULA by copying, downloading, installing, licensing, purchasing or otherwise using the Software. If the Licensee does not agree to the terms of this EULA, the Licensee may not copy, download, install or otherwise use the Software.

This EULA is a supplement to the Zoho Marketplace Terms of Use (the «**Marketplace Terms of Use**»). In case of a conflict between this EULA and the Marketplace Terms of Use, this EULA shall prevail.

### Grant of License <a href="#grant-of-license" id="grant-of-license"></a>

1.1 The Software is licensed, not sold, and no ownership right is conveyed to the Licensee, irrespective of the use of terms in this EULA.

1.2 This EULA grants the Licensee the rights according to the Licensee’s order through the Zoho Marketplace or a Reseller and the respective specifications including, but not limited to, for example the license, a maintenance or subscription period, the price, support and other services, and the number of authorized users (the «**Order**»).

1.3 The Licensor grants the Licensee a non-exclusive, non-sublicensable, non-transferable and worldwide license to use the Software limited to the scope of the Order. The Licensor reserves all rights not expressly granted to the Licensee in this EULA.

1.4 The rights under this EULA are non-exclusive, non-sublicensable and non-transferable. The Licensee may not convey, sell or transfer the Software to any third party without the Licensor’s prior express written consent.

1.5 The Licensee may not decompile, disassemble, modify or reverse engineer the Software in whole or in part, or create any derivative works from the Software without the Licensor’s prior express written consent.

1.6 The Licensee is allowed to make necessary backup copies for the purpose of backup only and for no other purpose.

1.7 The Licensee is allowed to install the Software and make the Software available for use on systems controlled, leased or owned by the Licensee or a third-party provider as long as the Licensee remains fully responsible for any compliance with this EULA.

1.8 The Software will, if not otherwise agreed or offered, delivered only in electronic form.

### 2. Third-Party Software <a href="#id-2.-third-party-software" id="id-2.-third-party-software"></a>

2.1 The Licensee acknowledges that the Software may contain software licensed by the Licensor from third parties, including open source software, and embedded in the Software, and that in addition to this EULA, additional obligations may apply in relation to any use of such third-party software by the Licensee. The Licensor shall not be liable for any third-party software.

2.2 The Software may depend on, require and use various third-party Application Programming Interface (APIs). The Licensor shall not be liable for any third-party APIs.

### 3. Payment Terms, Modifications and Termination <a href="#id-3.-payment-terms-modifications-and-termination" id="id-3.-payment-terms-modifications-and-termination"></a>

3.1 The Licensor may ask for upfront payments as a condition to grant any license to the Licensee. Any license shall only be granted to the Licensee if the Licensor has received full payment for the respective license.

3.2 The Licensor may modify this EULA at any time and at its sole discretion. If a modification is detrimental to the Licensee, the Licensor shall use reasonable efforts to notify any affected Licensee by sending e-mails to known e-mail addresses or by publishing a notification on the Licensor’s website or on the Zoho Marketplace. Continued use of the Software after such a notification by the Licensee is considered as an agreement with the modified EULA.

3.3 The Licensor may terminate any license if the Licensor is in default with payments or if the Licensor cannot reasonably expect the Licensee to make due payments.

3.4 The license shall terminate automatically if the Licensor fails to comply with this EULA.

### 4. Limitation of Liability and Warranty <a href="#id-4.-limitation-of-liability-and-warranty" id="id-4.-limitation-of-liability-and-warranty"></a>

4.1 The Licensor will use reasonable efforts to provide solutions for any reported issues. The Licensor will provide maintenance and support services, unless such services cannot be reasonably expected, for the Software on the Licensee’s request within the scope of the Order.

4.2 The Software is provided on an «as is» and «as available» basis without warranty, express or implied, of any kind of nature, including, but not limited to, any warranties of fitness for a specific purpose, or performance.

4.3 The Licensor shall not be liable to the Licensee or any other person for any consequential, direct, incidental, indirect or special damages of any kind due and in relation to the Software.

### 5. Miscellaneous <a href="#id-5.-miscellaneous" id="id-5.-miscellaneous"></a>

5.1 The Licensee grants the Licensor the right to use the Licensee’s company name / name and logo and any review provided or published in relation to the Software within promotional material, on the Licensor’s social media channels and on the Licensor’s website. The Licensee can revoke this right for future usage any time by submitting a respective request to the Licensor.

5.2 If any provision of this EULA should be held to be unenforceable for any reason, such provision shall be amended only to the extent necessary to make it enforceable and the remaining provisions of this EULA shall remain in full force and effect.

### 6. Choice of Law and Venue <a href="#id-6.-choice-of-law-and-venue" id="id-6.-choice-of-law-and-venue"></a>

6.1 This EULA shall be governed exclusively by Malaysian law excluding its conflict of laws rules and the United Nations Convention on Contracts for the International Sale of Goods (CISG).

6.2 The exclusive venue for both parties shall be the registered office of the Licensor.


# Installation

Please find the link below to install the companion app.<br>

US DC: <https://marketplace.zoho.com/app/desk/jira-extension-for-zoho-desk>

EU DC: <https://marketplace.zoho.eu/app/desk/jira-extension-for-zoho-desk>

AU DC: <https://marketplace.zoho.com.au/app/desk/jira-extension-for-zoho-desk>

IN DC: <https://marketplace.zoho.in/app/desk/jira-extension-for-zoho-desk>

CN DC: <https://marketplace.zoho.com.cn/app/desk/jira-extension-for-zoho-desk>

JP DC: <https://marketplace.zoho.jp/app/desk/jira-extension-for-zoho-desk>

SA DC: <https://marketplace.zoho.sa/app/desk/jira-extension-for-zoho-desk>

For setup guide, please refer to [Getting Started](/zoho-desk/jira-connector-for-zoho-desk/administrator-guide/getting-started)


# Release Notes

### Version 17.0

**Release Date:** August 14, 2026

#### 🚀 Release Notes: Setup Improvements

Zoho Desk OAuth permissions are no longer required when connecting the app, making setup simpler and faster.

### Version 16.0

**Release Date:** May 5, 2026

#### 🚀 Release Notes: Configurable Fields in Details Dialog

You can now configure which fields are displayed in the details dialog.

To configure this, navigate to the Preferences page and click the **Configure** button (screenshot below).

<figure><img src="/files/cfrZhjKcCBF0QLStz69C" alt=""><figcaption></figcaption></figure>

### Version 14.0

**Release Date:** March 23, 2026

#### 🚀 Release Notes: Create Jira Issue Workflow Automation

We’re excited to announce that **Create Jira Issue Workflow Automation** is now available in the Jira Connector for Zoho Desk.

#### ✨ What’s New

You can now automatically create Jira issues from Zoho Desk using workflow automation. This helps streamline your support and development processes by reducing manual effort and ensuring faster issue creation.

#### ⚙️ Getting Started

To start using this feature:

1. Ensure your **Zoho Desk extension is updated to the latest version**
2. Configure your workflow automation following this guide:\
   [Configure Jira Workflow Automation](/zoho-desk/jira-connector-for-zoho-desk/administrator-guide/configure-jira-workflow-automation)

### &#x20;Version 11.0

**Release Date:** June 23, 2025

We’re excited to announce the release of **version 11.0**, which includes new features to improve your overall experience.

#### 🚀 New Features

We’re excited to announce support for **Jira Product Discovery integration.**

✅ You can now:

* Create a Jira Product Discovery issue from a Zoho Desk ticket.

We’re continuously improving the integration to make your workflow smoother.\
\
For more details, please check [Jira Product Discovery Integration](/zoho-desk/jira-connector-for-zoho-desk/administrator-guide/jira-product-discovery-integration)

### Version 8.0

**Release Date:** May 14, 2025

We’re excited to announce the release of **version 8.0**, which includes new features to improve your overall experience.

#### 🚀 New Features

We’re excited to announce the **Jira Connector Left Panel** to enhance the Jira integration experience. This panel replaces the previous interface and brings **all existing features** from the earlier version, **plus  new capabilities** designed to boost productivity and collaboration.\
\
For more deails, please check [Jira Connector Left Panel](/zoho-desk/jira-connector-for-zoho-desk/user-guide/jira-connector-left-panel)

**Note:**\
Only the most recent releases are shown here.


# Security Statement

## Overview <a href="#securitystatement-overview" id="securitystatement-overview"></a>

This Security Statement explains how our data is stored and what informations are collected from you.

## Data and Access <a href="#securitystatement-data" id="securitystatement-data"></a>

* We use AWS to host our cloud apps. Daily backups are performed every 24 hours.
* We do not track any private/sensitive information.
* We never store any Confluence/Asana data on our servers or database. The only thing we store is OAuth details. Asana data may be cached in memory for optimisation purposes, but it will expire once time to live reaches zero.
* Application uses HTTPS and JWT as a validation.

## Billing, Licensing and Privacy Policy

We rely on Atlassian for billing and licensing. Therefor, any personal information is collected and processed by Atlassian, governed by the Atlassian Marketplace Terms of Use and the Atlassian Privacy Policy.&#x20;

We collect information to provide better services to our customers. The types of personal information or personal data we may collect about you include:

* your name;
* your contact details, including email address, mailing address and/or telephone number;&#x20;
* your demographic information, such as postcode;
* your preferences and/or opinions;
* details of the services we have provided to you and/or that you have enquired about, and our response to you;
* your browser session and geo-location data, device and network information, statistics on page views and sessions, acquisition sources, search queries and/or browsing behavior;
* information about your access and use of our services, including through the use of Internet cookies, your communications with our services, the type of browser you are using, the type of operating system you are using and the domain name of your Internet service provider;
* additional personal information that you provide to us, directly or indirectly, through your use of our services, associated applications, associated social media platforms and/or accounts from which you permit us to collect information; and
* any other personal information requested by us and/or provided by you or a third party.

## Customer Support

When you contact us for support, we will do our best to respond within 24 business hours from the time of your request. As we are a small company, we appreciate your patience.

## Contact

If you have any questions, please do not hesitate to contact us at **<atlassian@mybytes.tech>**


# End User License Agreement (EULA)

**This End-User License Agreement (EULA)** is a binding legal agreement between **MYBytes**(the «**Licensor**»), a provider of cloud-based and downloadable applications including related documentation and services (the «**Software**») through the Atlassian Marketplace or any other means that interoperate with applicable products and services by Atlassian Pty Ltd («**Atlassian**»), and you (either an individual or a single legal entity, the «**Licensee**») whose details are provided to the Licensor when you order or receive the Software from the Licensor or a Reseller (the «**Purchase**»).

The Licensee agrees to be bound by the terms of this EULA by copying, downloading, installing, licensing, purchasing or otherwise using the Software. If the Licensee does not agree to the terms of this EULA, the Licensee may not copy, download, install or otherwise use the Software.

This EULA is a supplement to the Atlassian Marketplace Terms of Use (the «**Marketplace Terms of Use**»). In case of a conflict between this EULA and the Marketplace Terms of Use, this EULA shall prevail.  &#x20;

## Grant of License

1.1 The Software is licensed, not sold, and no ownership right is conveyed to the Licensee, irrespective of the use of terms in this EULA.

1.2 This EULA grants the Licensee the rights according to the Licensee’s order through the Atlassian Marketplace or a Reseller and the respective specifications including, but not limited to, for example the license, a maintenance or subscription period, the price, support and other services, and the number of authorized users (the «**Order**»).

1.3 The Licensor grants the Licensee a non-exclusive, non-sublicensable, non-transferable and worldwide license to use the Software limited to the scope of the Order. The Licensor reserves all rights not expressly granted to the Licensee in this EULA.

1.4 The rights under this EULA are non-exclusive, non-sublicensable and non-transferable. The Licensee may not convey, sell or transfer the Software to any third party without the Licensor’s prior express written consent.

1.5 The Licensee may not decompile, disassemble, modify or reverse engineer the Software in whole or in part, or create any derivative works from the Software without the Licensor’s prior express written consent.

1.6 The Licensee is allowed to make necessary backup copies for the purpose of backup only and for no other purpose.

1.7 The Licensee is allowed to install the Software and make the Software available for use on systems controlled, leased or owned by the Licensee or a third-party provider as long as the Licensee remains fully responsible for any compliance with this EULA.

1.8 The Software will, if not otherwise agreed or offered, delivered only in electronic form.

## 2. Third-Party Software

2.1 The Licensee acknowledges that the Software may contain software licensed by the Licensor from third parties, including open source software, and embedded in the Software, and that in addition to this EULA, additional obligations may apply in relation to any use of such third-party software by the Licensee. The Licensor shall not be liable for any third-party software.

2.2 The Software may depend on, require and use various third-party Application Programming Interface (APIs). The Licensor shall not be liable for any third-party APIs.

## 3. Payment Terms, Modifications and Termination

3.1 The Licensor may ask for upfront payments as a condition to grant any license to the Licensee. Any license shall only be granted to the Licensee if the Licensor has received full payment for the respective license.

3.2 The Licensor may modify this EULA at any time and at its sole discretion. If a modification is detrimental to the Licensee, the Licensor shall use reasonable efforts to notify any affected Licensee by sending e-mails to known e-mail addresses or by publishing a notification on the Licensor’s website or on the Atlassian Marketplace. Continued use of the Software after such a notification by the Licensee is considered as an agreement with the modified EULA.

3.3 The Licensor may terminate any license if the Licensor is in default with payments or if the Licensor cannot reasonably expect the Licensee to make due payments.

3.4 The license shall terminate automatically if the Licensor fails to comply with this EULA.

## 4. Limitation of Liability and Warranty

4.1 The Licensor will use reasonable efforts to provide solutions for any reported issues. The Licensor will provide maintenance and support services, unless such services cannot be reasonably expected, for the Software on the Licensee’s request within the scope of the Order.

4.2 The Software is provided on an «as is» and «as available» basis without warranty, express or implied, of any kind of nature, including, but not limited to, any warranties of fitness for a specific purpose, or performance.

4.3 The Licensor shall not be liable to the Licensee or any other person for any consequential, direct, incidental, indirect or special damages of any kind due and in relation to the Software.

## 5. Miscellaneous

5.1 The Licensee grants the Licensor the right to use the Licensee’s company name / name and logo and any review provided or published in relation to the Software within promotional material, on the Licensor’s social media channels and on the Licensor’s website. The Licensee can revoke this right for future usage any time by submitting a respective request to the Licensor.

5.2 If any provision of this EULA should be held to be unenforceable for any reason, such provision shall be amended only to the extent necessary to make it enforceable and the remaining provisions of this EULA shall remain in full force and effect.

## 6. Choice of Law and Venue

6.1 This EULA shall be governed exclusively by Malaysian law excluding its conflict of laws rules and the United Nations Convention on Contracts for the International Sale of Goods (CISG).

6.2 The exclusive venue for both parties shall be the registered office of the Licensor.


# Connect to Forge Migration Plan

**Current status:** In Progress\
**Last updated:** July 28, 2026

### Overview

**Commitment status:** We intend to migrate all of our apps from Atlassian Connect to Forge before Atlassian Connect reaches end of support on December 31, 2026.

This page outlines the planned migration approach, expected timeline, potential customer impact, and any actions that may be required from administrators.

The app is being modernized to align with Atlassian Forge, Atlassian’s cloud app development platform. Forge provides Atlassian-hosted infrastructure and better alignment with Atlassian Cloud security and platform standards.

### Expected customer impact

The migration is planned to avoid customer-facing downtime. Short maintenance windows may be communicated if required.

Existing functionality is expected to continue working after the migration.

Administrators may be prompted to approve updated Forge permissions during the app update process. If any connected service needs to be reauthorized, affected administrators will be notified.

### Planned timeline

#### Phase 1: Development and validation

Incrementally migrate existing Connect functionality to Forge.

**Target period:** Q3 2026\
**Customer impact:** None expected

#### Phase 2: Customer rollout

Release the Forge-based version to eligible customers.

**Target period:** Q4 2026\
**Customer impact:** Administrators may need to upgrade the app and approve updated permissions.

#### Phase 3: Post-migration stabilization

Monitor migration completion, app performance, and support requests. Remaining Connect dependencies will be removed.

**Target period:** Q4 2026\
**Customer impact:** None expected

### How we will communicate updates

We will communicate migration updates through:

* Updates to this migration plan as milestones are reached
* Release notes for app versions that include Forge related changes
* Support guidance for known issues, required actions or reauthorization steps

### Support and contact

For questions about the migration plan, contact us at <support@mybytes.tech>