---
language: "en"
---
# Table Exporter for Confluence

Do you use Confluence tables to store and display information? Do you need to move data curated in the tables? Our add-on [Table Exporter for Confluence](https://marketplace.atlassian.com/apps/1222158/table-exporter-for-confluence?hosting=cloud&tab=overview) is all you need.

## Install

If you haven't installed, please install from Atlassian Marketplace here: [https://marketplace.atlassian.com/apps/1222158/table-exporter-for-confluence?hosting=cloud\&tab=overview](https://marketplace.atlassian.com/apps/1222158/table-exporter-for-confluence?hosting=cloud&tab=overview)

## User Guide

Once installed, navigate to Confluence page which contains the table you want to export.

Go to page action and then click on **Save Tables to CSV/Excel**  
![Table Exporter for Confluence](https://help.narva.net/__attachments/a_44a70aede81dd7fa9b13fcadc635d29f7152ec82c9c2b04acd67e3573673af94/table-export-button.png?cb=9410490aaa57bb3334843ab71bfd7d6f)

This will open a new prompt where link to CSV/Excel files will be displayed.  
![table-export-download.png](https://help.narva.net/__attachments/a_3800a9e2e687aa92e702d032bc008667f32b4fbe4dc359946f70c7667d9ceb73/table-export-download.png?cb=292dcdffa3fef7b37ad2736bdbfc578f)

You can click on the links to download to local computer.

If there are multiple tables in the page, they are ordered as they appear in the page.

---
language: "en"
---
# Advanced Label Manager for Jira (Custom Labels & Reports)

[**Advanced Label Manager for Jira**](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-for-jira-custom-labels-reports) gives you power to control and ability to to fully utilize labels in Jira.

Use the app to easily find duplicates labels, rename or delete them across all issues, and get clear visibility into how labels are used throughout your projects. Whether you're cleaning up label chaos or maintaining order in your growing project, this app gives you the tools to manage labels in your Jira instance efficiently.

Check out the pages below to learn how to use the app effectively.  
![image-20250106-070113.png](https://help.narva.net/__attachments/a_397dabbf4c5d6d4c5250b58b8fada1d156035e4996f0fe77a8fb474cf9eacbf7/image-20250106-070113.png?cb=fd3731d03f4cc2c4136e89f1517699dd)
Advanced Label Manager for Jira

* [Quickstart Guide](https://help.narva.net/label-manager-for-jira/getting-started.md)
* [Managing Jira Labels](https://help.narva.net/label-manager-for-jira/view-all-labels-in-jira.md)
* [Managing Custom Labels](https://help.narva.net/label-manager-for-jira/managing-custom-labels.md)
* [Using Colorful Labels in Jira](https://help.narva.net/label-manager-for-jira/using-colorful-custom-labels-in-jira.md)
* [Label Reports in Jira Dashboard](https://help.narva.net/label-manager-for-jira/label-reports-in-jira-dashboard.md)
* [Known Issues \& Limitations](https://help.narva.net/label-manager-for-jira/known-issues-limitations.md)
* [App Updates and Changelog](https://help.narva.net/label-manager-for-jira/app-updates-and-changelog.md)

---
language: "en"
---
# App Updates and Changelog

All major versions require manual upgrade. Please update the app from **Apps → Manage apps**

We document major releases on this page. For up-to-date version information, please visit our Marketplace listing here: [**Advanced Label Manager for Jira (Custom Labels \& Reports)**](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-for-jira-custom-labels-reports)

## v3.24.0 Label Reporting in Jira Dashboard

Release date: 2025-03-20

App now enables you to build label based reports right inside Jira dashboard. Check out the detailed guide: [Label Reports in Jira Dashboard](https://help.narva.net/label-manager-for-jira/label-reports-in-jira-dashboard.md) and some common use cases: [Top 3 Use-cases for Label Reporting](https://community.atlassian.com/forums/App-Central-discussions/Top-3-Use-Cases-for-Label-Reporting-and-Visualization-in-Jira/m-p/2984383)

### v3.20.0 Manage Custom Labels

Release date: 2025-03-07

You can now manage custom label field, checkout the details here: [Managing Custom Labels](https://help.narva.net/label-manager-for-jira/managing-custom-labels.md)

### v3.18.0 Labels Gadget

Release date: 2025-03-04

We have added [Labels Gadget (alternative to Jira Labels Gadget)](https://help.narva.net/label-manager-for-jira/labels-gadget-alternative-to-jira-labels-gadget.md). It will replace the default Labels Gadget which is soon going to be removed from Jira.

### v3.12.0 Create label and bulk add to multiple issues

Release date: 2025-02-17

You can now create new labels in advance, as well as quickly bulk [add a label to multiple issues](https://help.narva.net/label-manager-for-jira/bulk-add-label-to-multiple-jira-issues.md).

Along with these changes, we have significantly improved performance in large Jira instances.

### v3.0.0 App runs 100% in the Atlassian Cloud

Release date: 2024-12-12

Until this update, **Advanced Label Manager** was using Atlassian Connect framework and was hosted on our platform.

We have migrated it to Atlassian Forge, a secure app hosting platform specifically built for Atlassian apps. This means **the app is 100% hosted in the Atlassian Cloud**. There is no data egress to Narva servers and any other platforms, therefore significantly enhancing data security.

We highly recommend users to upgrade the app to latest version from **Apps → Manage apps**

### v2.1.0 Custom Labels

Release date: 2024-09-13

You can now use custom labels (with option to add colors to labels) to enhance your labels experience in Jira.

Check out the detailed docs here: [Using Colorful Labels in Jira](https://help.narva.net/label-manager-for-jira/using-colorful-custom-labels-in-jira.md)

---
language: "en"
---
# Create Labels and Add to Issues

Do you need to create labels and quickly add them to multiple issues in bulk?

Advanced Label Manager allows you to create labels in advance, add them to multiple issues at once, and remove them from a bulk of issues if needed.

## Create a new label

To create a new label:

1. Go to **Apps → Manage Labels**

2. Click on **Add**button, enter a label name and select an issue

3. Finally, confirm it

![image-20250218-141431.png](https://help.narva.net/__attachments/a_69b15854cee19dfb5386a0e4c6d3c962d4939a89f48c6ec3ffddef4e7d5a0b25/image-20250218-141431.png?cb=013192102b60ccd2d02ff3eaf31569a3)
Add new label

Please note: A new label has to be added to at least one issue so that it can be saved and reused later.

## Add existing label to multiple Issues

In order to add an existing label to one or more issues:

1. Click on the bulk add icon under **Actions**

   ![image-20250210-094255.png](https://help.narva.net/__attachments/a_7b5babf7025c47070b93bddb0c06dab0119b8f1d2f81a915605f54049ebacca8/image-20250210-094255.png?cb=39767d5fbcc1b9ef010b057dda3851c7)
2. Select the issues

![image-20250210-102405.png](https://help.narva.net/__attachments/a_1bddc90405c2332b7137601831cac03ee1ca850f12f4667b21b89553f932b551/image-20250210-102405.png?cb=413fc8edcc2c35cda63276a4531d4663)
User can search issues and filter issues by project and status

3. Confirm to add label

If you want to narrow down issues (when you have tons of them), you can use search and filter features.

## Remove label from multiple Issues

To remove labels from Jira issues, please click on the same icon:

1. Click on**the delete icon** under **Actions**.

2. Select issues that you'd like to remove the labels from.

3. Confirm to remove label.

![image-20250210-111832.png](https://help.narva.net/__attachments/a_77106e8ad014bde0c905493b9b95dd1cad6d5347fe3351fde0bd14a69abf6341/image-20250210-111832.png?cb=49ff9c196c41dbbc1d97e505a70b6361)
User can search issues and filter issues by project and status

---
language: "en"
---
# Delete Labels in Jira

## Delete a label

You can remove labels that are not needed anymore in your Jira environment. When you delete labels using this app, those labels will be completely removed from all associated issues.

If you just want to edit or merge the duplicate labels, please refer to this page [Edit or Merge Labels in Jira](https://help.narva.net/label-manager-for-jira/rename-a-label-in-jira.md) instead.

To delete a label:

1. Go to **Apps → Manage Labels**.

2. Find the label and click**a delete icon**. A delete window will open.

3. Select all issues if you'd like to delete the label.

If you have a label that is used in too many issues, this operation might take a while.

To delete a label only in a project, go to **Project → Manage Labels**instead.

## Bulk delete labels

To delete multiple labels:

1. Go to **Apps → Manage Labels**

2. Check the labels and click **Delete** . A window with list of issues will open, click **Delete**.

3. Select all issues if you'd like to delete the label.

![Screenshot 2025-03-05 at 13.51.20-20250305-055201.png](https://help.narva.net/__attachments/a_32db7ee490b9ec957aa6d0445ee5ce052c49a476338c9d5e58463b2689e66989/Screenshot%202025-03-05%20at%2013.51.20-20250305-055201.png?cb=1c30f88d5aaf2d2155ae6631403c1804)  
![image-20250305-054256.png](https://help.narva.net/__attachments/a_3f580221882b4fe642ab7097f201198adcbe1333a7e3221263ba74da345d156a/image-20250305-054256.png?cb=3387e4b9d5a0af9693056ea281c46c35)
Select all issues to delete a label

Sometimes deleted labels are still suggested in label field, please refer to [Known Issues \& Limitations](https://help.narva.net/label-manager-for-jira/known-issues-limitations.md) for workaround.

---
language: "en"
---
# Quickstart Guide

**Advanced Label Manager for Jira** is available on Atlassian Marketplace. You can try it for 30 days for **FREE**!

1. Go to [**Advanced Label Manager for Jira**](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-for-jira-custom-labels-reports)on **Atlassian Marketplace**

2. Click on **Try it free**

3. Choose your instance and click **Start free trial**

The app will be installed in your Jira instance.

![Screenshot 2025-01-06 at 13.54.54-20250106-065513.png](https://help.narva.net/__attachments/a_2739cac436f16154e4b7a69c950bf5fc9c99a2c63fdda241f4a2d232f516fafa/Screenshot%202025-01-06%20at%2013.54.54-20250106-065513.png?cb=59c51d2c17442fff45dae57a70bdafb7)
Advanced Label Manager for Jira (Custom Labels \& Reports) - Atlassian Marketplace

If **you are not the Jira admin, you can request the app** instead, following the same process above. Your Jira admin will be informed with the request to install this app.

## Using the app

Once the app is installed, you can now start using it.

* To manage**default Jira Labels** : From the Top Nav, go to**Apps → Manage Labels**

* To use **Colorful Custom Labels** : From the Top Nav, go to**Apps → Manage Labels → Colorful Labels**(left sidebar)

## New Jira navigation

Jira has a new major redesign that affects how you find apps.

### Find Advanced Label Manager (global):

1. On the left navigation bar, expand **Apps**

2. You can find **Manage Labels** under Apps.

![new-nav.png](https://help.narva.net/__attachments/a_543f70213054b801364ba21d65244499eef44f10febade504a31a1c92e29db9a/new-nav.png?cb=40ef1d6054efdba2eeea68ecc5c8a8a7)
Manage Labels (all projects)

Note: Only Jira admin can access this page.

### Find Advanced Label Manager (project):

1. Open a project by expanding **Projects** on the left navigation bar.

<!-- -->

2. On the project **Board** page, click **More** and find **Manage Labels**.

![image-20250305-094935.png](https://help.narva.net/__attachments/a_d2dea5e9cd5dc65f85eebc2f201a7d6ff9cda0784545080ae65a67d6e93c50a5/image-20250305-094935.png?cb=43a9710c2c0e5afb6949908dc77388f5)
Manage project specific labels

Also, check out the full features and detailed documentation in these pages:

* [Managing Jira Labels](https://help.narva.net/label-manager-for-jira/view-all-labels-in-jira.md)

* [Managing Custom Labels](https://help.narva.net/label-manager-for-jira/managing-custom-labels.md)

* [Using Colorful Labels in Jira](https://help.narva.net/label-manager-for-jira/using-colorful-custom-labels-in-jira.md)

---
language: "en"
---
# How to Track Request Types in Jira Service Management (JSM)

If you've spent any time in **Jira Service Management (JSM)**, you know that managing incoming requests can feel like herding cats. From incidents to service requests to change approvals, it's easy to lose sight of requests types that are flooding your queues.

But what if there was a **simple, label-based system** to track request types *and* generate visual, dashboard-ready insights---without needing a degree in JQL?

Say hello to [**Advanced Label Manager for Jira**](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-for-jira-custom-labels-reports?hosting=cloud&tab=overview&utm_source=help_center&utm_medium=refferal&utm_campaign=use-case-1). In this article, we'll show you how to:

1. Use labels to categorize different request types in JSM using Automation

2. Use Advanced Label Manager's built-in dashboard gadgets to gain visibility

3. Make data-driven decisions (without spreadsheets)

## **🏷️ Why Use Labels for Tracking Request Types?**

You might be wondering---"JSM already has request types, so why use labels too?"

Here's why:  

|         **Request Type (JSM)**         |     **Labels (with Advanced Label Manager)**     |
|----------------------------------------|--------------------------------------------------|
| System field (limited reporting)       | Fully customizable                               |
| Hard to filter across projects         | Easy to search, filter, and visualize            |
| Not visible in standard issue search   | Labels work everywhere (even in Jira dashboards) |
| Cannot have multiple types per request | Labels = multi-tagging flexibility               |

By tagging requests with labels like incident, access-request, or hardware-issue, you can slice and dice your data across projects, teams, and workflows.

### **🔄 Step 1: Automate Labels with Automation Rules**

To avoid manual mistakes or missing labels, use **Jira automation** to apply labels based on the request type.

Here's a simple automation rule:

* **Trigger:** Work item (issue) created

* **Condition:** Request type = "New Employee Onboarding"

* **Action:** Add label hr-onboarding

![automation-rule.png](https://help.narva.net/__attachments/a_211a85c4029863f679a7c698c0b4dc8298909761c00efa3ee652adf4f34daeb5/automation-rule.png?cb=ebdb20b1e36c58fa306b7a970d0b8f49)
Automate labels with Jira Automation rules

### **📊 Step 2: Use Advanced Label Manager's Reporting Features**

Now here's where it gets fun. You can visualize the labels setup in the step above.

**Advanced Label Manager for Jira** offers a clean, powerful interface to:

1. 🔍 **Search and manage labels** across all projects

2. 📈 **Generate label usage reports** to see how often each label is used and compare

In above example, you can select labels used for request types and generate report like below:  
![request-types-report.png](https://help.narva.net/__attachments/a_f531f1e7c07726b06e41e86a9e21c5c29aad6dd097aa78ac95f348d2b51d7113/request-types-report.png?cb=76077767450e3993c406eea8fcc4a3a8)
Compare requests count by request types in JSM

### **📌 Summary**

Tracking request types in JSM doesn't need to be complex. With a simple label strategy and the reporting power available in **Advanced Label Manager**, you can:

* Improve visibility into what's coming into your service desk

* Understand trends and bottlenecks and make data driven decisions

Haven't you used **Advanced Label Manager for Jira** yet? Then start a 30-day [free trial](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-for-jira-custom-labels-reports?hosting=cloud&tab=overview&utm_source=help_center&utm_medium=refferal&utm_campaign=use-case-1) now!

---
language: "en"
---
# Known Issues & Limitations

## Jira Labels

### 1. Deleted labels are still suggested in label field

Sometimes deleted labels might be still suggested as recent labels. This is caused by Jira storing recently used labels in browser local storage. There is a [ticket](https://jira.atlassian.com/browse/JRACLOUD-78579) to fix this in Jira Issue tracker.

In the meantime, you can delete the local storage data from your browser. To do that, open **Console** → **Application** (or **Storage** in Firefox) → **Local Storage** . After that, find your Jira URL, right click and use **Delete All** popup to delete temporary data stored in your browser.

### 2. Field 'labels' cannot be set. It is not on the appropriate screen, or unknown

When editing and deleting labels, sometimes you might get this error.  
![label-field-screen-error-3.png](https://help.narva.net/__attachments/a_02780221844961e94ddc705cc77b2258e7974dcebacb8c1e146a51209ca4718f/label-field-screen-error-3.png?cb=4f392f312d1d998a828e657710c5075e)
Error message when labels field is not editable

This happens when label is not in **Create** or **Edit Screen**. You can add labels field to those screen, and it should work as expected.

You can find screens from **Project Settings → Issues → Screens**.  
![Jira-screen-label-field-2.png](https://help.narva.net/__attachments/a_4983776e41883c18a0be07a07d0cada561305a37f90dacc9f0484fa8ac693afe/Jira-screen-label-field-2.png?cb=d2ab50d5c57dfe0a4c0146ba9a069036)
Add labels field to Jira screens

### 3. Zero issue count (empty labels)

App might show labels with zero issue count. These labels are from archived projects, please refer to docs below:

[Manage Labels from Archived Projects](https://help.narva.net/label-manager-for-jira/manage-labels-from-archived-projects.md)

### 4. Delayed operation (Labels not deleted/updated immediately)

There are cases when you delete a label, the deleted label is not removed from the app. This is due to a caching issue with Atlassian's API that we use in some of the application's features. Please refresh the table periodically to see the update.

## Colorful Custom Labels

### 1. Board in team managed projects

Boards in team-managed projects (e.g. work management), service and product discovery projects are very limited and do not support adding custom fields.

Colorful Labels is a custom field, therefore currently it cannot be added to board view. There is a [ticket](https://jira.atlassian.com/browse/JRACLOUD-85694) in Jira backlog to track this limitation.

---
language: "en"
---
# Label Report Gadget

Use **Label Report** gadget to do advanced reporting on label fields. It gives better visualization of a selected labels in different chart types: bar, line and pie charts.

Follow the steps below to add a Label Report:  
![Screen Recording 2025-03-26 at 16.12.55 (1).gif](https://help.narva.net/__attachments/a_ed9521296f9915e0753d399aa004a5dd9097f1db9427d85f8ad1506ab2e37560/Screen%20Recording%202025-03-26%20at%2016.12.55%20(1).gif?cb=35e450ad580b39d24a7ece0473fd9943)

1. Go to a Jira dashboard and click edit

2. Then click on **Add Gadget**

3. Search for **Label Report** and click Add

![image-20250314-051717.png](https://help.narva.net/__attachments/a_08d949ef2775eabf66b5e87ba767e38a4ce25f55404e61480daa6ef4ff2a17d6/image-20250314-051717.png?cb=8535f87c790fb3df1de9063ca1d25a46)
Label Report

If you do not see the gadget above, please ensure that you have installed the [Advanced Label Manager](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-colorful-custom-labels-for-jira?hosting=cloud&tab=overview).  
![image-20250326-083549.png](https://help.narva.net/__attachments/a_1602b36fd0ea40d251bb16b8755fc0b3a866203ec6b90d1a671530696dbf0040/image-20250326-083549.png?cb=da49ad14d6ff71e23e5f1d534728cce3)
Label Report

4. Select a label field. Jira default field is named "Labels".

5. Select a label or multiple labels you'd like to quantify into the chart.

6. Select a chart type. The gadget supports bar chart, donut chart, and pie chart.

![labels-pie-chart.png](https://help.narva.net/__attachments/a_279d0e993f73dc5923a849f5d20f07ba56b49e7bbfe8253290b554a08c559a7b/labels-pie-chart.png?cb=ac858ca69d541665528bde215a8ef4db)
Label Report gadget example pie chart

## Visualize labels over time

You can group labels by the time the labels are tagged. The chart below shows JSM request types by labels "HR onboarding" and "Access Requests" by month.  
![request-types-report.png](https://help.narva.net/__attachments/a_8dc0f4eb0fc564a9c0758f1991ae0e7ad55f4b6433c1710019fa83d7ad6af2b9/request-types-report.png?cb=76077767450e3993c406eea8fcc4a3a8)

To set this, add the time configuration on the gadget under "Duration":

1. Select the fields and the labels you'd like to show on the chart.

2. Select time duration

3. Select how you'd like to group the labels (weekly, monthly, etc.)

![image-20250326-093513.png](https://help.narva.net/__attachments/a_936357cef4384752488c434f7031ad4d868ac077e5db8f331db0d13dae7270be/image-20250326-093513.png?cb=9664c747f8247a2149fa2931e3c8f981)

---
language: "en"
---
# Label Reporting Use Cases

* [How to Track Request Types in Jira Service Management (JSM)](https://help.narva.net/label-manager-for-jira/how-to-track-request-types-in-jira-service-managem.md)

---
language: "en"
---
# Label Reports in Jira Dashboard

[++**Advanced Label Manager for Jira (Custom Labels \& Reports)**++](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-for-jira-custom-labels-reports) version 3.0 and above has label reporting capability. The reporting gadgets can be used in Jira dashboard along side default Jira reporting gadgets.

These label reporting gadgets are available:  
* [Label Report Gadget](https://help.narva.net/label-manager-for-jira/label-report-gadget.md)
* [Labels Gadget (alternative to Jira Labels Gadget)](https://help.narva.net/label-manager-for-jira/labels-gadget-alternative-to-jira-labels-gadget.md)
* [Label Reporting Use Cases](https://help.narva.net/label-manager-for-jira/label-reporting-use-cases.md)

---
language: "en"
---
# Labels Gadget (alternative to Jira Labels Gadget)

Atlassian [announced](https://community.atlassian.com/t5/Jira-articles/Update-We-re-ending-support-for-five-dashboard-gadgets-in-May/ba-p/2844556) that the Labels Gadget, along with four other dashboard gadgets, will be removed from May 2025.

In response to this change, we have developed an alternative gadget, a drop-in replacement for the Labels Gadget as part of our app, **Advanced Label Manager for Jira**.

1. Go to a Jira dashboard and click edit

2. Then click on **Add Gadget**

3. Search for **Labels (Advanced Label Manager)** and click Add

![Labels-gadget-search-1.png](https://help.narva.net/__attachments/a_2b20e447c7d920fd38d1b3559b55e8b5bca1e306d786d0efd392a19147745bb0/Labels-gadget-search-1.png?cb=6e399e1c8ec5eed42800a34fb235aaad)
Labels Gadget alternative

If you do not see the gadget above, please ensure that you have installed the [Advanced Label Manager](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-colorful-custom-labels-for-jira?hosting=cloud&tab=overview).

4. Select a project or a filter and label field. Jira default field is named "Labels".

![image-20250304-072148.png](https://help.narva.net/__attachments/a_ce080fa163496bc67cf338a1ba00eb1866f9ff97e3e7a32250f8ffea6b83bb7c/image-20250304-072148.png?cb=93a8f0d0493aa16ed12c6ac7821882c7)

Unlike default Labels Gadget, this gadget also supports saved filter along side project.  
![Labels-Gadget.png](https://help.narva.net/__attachments/a_3f68ce51d611774567cfd1e6d0f6989cd735b9644f455efb40c224f7e18ab1a5/Labels-Gadget.png?cb=4a11d6821a1bcb3fb63fa45e53e87247)
Labels Gadget: original vs. Advanced Label Manager

## How to migrate from the current Labels Gadget?

Currently, there is no automatic migration path, so it has to be done manually. You can simply remove the old gadget and add Labels Gadget from the app.

---
language: "en"
---
# Manage Labels from Archived Projects

When you use [**Advanced Label Manager**](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-colorful-custom-labels-for-jira)to manage labels in Jira, you might notice some labels without any issues (aka empty labels). If a label is not used in at least one issue, it should not exist.

So, what are these empty labels?

These labels without any issues are from archived projects. When you archive a project, Jira archives all issues and related entities like components, attachments and versions. **However, it does not archive labels. Since the associated issues are archived but not the labels, the app cannot find actual labels usage data.**  
In some cases, **recently** **deleted labels** may appear as empty labels (even if they are not associated with any archived projects). This is caused by **caching in Jira API**, so you might have to wait a while till they are completely removed from the cache.

Here is an example:  
![archived-empty-labels.png](https://help.narva.net/__attachments/a_09a39ebac392ea39d2dac4d54cdcb78c5b732a88c2b494464fd53b22bf887582/archived-empty-labels.png?cb=40fdc06f53de83d5cce3e93ba41afc4c)
Labels from archived projects

## How to manage labels from archived projects?

If you need to manage these labels (e.g. want to delete them), you can unarchive the related projects temporarily.

Restore the archived projects:

* Go to **Jira Settings** →**Projects**

* Select **Archive** tab on the left sidebar

* Click on Action (**...** ) and **Restore**

![restore-project.png](https://help.narva.net/__attachments/a_7ee0cff567fac53ae469e16c4f73cbf3eef011500ead2d1da3c3d32151d55928/restore-project.png?cb=659ad46b61d75db06a639b385142c093)
Restore an archived project

Once the archived projects are restored, the labels will show count as usual. All the label management features like editing, merging and deleting will also work as expected.

### Show or hide archived labels

If you want to filter out archived labels, you can use the configuration toggle on the left sidebar.  
![hide-empty-labels.png](https://help.narva.net/__attachments/a_f7fc01e07d052aa22f51185641b4f80122595a892dd670a988d528fea58e2952/hide-empty-labels.png?cb=0268d629781901da5e1e1f314426671a)
Toggle labels from archived projects

Setting this toggle on will hide empty labels from app dashboard, so you can focus on only active labels.

---
language: "en"
---
# Managing Custom Labels

If you use custom labels, you can now manage custom label fields along side Jira labels.

## Select a Custom Field

1. Go to Top Nav → Manage Labels → Custom Labels

2. Select a Custom Label Field

![Custom-Labels-Field-1.png](https://help.narva.net/__attachments/a_a33eff36d8b942b55ca8282294a2694274bf93a5128f603da7c461e2a5a934fa/Custom-Labels-Field-1.png?cb=a6f5b1ce477b37061b94ef0809605409)
Select a Custom Label Field to manage

## Manage Custom Labels

Once a label field is selected, you can manage labels with similar interface to default label management.

Key features:

* Create labels and quickly add to multiple issues

* View issue counts, projects and more

* Search labels, filter by projects or use JQL for advanced search and filtering

* Use rename, bulk delete and merge to save time

![Custom-Labels-2.png](https://help.narva.net/__attachments/a_0fddb4d8ab8f4dfa6cbd1ade225f167efdb02396985ddf5067ebdc17dd2be135/Custom-Labels-2.png?cb=898935d949c1e6f277a4c64b9c394b07)
Manage Custom Labels in Jira

You can also seamlessly switch to another custom field as needed.

---
language: "en"
---
# Edit or Merge Labels in Jira

## Edit or rename labels

Using [**Advanced Label Manager for Jira**](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-for-jira-custom-labels-reports), you can edit the label name as needed. The renaming will be reflected in all issues where the label was used.

To rename labels globally:

1. Go to **Apps → Manage Labels**

2. Find the label and click **a pencil icon** (✏️) to rename.

3. Optional: you can select some issues to rename, and some issues will stay the same.

To rename labels in a project, go to **Project → Manage Labels**instead.  
![image-20250305-061933.png](https://help.narva.net/__attachments/a_e3bdc9fa0e62fe21521b7f5eb94d6f7fde17dc82cf293e113363c5e842dda374/image-20250305-061933.png?cb=67f8a0ab380cd6a56dd0d92d0dcd83a3)
Renaming Label  
Please note: If you are in global mode, administrative actions (rename, delete etc.) will affect all projects. If you do not want this, use per project label management.

## Merge two or more labels

If you have duplicate labels or just need to merge multiple labels into one, this is now possible.

In order to merge labels:

1. Find and select labels to be merged

2. Click **Merge**, which will open a new window

3. Select existing or type new label as target label

![merge-labels.png](https://help.narva.net/__attachments/a_cf8f927688097a36434d30c5eb3136ffe7d24819b6aa715d11fdbea720d0960b/merge-labels.png?cb=aa75805577dad8bff810680103ddc2bd)
Merge labels in Jira

## Add a label to issues

You can tag a label for multiple issues without leaving the application in one page:

1. Select a label and click on **the add icon** in the **Actions** column.

   ![Screenshot 2025-03-05 at 14.54.50-20250305-065510.png](https://help.narva.net/__attachments/a_5837787acbf8d103b4145cad022e9b2a2d414add24b97be93e4f5c5967bb0ce9/Screenshot%202025-03-05%20at%2014.54.50-20250305-065510.png?cb=63af42843064d4a8f0033eee9a31b907)

   It will open a modal/window.
2. Select issues by checking and unchecking them.

3. Click **Add label to x issues**.

![image-20250305-082847.png](https://help.narva.net/__attachments/a_04f131d899c8f600466fe9790e7f48fa691e2eabbb14e41a02eea26ed71a35f9/image-20250305-082847.png?cb=be0a033fea2632805b7faf1882e57986)

To recheck if the label is successfully implemented, open the issue and see the Labels field.  
![Screenshot 2025-03-05 at 16.36.40-20250305-083653.png](https://help.narva.net/__attachments/a_6fbb47892d30411606f25c563126878670c8d1b99851f7aefe877f21f67a1ae2/Screenshot%202025-03-05%20at%2016.36.40-20250305-083653.png?cb=592a51d4f5eeb47e0a1bffa6434e96a9)

## Remove a label from issues

1. Select a label and click on **the delete icon** in the **Actions** column. It will open a modal/window.

2. Select issues by checking and unchecking them.

3. Click **Delete**.

![image-20250305-083913.png](https://help.narva.net/__attachments/a_b4a2f6d1902c7af5c9ba424b7c4b537889e7d1a5f7b6dc303f8344878681d233/image-20250305-083913.png?cb=c4541d2b4835e53b9017bf61e5a54a00)

Label will be removed from all selected issues.

---
language: "en"
---
# Using Colorful Labels in Jira

[**Advanced Label Manager for Jira (Custom Labels \& Reports)**](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-for-jira-custom-labels-reports) (version 2.0) has a new major feature that enables you to use **colorful custom labels** in Jira.

## Benefits of Colorful Labels

* **Create Standard Labels**: Create labels in advance to standardize their usage across team members as well as the entire organization.

* **Enhanced Visual Experience**: Define custom label colors to improve user experience and make Jira labels more engaging, vibrant and intuitive.

![Advanced Labels-II.png](https://help.narva.net/__attachments/a_a5b92197aba6f482942f43044c1e5d58d1fb035ca5ec62b9a62ffbda0ba931f7/Advanced%20Labels-II.png?cb=72d9af43b715d4ae3a307e71a818188e)
Using Colorful Custom Labels in Jira  
If you are using an old version of the app (\< 2.0), a manual upgrade is needed. Jira admins can upgrade the app from Top Nav → Apps → Manage apps

To open Colorful Labels, on Jira navigation bar, open **Apps → Manage Labels → Colorful Labels**.  
![colorful-labels-dashboard-2.png](https://help.narva.net/__attachments/a_a3ce2816c71d9cfbb2da07e6e5e8b7b77b9aeff799779d6061c489d7fdcd87c0/colorful-labels-dashboard-2.png?cb=796a8f8d66e9e1228c400be0b7763576)

You can pre-define labels using "Add" button. To use the labels, first set up a label field called "Colorful Labels" on your project issue type. Please refer to the guides below of how to set up the field.

In order to find out what type of project you are using, on Jira navigation bar, please go to **Projects → View all projects**. The project's type can be located on the "Type" column.

## Set up on Team-manage projects

1. Navigate to Project settings on the left menu → Issue types → select an issue type.

2. On the right side, find "**Colorful Labels**" field under Suggested fields or search the field.

3. Drag and drop into Context fields and save changes.

![Advanced-Labels-TM.png](https://help.narva.net/__attachments/a_1268cfa1acbee1f6071217ff5d8814ab20ddf6a0f39eb90e07203150b67fd001/Advanced-Labels-TM.png?cb=52ae8e94babf95fcb8cafaa958ae1d9f)
Adding Colorful Labels to team managed projects  
Please note, board in team managed projects do not support custom fields. Therefore, Colorful Labels cannot be added to **board** in **team managed projects**.

## Set up on Company-managed projects

1. Go to Project settings on the left menu → Issue → Layout → Edit issue layout

2. Locate "**Colorful Labels**" under Suggested fields or search the field if it is not suggested

3. Drag and drop it into Context fields → Save changes.

![Advanced-Labels-CM.png](https://help.narva.net/__attachments/a_ccf9e247953817b22406d4035a139771a262bb5d97469bcc28872e85f38a82a0/Advanced-Labels-CM.png?cb=d6aa1d829a1539b4c614506ad7a528ed)
Adding Colorful Labels to company managed projects

In order to see if it's set up properly, create an issue in the project. The field "Colorful Labels" should appear on the modal, then select the labels from the dropdown.

### Display the custom field in board view

Custom Field in board view is currently not customizable, therefore it will be displayed like a normal labels field.

The card field configuration only exists in Company-managed projects. In order to configure this field on Company-managed card, please do the following:

1. Open (...) → Configure Board → Card Layout

2. Select Card Layout on the left tab

3. Add field → Search for "Colorful Labels" and save it

![image-20250129-095200.png](https://help.narva.net/__attachments/a_48ec9c3fb87f994386d7d91165d47fdc719ed6e1098f17eb470e545947a639cf/image-20250129-095200.png?cb=32c637d53d5432c0e0433102eb98584a)

7. After saving, please go to the Kanban board again

8. Click View Settings on the right corner and ensure the "Colorful Labels" toggle is on.

![add-to-board.png](https://help.narva.net/__attachments/a_e568a5cc4fcafb5cbc6d2d2a36e5642b693b212fcbba5f7b9d092aa148dfceeb/add-to-board.png?cb=79a380abf3d971045731e18004bc25b3)
Add label field to Jira board

For more references regarding this limitation, please go to Atlassian [documentation](https://support.atlassian.com/jira-software-cloud/docs/customize-cards/).

---
language: "en"
---
# Managing Jira Labels

[**Advanced Label Manager for Jira**](https://marketplace.atlassian.com/apps/1221542/advanced-label-manager-for-jira-custom-labels-reports) offers powerful label management and reporting features to effortlessly manage labels in Jira.

## Manage labels in Jira globally (instance wide)

You can search, list and administer all labels in Jira system wide (i.e. labels used in all projects).

To manage labels system wide, go to Jira top navigation and find **Apps** → **Manage Labels.**  
Please note that this feature needs***admin or*** [***global permissions***](https://confluence.atlassian.com/adminjiracloud/managing-global-permissions-776636359.html)*.*If you do not see Manage Labels tab, it is likely that you do not have permission. Please ask your admin for access rights.

If you are admin or have correct permissions, it should look like below:  
![Manage-Labels-global-1.png](https://help.narva.net/__attachments/a_6c2f01fc7707c8993e6b9620b90cf37650591a8325772ab8c14ada3d90c1aea4/Manage-Labels-global-1.png?cb=20b268250e64dd3337f8375d46005335)
Manage labels in Jira (global)

**Need to search issues by label** to see what in issues a label used? Just click on issue count and then **See JQL filter**, and it will show a Jira filter with all the issues under a label.

## Manage labels in a specific project

Unlike global label management, project specific label management feature is available to all members in the project. To manage labels, click on **Manage Labels** tab on left sidebar in your Jira project.  
![Screenshot 2025-03-03 at 16.12.03-20250303-081302.png](https://help.narva.net/__attachments/a_f83a476d33a3c455f096604bc8789ebdec7c14734b1e4f8a3aac3f459df13469/Screenshot%202025-03-03%20at%2016.12.03-20250303-081302.png?cb=cbb3a389f374e7346681cdeb6f2d660a)
Manage labels (specific project)

## Search and filter labels

![Screenshot 2025-03-03 at 18.56.23(1)-20250303-105949.png](https://help.narva.net/__attachments/a_8f7c8ad8b7cca0ad1a4df806f08d31a9428dba20a4445d3ad450bbeb7f69359b/Screenshot%202025-03-03%20at%2018.56.23(1)-20250303-105949.png?cb=ee25c04426b4ce060637842637867004)

### 1. Search labels

You can simply **search** specific labels and **sort** labels by number of issues or alphabetically, and quickly understand how they are used.

### 2. Advanced label search using JQL

Advanced Label Manager supports filtering issues by projects and an advance search by JQL. **Switch the toggle** to change how you would like to search the labels. **The JQL supports the same scripts as Jira issue search** . Please [see](https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/) for how to use JQL search.  
![Screenshot 2025-03-03 at 16.46.35-20250303-084638.png](https://help.narva.net/__attachments/a_77ffed401bc42f5de4bc492c1474b5d00d2e0abd688d4c0d7144745125c23630/Screenshot%202025-03-03%20at%2016.46.35-20250303-084638.png?cb=514cac343f35409f18bcb6a4fbdedcf9)
Search label with JQL

### Issues by label

Easily view issues by label. Click on the issue count on the table and a new window will open where you can filter by the project, status (e.g. to do, in progress, done) and you can search issues by summary and other text fields.  
![Issues-by-label-1.png](https://help.narva.net/__attachments/a_8454ede4cf0bfc19181e2332670d95acdd26577144abc5a48ba07bb07f3a8e24/Issues-by-label-1.png?cb=53521bb0d6a178dc5e2b410f05606e51)
Issues by label

Follow these guides to add, rename, merge and delete labels.  
* [Create Labels and Add to Issues](https://help.narva.net/label-manager-for-jira/bulk-add-label-to-multiple-jira-issues.md)
* [Delete Labels in Jira](https://help.narva.net/label-manager-for-jira/delete-a-label-in-jira.md)
* [Edit or Merge Labels in Jira](https://help.narva.net/label-manager-for-jira/rename-a-label-in-jira.md)

---
language: "en"
---
# Easy Gantt Charts for Confluence

Do you need to use the Gantt chart in Confluence? [Easy Gantt Charts for Confluence](https://marketplace.atlassian.com/apps/1222190) add an easy-to-use Gantt chart macro that has all the features you need.

## Install

Please install from Atlassian Marketplace here: [https://marketplace.atlassian.com/apps/1222190](https://marketplace.atlassian.com/apps/1222190/easy-gantt-charts-for-confluence?hosting=cloud&tab=overview)

Once installed, you can start using this app.

* Open the Confluence page, type "/gantt" and find **Gantt Chart**.

* Click on the edit icon, and it should appear as an empty table where you can enter data.

![image-20240229-052614.png](https://help.narva.net/__attachments/a_cac740b207446b46a56d045723becd4ecb87639df6fc3db8ea3360a883449268/image-20240229-052614.png?cb=ca1d8a46d3869b4352efc4b2c98436db)
Easy Gantt Chart app

Familiarize yourself with this editing interface. It has some advanced features, for example you can:

* Create hierarchical tasks tree or set dependencies between tasks

* Show progress bar/indicator

* Drag and drop tasks (change start and end date, move up and down etc.)

* Select the best scale, you can choose from day, week, month, quarter and year

### Need Help?

If you have any questions or issues, please contact us via email at [support@bitwelt.atlassian.net](mailto:support@bitwelt.atlassian.net) or the Service Desk portal at <https://bitwelt.atlassian.net/servicedesk>.

* [Main Features](https://help.narva.net/easy-gantt-charts-for-confluence/main-features.md)

---
language: "en"
---
# Main Features

## Create tasks

Create a new chart by adding tasks. Click on the plus button to simply add a task and set the timeline.  
![Screenshot 2024-02-27 at 21.08.43-20240227-132257.png](https://help.narva.net/__attachments/a_b49b2ff9defa15b396e23d6114a9135b81f6903a7ba961f04839b47cff168112/Screenshot%202024-02-27%20at%2021.08.43-20240227-132257.png?cb=1465ace360ba04b642694f1859571b50)
Add a task

### Save and export

In order to save, please click 'Save' and update the Confluence page. The chart will not be updated if the Confluence page is not updated as well.

In order to export the chart to your local, please click 'Export' and select to export to PDF or Excel file.

### View chart in different scales

User can display the chart by daily, weekly, monthly, quarterly, or yearly.  
![Screenshot 2024-02-27 at 22.41.02-20240227-144107.png](https://help.narva.net/__attachments/a_596ccaaf67328f19b5c57ccf7acce09389e2af456c6a2b4f53029d7b38bbd7ec/Screenshot%202024-02-27%20at%2022.41.02-20240227-144107.png?cb=8992d357fcafb7256b12030c7b666996)
Chart in monthly view

---
language: "en"
---
# Extra Fields for Jira Service Management

Information available to your customer in Jira Service Management portal is too limited? Do you want to show request priority, assignee, time estimate and many other fields to JSM customers? You can solve this problem with [Extra Fields for Jira Service Management](https://marketplace.atlassian.com/apps/1222530/extra-fields-for-jira-service-management?hosting=cloud&tab=overview)  
This add-on was initially released as Read Only Fields for Jira Service Desk.

## Install

If you haven't installed, please install from Atlassian Marketplace here: [https://marketplace.atlassian.com/apps/1222530](https://marketplace.atlassian.com/apps/1222530/read-only-fields-for-jira-service-desk)

## User Guide

Once installed, you can go to Service Desk project setting. On the left sidebar, find tab: **Portal Extra Fields**  
![extra-fields-jsm-ii.png](https://help.narva.net/__attachments/a_4ca60b4e899ec3ebe63bcec91be00c3c309c3ffd0604f2aa73516c5d95c0dc35/extra-fields-jsm-ii.png?cb=1a84297faaa2b52ef3167703f0bf23e9)
Extra Fields for JSM configuration

Here you can choose fields which you want to let customers view. Please note that fields selected here needs to have value. If any of the fields does not yet contain value, it will not be displayed in the portal.

Save the selected fields. Now you can create a test request or use an existing request. Make sure to assign values to selected fields via issue edit screen if they are empty.

### Portal View

![read-only-fields-II.png](https://help.narva.net/__attachments/a_2737a215d5dc3b13dc6b981057cbbe3db619a45c74bf66ac3a376fa7cd8dd4a4/read-only-fields-II.png?cb=56706c3a73cd0b3ffbf89c43b6d64363)

Those read only fields with values will be displayed in portal request detail view.

If you faced any issue, checkout the following page for possible workaround:  
* [Known Issues and Possible Solutions](https://help.narva.net/extra-fields-for-jira-service-management/known-issues-and-possible-solutions.md)

---
language: "en"
---
# Known Issues and Possible Solutions

## **1. AJAX Error 400**

This error can occur if the request type linked to the request no longer exists in the Jira Service Management project. This may happen if the request type was renamed, deleted, or replaced.  
![Screenshot 2025-08-11 at 2.17.09 PM.png](https://help.narva.net/__attachments/a_106f5b6d0bf8ce3f675bb3de6de1f92b69f72ae764c3053aa638606837e0aa46/Screenshot%202025-08-11%20at%202.17.09%E2%80%AFPM.png?cb=c08f0dfa3410f171fd888249b391b23f)

**How to Confirm:**

1. Open the affected request in the Jira Service Management portal.

2. Check the **Request type** field:

   1. If it appears empty, the linked request type no longer exists.

3. In the affected Jira Service Management project, go to:

   **Project settings** → **Request management** → **Request types**.

4. Look for the missing request type in the list.

   1. If it's not listed, this confirms the cause of the error

**Possible Workaround:**

Edit the affected request from the JSM board and change its request type to an **existing request type** in the project. After this, the request should work as expected.  
![Screenshot 2025-08-11 at 2.41.58 PM.png](https://help.narva.net/__attachments/a_83429d80d6b467de3ebacfe43d4a1e5972939b80517308d338b90e5af01e143f/Screenshot%202025-08-11%20at%202.41.58%E2%80%AFPM.png?cb=9f0c41d4174bda1b2c502563e569564d)

### **2. Some attachments are not displayed in customer portal**

If you create a ticket internally (not from customer portal) and share with customer, attachments might not be displayed to customer. This is caused by Jira permission issue.

As an alternative option, **you can create a ticket from customer portal on behalf of customer** instead of creating a ticket internally and sharing it with them.  
![JSM-create-on-behalf-of-customer.png](https://help.narva.net/__attachments/a_a420ea5398b21800f09140c11fd4dc0b065830e1b4045044789c1d57e0798c9f/JSM-create-on-behalf-of-customer.png?cb=714c0ec0593f60ffe601eadfa428bb8e)

Attachments added here will be visible to the customer and any other customers whom the ticket is shared afterward.

---
language: "en"
---
# LaTeX Math for Confluence - Math Formula & Equations

[**LaTeX Math for Confluence**](https://marketplace.atlassian.com/apps/1226109/latex-math-for-confluence-math-formula-equations?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=overview) enables you to add mathematical formula and equations in Confluence pages seamlessly.

![image-20241118-041053.png](https://help.narva.net/__attachments/a_eb79c8f7a9cd4ef2b289c07fdebc6e06664f872b66478cf22900125896a54fd1/image-20241118-041053.png?cb=6d60abc443205f765ecb589aa1025ceb)
Math formula in Confluence example

## Install

If you are Confluence admin, you can install the app from Atlassian Marketplace.

1. Go to [**LaTeX Math for Confluence**](https://marketplace.atlassian.com/apps/1226109/latex-math-for-confluence-math-formula-equations?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=overview)on **Atlassian Marketplace**

2. Click on **Get it now**

3. Choose your instance and click**Install app**

Wait for a while for installation to complete. After that, you can start using the macros in Confluence pages.

If you are not a Confluence admin, you can request admin to install following the same steps.  
* [Math Formula \& Equations in Confluence](https://help.narva.net/latex-math-for-confluence/math-formula-equations-in-confluence.md)
* [LaTeX Unit](https://help.narva.net/latex-math-for-confluence/latex-unit.md)
* [Exporting to Microsoft Word](https://help.narva.net/latex-math-for-confluence/exporting-to-microsoft-word.md)
* [Migrate LaTeX from Confluence DC or Server to Cloud](https://help.narva.net/latex-math-for-confluence/migrate-latex-math-formula-from-confluence-dc-serv.md)
* [Troubleshooting Guide](https://help.narva.net/latex-math-for-confluence/troubleshooting-guide.md)
* [v2.0 Runs on Atlassian](https://help.narva.net/latex-math-for-confluence/v2-0-runs-on-atlassian.md)

---
language: "en"
---
# Exporting to Microsoft Word

The default Confluence to Word export feature currently uses legacy .doc format. This means exported contents are not compatible with most modern word processors because .docx is the supported standard. It also makes it difficult to add support for Confluence page contents (also known as macros) created by apps like LaTeX Math.

This issue is currently tracked here: <https://jira.atlassian.com/browse/CONFCLOUD-68305>

## Companion app: Advanced Word (Docx) Exporter

In order to work around this issue, we have released a FREE app:

[**Advanced Word (Docx) Exporter for Confluence**](https://marketplace.atlassian.com/apps/156764753/advanced-word-docx-exporter-for-confluence?hosting=cloud&tab=overview)

Using this app, you can:

* Export Confluence pages to Word in DOCX, the industry standard format compatible with most word processors

* Supports exporting LaTeX formula as well as other commonly used macros like tasks, panels etc.

![export-to-word.png](https://help.narva.net/__attachments/a_0ac189e90c98ca2994d96294071e61c7ae5b9de35c3a4b0a2bfd3ce67cbf11a4/export-to-word.png?cb=b137f80fd8aa615200ec8560060dc4e2)
Export to Word using Advanced Word Exporter app

We will keep this app **FREE forever** for customers using **LaTeX Math for Confluence** . You can install it from the Marketplace listing here: [Advanced Word (Docx) Exporter for Confluence](https://marketplace.atlassian.com/apps/156764753/advanced-word-docx-exporter-for-confluence?hosting=cloud&tab=overview)

---
language: "en"
---
# LaTeX Unit

You can also write units in Confluence pages using [**LaTeX Math for Confluence**](https://marketplace.atlassian.com/apps/1226109/latex-math-for-confluence-math-formula-equations?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=latex_unit).

You can use **Easy Math - LaTeX Inline** macro for units.

Unlike regular formula and equations, units are handled slightly differently. LaTeX Math for Confluence uses MathJax rendering library to render TeX.

For writing units, you can refer to this community reference guide: <https://math.meta.stackexchange.com/questions/5020/mathjax-basic-tutorial-and-quick-reference/27212#27212>

Here are some examples using the app:

## Single Units

Syntax: `\mathrm{m}` Output: ![](data:image/svg+xml;base64,PHN2ZyBzdHlsZT0ib3ZlcmZsb3c6IHZpc2libGU7IHZlcnRpY2FsLWFsaWduOiAwOyIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB3aWR0aD0iMS44ODVleCIgaGVpZ2h0PSIxZXgiIHJvbGU9ImltZyIgZm9jdXNhYmxlPSJmYWxzZSIgdmlld0JveD0iMCAtNDQyIDgzMyA0NDIiIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIj4KICAgICAgPGRlZnM+CiAgICAgICAgPHN0eWxlPgogICAgICAgICAgZ1tmaWxsPSJjdXJyZW50Q29sb3IiXSB7IGZpbGw6ICMwMDAwMDA7IH0KICAgICAgICAgIFtzdHJva2U9ImN1cnJlbnRDb2xvciJdIHsgc3Ryb2tlOiAjMDAwMDAwOyB9CiAgICAgICAgICBnW2ZpbGw9IndoaXRlIl0geyBmaWxsOiAjRkZGRkZGOyB9CiAgICAgICAgICBbc3Ryb2tlPSJ3aGl0ZSJdIHsgc3Ryb2tlOiAjRkZGRkZGOyB9CiAgICAgICAgICBnW2ZpbGw9ImJsYWNrIl0geyBmaWxsOiAjMDAwMDAwOyB9CiAgICAgICAgICBbc3Ryb2tlPSJibGFjayJdIHsgc3Ryb2tlOiAjMDAwMDAwOyB9CiAgICAgICAgPC9zdHlsZT4KICAgICAgPC9kZWZzPgogICAgPGRlZnM+PHBhdGggaWQ9Ik1KWC00My1URVgtTi02RCIgZD0iTTQxIDQ2SDU1UTk0IDQ2IDEwMiA2MFY2OFExMDIgNzcgMTAyIDkxVDEwMiAxMjJUMTAzIDE2MVQxMDMgMjAzUTEwMyAyMzQgMTAzIDI2OVQxMDIgMzI4VjM1MVE5OSAzNzAgODggMzc2VDQzIDM4NUgyNVY0MDhRMjUgNDMxIDI3IDQzMUwzNyA0MzJRNDcgNDMzIDY1IDQzNFQxMDIgNDM2UTExOSA0MzcgMTM4IDQzOFQxNjcgNDQxVDE3OCA0NDJIMTgxVjQwMlExODEgMzY0IDE4MiAzNjRUMTg3IDM2OVQxOTkgMzg0VDIxOCA0MDJUMjQ3IDQyMVQyODUgNDM3UTMwNSA0NDIgMzM2IDQ0MlEzNTEgNDQyIDM2NCA0NDBUMzg3IDQzNFQ0MDYgNDI2VDQyMSA0MTdUNDMyIDQwNlQ0NDEgMzk1VDQ0OCAzODRUNDUyIDM3NFQ0NTUgMzY2TDQ1NyAzNjFMNDYwIDM2NVE0NjMgMzY5IDQ2NiAzNzNUNDc1IDM4NFQ0ODggMzk3VDUwMyA0MTBUNTIzIDQyMlQ1NDYgNDMyVDU3MiA0MzlUNjAzIDQ0MlE3MjkgNDQyIDc0MCAzMjlRNzQxIDMyMiA3NDEgMTkwVjEwNFE3NDEgNjYgNzQzIDU5VDc1NCA0OVE3NzUgNDYgODAzIDQ2SDgxOVYwSDgxMUw3ODggMVE3NjQgMiA3MzcgMlQ2OTkgM1E1OTYgMyA1ODcgMEg1NzlWNDZINTk1UTY1NiA0NiA2NTYgNjJRNjU3IDY0IDY1NyAyMDBRNjU2IDMzNSA2NTUgMzQzUTY0OSAzNzEgNjM1IDM4NVQ2MTEgNDAyVDU4NSA0MDRRNTQwIDQwNCA1MDYgMzcwUTQ3OSAzNDMgNDcyIDMxNVQ0NjQgMjMyVjE2OFYxMDhRNDY0IDc4IDQ2NSA2OFQ0NjggNTVUNDc3IDQ5UTQ5OCA0NiA1MjYgNDZINTQyVjBINTM0TDUxMCAxUTQ4NyAyIDQ2MCAyVDQyMiAzUTMxOSAzIDMxMCAwSDMwMlY0NkgzMThRMzc5IDQ2IDM3OSA2MlEzODAgNjQgMzgwIDIwMFEzNzkgMzM1IDM3OCAzNDNRMzcyIDM3MSAzNTggMzg1VDMzNCA0MDJUMzA4IDQwNFEyNjMgNDA0IDIyOSAzNzBRMjAyIDM0MyAxOTUgMzE1VDE4NyAyMzJWMTY4VjEwOFExODcgNzggMTg4IDY4VDE5MSA1NVQyMDAgNDlRMjIxIDQ2IDI0OSA0NkgyNjVWMEgyNTdMMjM0IDFRMjEwIDIgMTgzIDJUMTQ1IDNRNDIgMyAzMyAwSDI1VjQ2SDQxWiI+PC9wYXRoPjwvZGVmcz48ZyBzdHJva2U9ImN1cnJlbnRDb2xvciIgZmlsbD0iY3VycmVudENvbG9yIiBzdHJva2Utd2lkdGg9IjAiIHRyYW5zZm9ybT0ic2NhbGUoMSwtMSkiPjxnIGRhdGEtbW1sLW5vZGU9Im1hdGgiPjxnIGRhdGEtbW1sLW5vZGU9IlRlWEF0b20iIGRhdGEtbWp4LXRleGNsYXNzPSJPUkQiPjxnIGRhdGEtbW1sLW5vZGU9Im1pIj48dXNlIGRhdGEtYz0iNkQiIHhsaW5rOmhyZWY9IiNNSlgtNDMtVEVYLU4tNkQiPjwvdXNlPjwvZz48L2c+PC9nPjwvZz48L3N2Zz4=)

Syntax: `\mathrm{kg}` Output: ![](data:image/svg+xml;base64,PHN2ZyBzdHlsZT0ib3ZlcmZsb3c6IHZpc2libGU7IHZlcnRpY2FsLWFsaWduOiAtMC40NjZleDsiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgd2lkdGg9IjIuMzI2ZXgiIGhlaWdodD0iMi4wMzZleCIgcm9sZT0iaW1nIiBmb2N1c2FibGU9ImZhbHNlIiB2aWV3Qm94PSIwIC02OTQgMTAyOCA5MDAiIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIj4KICAgICAgPGRlZnM+CiAgICAgICAgPHN0eWxlPgogICAgICAgICAgZ1tmaWxsPSJjdXJyZW50Q29sb3IiXSB7IGZpbGw6ICMwMDAwMDA7IH0KICAgICAgICAgIFtzdHJva2U9ImN1cnJlbnRDb2xvciJdIHsgc3Ryb2tlOiAjMDAwMDAwOyB9CiAgICAgICAgICBnW2ZpbGw9IndoaXRlIl0geyBmaWxsOiAjRkZGRkZGOyB9CiAgICAgICAgICBbc3Ryb2tlPSJ3aGl0ZSJdIHsgc3Ryb2tlOiAjRkZGRkZGOyB9CiAgICAgICAgICBnW2ZpbGw9ImJsYWNrIl0geyBmaWxsOiAjMDAwMDAwOyB9CiAgICAgICAgICBbc3Ryb2tlPSJibGFjayJdIHsgc3Ryb2tlOiAjMDAwMDAwOyB9CiAgICAgICAgPC9zdHlsZT4KICAgICAgPC9kZWZzPgogICAgPGRlZnM+PHBhdGggaWQ9Ik1KWC0yOC1URVgtTi02QiIgZD0iTTM2IDQ2SDUwUTg5IDQ2IDk3IDYwVjY4UTk3IDc3IDk3IDkxVDk3IDEyNFQ5OCAxNjdUOTggMjE3VDk4IDI3MlQ5OCAzMjlROTggMzY2IDk4IDQwN1Q5OCA0ODJUOTggNTQyVDk3IDU4NlQ5NyA2MDNROTQgNjIyIDgzIDYyOFQzOCA2MzdIMjBWNjYwUTIwIDY4MyAyMiA2ODNMMzIgNjg0UTQyIDY4NSA2MSA2ODZUOTggNjg4UTExNSA2ODkgMTM1IDY5MFQxNjUgNjkzVDE3NiA2OTRIMTc5VjQ2M0wxODAgMjMzTDI0MCAyODdRMzAwIDM0MSAzMDQgMzQ3UTMxMCAzNTYgMzEwIDM2NFEzMTAgMzgzIDI4OSAzODVIMjg0VjQzMUgyOTNRMzA4IDQyOCA0MTIgNDI4UTQ3NSA0MjggNDg0IDQzMUg0ODlWMzg1SDQ3NlE0MDcgMzgwIDM2MCAzNDFRMjg2IDI3OCAyODYgMjc0UTI4NiAyNzMgMzQ5IDE4MVQ0MjAgNzlRNDM0IDYwIDQ1MSA1M1Q1MDAgNDZINTExVjBINTA1UTQ5NiAzIDQxOCAzUTMyMiAzIDMwNyAwSDI5OVY0NkgzMDZRMzMwIDQ4IDMzMCA2NVEzMzAgNzIgMzI2IDc5UTMyMyA4NCAyNzYgMTUzVDIyOCAyMjJMMTc2IDE3NlYxMjBWODRRMTc2IDY1IDE3OCA1OVQxODkgNDlRMjEwIDQ2IDIzOCA0NkgyNTRWMEgyNDZRMjMxIDMgMTM3IDNUMjggMEgyMFY0NkgzNloiPjwvcGF0aD48cGF0aCBpZD0iTUpYLTI4LVRFWC1OLTY3IiBkPSJNMzI5IDQwOVEzNzMgNDUzIDQyOSA0NTNRNDU5IDQ1MyA0NzIgNDM0VDQ4NSAzOTZRNDg1IDM4MiA0NzYgMzcxVDQ0OSAzNjBRNDE2IDM2MCA0MTIgMzkwUTQxMCA0MDQgNDE1IDQxMVE0MTUgNDEyIDQxNiA0MTRWNDE1UTM4OCA0MTIgMzYzIDM5M1EzNTUgMzg4IDM1NSAzODZRMzU1IDM4NSAzNTkgMzgxVDM2OCAzNjlUMzc5IDM1MVQzODggMzI1VDM5MiAyOTJRMzkyIDIzMCAzNDMgMTg3VDIyMiAxNDNRMTcyIDE0MyAxMjMgMTcxUTExMiAxNTMgMTEyIDEzM1ExMTIgOTggMTM4IDgxUTE0NyA3NSAxNTUgNzVUMjI3IDczUTMxMSA3MiAzMzUgNjdRMzk2IDU4IDQzMSAyNlE0NzAgLTEzIDQ3MCAtNzJRNDcwIC0xMzkgMzkyIC0xNzVRMzMyIC0yMDYgMjUwIC0yMDZRMTY3IC0yMDYgMTA3IC0xNzVRMjkgLTE0MCAyOSAtNzVRMjkgLTM5IDUwIC0xNVQ5MiAxOEwxMDMgMjRRNjcgNTUgNjcgMTA4UTY3IDE1NSA5NiAxOTNRNTIgMjM3IDUyIDI5MlE1MiAzNTUgMTAyIDM5OFQyMjMgNDQyUTI3NCA0NDIgMzE4IDQxNkwzMjkgNDA5Wk0yOTkgMzQzUTI5NCAzNzEgMjczIDM4N1QyMjEgNDA0UTE5MiA0MDQgMTcxIDM4OFQxNDUgMzQzUTE0MiAzMjYgMTQyIDI5MlExNDIgMjQ4IDE0OSAyMjdUMTc5IDE5MlExOTYgMTgyIDIyMiAxODJRMjQ0IDE4MiAyNjAgMTg5VDI4MyAyMDdUMjk0IDIyN1QyOTkgMjQyUTMwMiAyNTggMzAyIDI5MlQyOTkgMzQzWk00MDMgLTc1UTQwMyAtNTAgMzg5IC0zNFQzNDggLTExVDI5OSAtMlQyNDUgMEgyMThRMTUxIDAgMTM4IC02UTExOCAtMTUgMTA3IC0zNFQ5NSAtNzRROTUgLTg0IDEwMSAtOTdUMTIyIC0xMjdUMTcwIC0xNTVUMjUwIC0xNjdRMzE5IC0xNjcgMzYxIC0xMzlUNDAzIC03NVoiPjwvcGF0aD48L2RlZnM+PGcgc3Ryb2tlPSJjdXJyZW50Q29sb3IiIGZpbGw9ImN1cnJlbnRDb2xvciIgc3Ryb2tlLXdpZHRoPSIwIiB0cmFuc2Zvcm09InNjYWxlKDEsLTEpIj48ZyBkYXRhLW1tbC1ub2RlPSJtYXRoIj48ZyBkYXRhLW1tbC1ub2RlPSJUZVhBdG9tIiBkYXRhLW1qeC10ZXhjbGFzcz0iT1JEIj48ZyBkYXRhLW1tbC1ub2RlPSJtaSI+PHVzZSBkYXRhLWM9IjZCIiB4bGluazpocmVmPSIjTUpYLTI4LVRFWC1OLTZCIj48L3VzZT48dXNlIGRhdGEtYz0iNjciIHhsaW5rOmhyZWY9IiNNSlgtMjgtVEVYLU4tNjciIHRyYW5zZm9ybT0idHJhbnNsYXRlKDUyOCwwKSI+PC91c2U+PC9nPjwvZz48L2c+PC9nPjwvc3ZnPg==)

### Powers of n

Syntax: `4.15\times10^{n}`

Output: ![](data:image/svg+xml;base64,PHN2ZyBzdHlsZT0ib3ZlcmZsb3c6IHZpc2libGU7IHZlcnRpY2FsLWFsaWduOiAtMC4wNWV4OyIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB3aWR0aD0iMTAuMTk4ZXgiIGhlaWdodD0iMS42NDZleCIgcm9sZT0iaW1nIiBmb2N1c2FibGU9ImZhbHNlIiB2aWV3Qm94PSIwIC03MDUuNiA0NTA3LjcgNzI3LjYiIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIj4KICAgICAgPGRlZnM+CiAgICAgICAgPHN0eWxlPgogICAgICAgICAgZ1tmaWxsPSJjdXJyZW50Q29sb3IiXSB7IGZpbGw6ICMwMDAwMDA7IH0KICAgICAgICAgIFtzdHJva2U9ImN1cnJlbnRDb2xvciJdIHsgc3Ryb2tlOiAjMDAwMDAwOyB9CiAgICAgICAgICBnW2ZpbGw9IndoaXRlIl0geyBmaWxsOiAjRkZGRkZGOyB9CiAgICAgICAgICBbc3Ryb2tlPSJ3aGl0ZSJdIHsgc3Ryb2tlOiAjRkZGRkZGOyB9CiAgICAgICAgICBnW2ZpbGw9ImJsYWNrIl0geyBmaWxsOiAjMDAwMDAwOyB9CiAgICAgICAgICBbc3Ryb2tlPSJibGFjayJdIHsgc3Ryb2tlOiAjMDAwMDAwOyB9CiAgICAgICAgPC9zdHlsZT4KICAgICAgPC9kZWZzPgogICAgPGRlZnM+PHBhdGggaWQ9Ik1KWC00Mi1URVgtTi0zNCIgZD0iTTQ2MiAwUTQ0NCAzIDMzMyAzUTIxNyAzIDE5OSAwSDE5MFY0NkgyMjFRMjQxIDQ2IDI0OCA0NlQyNjUgNDhUMjc5IDUzVDI4NiA2MVEyODcgNjMgMjg3IDExNVYxNjVIMjhWMjExTDE3OSA0NDJRMzMyIDY3NCAzMzQgNjc1UTMzNiA2NzcgMzU1IDY3N0gzNzNMMzc5IDY3MVYyMTFINDcxVjE2NUgzNzlWMTE0UTM3OSA3MyAzNzkgNjZUMzg1IDU0UTM5MyA0NyA0NDIgNDZINDcxVjBINDYyWk0yOTMgMjExVjU0NUw3NCAyMTJMMTgzIDIxMUgyOTNaIj48L3BhdGg+PHBhdGggaWQ9Ik1KWC00Mi1URVgtTi0yRSIgZD0iTTc4IDYwUTc4IDg0IDk1IDEwMlQxMzggMTIwUTE2MiAxMjAgMTgwIDEwNFQxOTkgNjFRMTk5IDM2IDE4MiAxOFQxMzkgMFQ5NiAxN1Q3OCA2MFoiPjwvcGF0aD48cGF0aCBpZD0iTUpYLTQyLVRFWC1OLTMxIiBkPSJNMjEzIDU3OEwyMDAgNTczUTE4NiA1NjggMTYwIDU2M1QxMDIgNTU2SDgzVjYwMkgxMDJRMTQ5IDYwNCAxODkgNjE3VDI0NSA2NDFUMjczIDY2M1EyNzUgNjY2IDI4NSA2NjZRMjk0IDY2NiAzMDIgNjYwVjM2MUwzMDMgNjFRMzEwIDU0IDMxNSA1MlQzMzkgNDhUNDAxIDQ2SDQyN1YwSDQxNlEzOTUgMyAyNTcgM1ExMjEgMyAxMDAgMEg4OFY0NkgxMTRRMTM2IDQ2IDE1MiA0NlQxNzcgNDdUMTkzIDUwVDIwMSA1MlQyMDcgNTdUMjEzIDYxVjU3OFoiPjwvcGF0aD48cGF0aCBpZD0iTUpYLTQyLVRFWC1OLTM1IiBkPSJNMTY0IDE1N1ExNjQgMTMzIDE0OCAxMTdUMTA5IDEwMUgxMDJRMTQ4IDIyIDIyNCAyMlEyOTQgMjIgMzI2IDgyUTM0NSAxMTUgMzQ1IDIxMFEzNDUgMzEzIDMxOCAzNDlRMjkyIDM4MiAyNjAgMzgySDI1NFExNzYgMzgyIDEzNiAzMTRRMTMyIDMwNyAxMjkgMzA2VDExNCAzMDRROTcgMzA0IDk1IDMxMFE5MyAzMTQgOTMgNDg1VjYxNFE5MyA2NjQgOTggNjY0UTEwMCA2NjYgMTAyIDY2NlExMDMgNjY2IDEyMyA2NThUMTc4IDY0MlQyNTMgNjM0UTMyNCA2MzQgMzg5IDY2MlEzOTcgNjY2IDQwMiA2NjZRNDEwIDY2NiA0MTAgNjQ4VjYzNVEzMjggNTM4IDIwNSA1MzhRMTc0IDUzOCAxNDkgNTQ0TDEzOSA1NDZWMzc0UTE1OCAzODggMTY5IDM5NlQyMDUgNDEyVDI1NiA0MjBRMzM3IDQyMCAzOTMgMzU1VDQ0OSAyMDFRNDQ5IDEwOSAzODUgNDRUMjI5IC0yMlExNDggLTIyIDk5IDMyVDUwIDE1NFE1MCAxNzggNjEgMTkyVDg0IDIxMFQxMDcgMjE0UTEzMiAyMTQgMTQ4IDE5N1QxNjQgMTU3WiI+PC9wYXRoPjxwYXRoIGlkPSJNSlgtNDItVEVYLU4tRDciIGQ9Ik02MzAgMjlRNjMwIDkgNjA5IDlRNjA0IDkgNTg3IDI1VDQ5MyAxMThMMzg5IDIyMkwyODQgMTE3UTE3OCAxMyAxNzUgMTFRMTcxIDkgMTY4IDlRMTYwIDkgMTU0IDE1VDE0NyAyOVExNDcgMzYgMTYxIDUxVDI1NSAxNDZMMzU5IDI1MEwyNTUgMzU0UTE3NCA0MzUgMTYxIDQ0OVQxNDcgNDcxUTE0NyA0ODAgMTUzIDQ4NVQxNjggNDkwUTE3MyA0OTAgMTc1IDQ4OVExNzggNDg3IDI4NCAzODNMMzg5IDI3OEw0OTMgMzgyUTU3MCA0NTkgNTg3IDQ3NVQ2MDkgNDkxUTYzMCA0OTEgNjMwIDQ3MVE2MzAgNDY0IDYyMCA0NTNUNTIyIDM1NUw0MTggMjUwTDUyMiAxNDVRNjA2IDYxIDYxOCA0OFQ2MzAgMjlaIj48L3BhdGg+PHBhdGggaWQ9Ik1KWC00Mi1URVgtTi0zMCIgZD0iTTk2IDU4NVExNTIgNjY2IDI0OSA2NjZRMjk3IDY2NiAzNDUgNjQwVDQyMyA1NDhRNDYwIDQ2NSA0NjAgMzIwUTQ2MCAxNjUgNDE3IDgzUTM5NyA0MSAzNjIgMTZUMzAxIC0xNVQyNTAgLTIyUTIyNCAtMjIgMTk4IC0xNlQxMzcgMTZUODIgODNRMzkgMTY1IDM5IDMyMFEzOSA0OTQgOTYgNTg1Wk0zMjEgNTk3UTI5MSA2MjkgMjUwIDYyOVEyMDggNjI5IDE3OCA1OTdRMTUzIDU3MSAxNDUgNTI1VDEzNyAzMzNRMTM3IDE3NSAxNDUgMTI1VDE4MSA0NlEyMDkgMTYgMjUwIDE2UTI5MCAxNiAzMTggNDZRMzQ3IDc2IDM1NCAxMzBUMzYyIDMzM1EzNjIgNDc4IDM1NCA1MjRUMzIxIDU5N1oiPjwvcGF0aD48cGF0aCBpZD0iTUpYLTQyLVRFWC1JLTFENDVCIiBkPSJNMjEgMjg3UTIyIDI5MyAyNCAzMDNUMzYgMzQxVDU2IDM4OFQ4OSA0MjVUMTM1IDQ0MlExNzEgNDQyIDE5NSA0MjRUMjI1IDM5MFQyMzEgMzY5UTIzMSAzNjcgMjMyIDM2N0wyNDMgMzc4UTMwNCA0NDIgMzgyIDQ0MlE0MzYgNDQyIDQ2OSA0MTVUNTAzIDMzNlQ0NjUgMTc5VDQyNyA1MlE0MjcgMjYgNDQ0IDI2UTQ1MCAyNiA0NTMgMjdRNDgyIDMyIDUwNSA2NVQ1NDAgMTQ1UTU0MiAxNTMgNTYwIDE1M1E1ODAgMTUzIDU4MCAxNDVRNTgwIDE0NCA1NzYgMTMwUTU2OCAxMDEgNTU0IDczVDUwOCAxN1Q0MzkgLTEwUTM5MiAtMTAgMzcxIDE3VDM1MCA3M1EzNTAgOTIgMzg2IDE5M1Q0MjMgMzQ1UTQyMyA0MDQgMzc5IDQwNEgzNzRRMjg4IDQwNCAyMjkgMzAzTDIyMiAyOTFMMTg5IDE1N1ExNTYgMjYgMTUxIDE2UTEzOCAtMTEgMTA4IC0xMVE5NSAtMTEgODcgLTVUNzYgN1Q3NCAxN1E3NCAzMCAxMTIgMTgwVDE1MiAzNDNRMTUzIDM0OCAxNTMgMzY2UTE1MyA0MDUgMTI5IDQwNVE5MSA0MDUgNjYgMzA1UTYwIDI4NSA2MCAyODRRNTggMjc4IDQxIDI3OEgyN1EyMSAyODQgMjEgMjg3WiI+PC9wYXRoPjwvZGVmcz48ZyBzdHJva2U9ImN1cnJlbnRDb2xvciIgZmlsbD0iY3VycmVudENvbG9yIiBzdHJva2Utd2lkdGg9IjAiIHRyYW5zZm9ybT0ic2NhbGUoMSwtMSkiPjxnIGRhdGEtbW1sLW5vZGU9Im1hdGgiPjxnIGRhdGEtbW1sLW5vZGU9Im1uIj48dXNlIGRhdGEtYz0iMzQiIHhsaW5rOmhyZWY9IiNNSlgtNDItVEVYLU4tMzQiPjwvdXNlPjx1c2UgZGF0YS1jPSIyRSIgeGxpbms6aHJlZj0iI01KWC00Mi1URVgtTi0yRSIgdHJhbnNmb3JtPSJ0cmFuc2xhdGUoNTAwLDApIj48L3VzZT48dXNlIGRhdGEtYz0iMzEiIHhsaW5rOmhyZWY9IiNNSlgtNDItVEVYLU4tMzEiIHRyYW5zZm9ybT0idHJhbnNsYXRlKDc3OCwwKSI+PC91c2U+PHVzZSBkYXRhLWM9IjM1IiB4bGluazpocmVmPSIjTUpYLTQyLVRFWC1OLTM1IiB0cmFuc2Zvcm09InRyYW5zbGF0ZSgxMjc4LDApIj48L3VzZT48L2c+PGcgZGF0YS1tbWwtbm9kZT0ibW8iIHRyYW5zZm9ybT0idHJhbnNsYXRlKDIwMDAuMiwwKSI+PHVzZSBkYXRhLWM9IkQ3IiB4bGluazpocmVmPSIjTUpYLTQyLVRFWC1OLUQ3Ij48L3VzZT48L2c+PGcgZGF0YS1tbWwtbm9kZT0ibXN1cCIgdHJhbnNmb3JtPSJ0cmFuc2xhdGUoMzAwMC40LDApIj48ZyBkYXRhLW1tbC1ub2RlPSJtbiI+PHVzZSBkYXRhLWM9IjMxIiB4bGluazpocmVmPSIjTUpYLTQyLVRFWC1OLTMxIj48L3VzZT48dXNlIGRhdGEtYz0iMzAiIHhsaW5rOmhyZWY9IiNNSlgtNDItVEVYLU4tMzAiIHRyYW5zZm9ybT0idHJhbnNsYXRlKDUwMCwwKSI+PC91c2U+PC9nPjxnIGRhdGEtbW1sLW5vZGU9IlRlWEF0b20iIHRyYW5zZm9ybT0idHJhbnNsYXRlKDEwMzMsMzkzLjEpIHNjYWxlKDAuNzA3KSIgZGF0YS1tangtdGV4Y2xhc3M9Ik9SRCI+PGcgZGF0YS1tbWwtbm9kZT0ibWkiPjx1c2UgZGF0YS1jPSIxRDQ1QiIgeGxpbms6aHJlZj0iI01KWC00Mi1URVgtSS0xRDQ1QiI+PC91c2U+PC9nPjwvZz48L2c+PC9nPjwvZz48L3N2Zz4=)

### Exponents

Syntax: `300\mathrm{m}^2`

Output: ![](data:image/svg+xml;base64,PHN2ZyBzdHlsZT0ib3ZlcmZsb3c6IHZpc2libGU7IHZlcnRpY2FsLWFsaWduOiAtMC4wNWV4OyIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB3aWR0aD0iNi4yNjZleCIgaGVpZ2h0PSIxLjkzN2V4IiByb2xlPSJpbWciIGZvY3VzYWJsZT0iZmFsc2UiIHZpZXdCb3g9IjAgLTgzMy45IDI3NjkuNiA4NTUuOSIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiPgogICAgICA8ZGVmcz4KICAgICAgICA8c3R5bGU+CiAgICAgICAgICBnW2ZpbGw9ImN1cnJlbnRDb2xvciJdIHsgZmlsbDogIzAwMDAwMDsgfQogICAgICAgICAgW3N0cm9rZT0iY3VycmVudENvbG9yIl0geyBzdHJva2U6ICMwMDAwMDA7IH0KICAgICAgICAgIGdbZmlsbD0id2hpdGUiXSB7IGZpbGw6ICNGRkZGRkY7IH0KICAgICAgICAgIFtzdHJva2U9IndoaXRlIl0geyBzdHJva2U6ICNGRkZGRkY7IH0KICAgICAgICAgIGdbZmlsbD0iYmxhY2siXSB7IGZpbGw6ICMwMDAwMDA7IH0KICAgICAgICAgIFtzdHJva2U9ImJsYWNrIl0geyBzdHJva2U6ICMwMDAwMDA7IH0KICAgICAgICA8L3N0eWxlPgogICAgICA8L2RlZnM+CiAgICA8ZGVmcz48cGF0aCBpZD0iTUpYLTIxLVRFWC1OLTMzIiBkPSJNMTI3IDQ2M1ExMDAgNDYzIDg1IDQ4MFQ2OSA1MjRRNjkgNTc5IDExNyA2MjJUMjMzIDY2NVEyNjggNjY1IDI3NyA2NjRRMzUxIDY1MiAzOTAgNjExVDQzMCA1MjJRNDMwIDQ3MCAzOTYgNDIxVDMwMiAzNTBMMjk5IDM0OFEyOTkgMzQ3IDMwOCAzNDVUMzM3IDMzNlQzNzUgMzE1UTQ1NyAyNjIgNDU3IDE3NVE0NTcgOTYgMzk1IDM3VDIzOCAtMjJRMTU4IC0yMiAxMDAgMjFUNDIgMTMwUTQyIDE1OCA2MCAxNzVUMTA1IDE5M1ExMzMgMTkzIDE1MSAxNzVUMTY5IDEzMFExNjkgMTE5IDE2NiAxMTBUMTU5IDk0VDE0OCA4MlQxMzYgNzRUMTI2IDcwVDExOCA2N0wxMTQgNjZRMTY1IDIxIDIzOCAyMVEyOTMgMjEgMzIxIDc0UTMzOCAxMDcgMzM4IDE3NVYxOTVRMzM4IDI5MCAyNzQgMzIyUTI1OSAzMjggMjEzIDMyOUwxNzEgMzMwTDE2OCAzMzJRMTY2IDMzNSAxNjYgMzQ4UTE2NiAzNjYgMTc0IDM2NlEyMDIgMzY2IDIzMiAzNzFRMjY2IDM3NiAyOTQgNDEzVDMyMiA1MjVWNTMzUTMyMiA1OTAgMjg3IDYxMlEyNjUgNjI2IDI0MCA2MjZRMjA4IDYyNiAxODEgNjE1VDE0MyA1OTJUMTMyIDU4MEgxMzVRMTM4IDU3OSAxNDMgNTc4VDE1MyA1NzNUMTY1IDU2NlQxNzUgNTU1VDE4MyA1NDBUMTg2IDUyMFExODYgNDk4IDE3MiA0ODFUMTI3IDQ2M1oiPjwvcGF0aD48cGF0aCBpZD0iTUpYLTIxLVRFWC1OLTMwIiBkPSJNOTYgNTg1UTE1MiA2NjYgMjQ5IDY2NlEyOTcgNjY2IDM0NSA2NDBUNDIzIDU0OFE0NjAgNDY1IDQ2MCAzMjBRNDYwIDE2NSA0MTcgODNRMzk3IDQxIDM2MiAxNlQzMDEgLTE1VDI1MCAtMjJRMjI0IC0yMiAxOTggLTE2VDEzNyAxNlQ4MiA4M1EzOSAxNjUgMzkgMzIwUTM5IDQ5NCA5NiA1ODVaTTMyMSA1OTdRMjkxIDYyOSAyNTAgNjI5UTIwOCA2MjkgMTc4IDU5N1ExNTMgNTcxIDE0NSA1MjVUMTM3IDMzM1ExMzcgMTc1IDE0NSAxMjVUMTgxIDQ2UTIwOSAxNiAyNTAgMTZRMjkwIDE2IDMxOCA0NlEzNDcgNzYgMzU0IDEzMFQzNjIgMzMzUTM2MiA0NzggMzU0IDUyNFQzMjEgNTk3WiI+PC9wYXRoPjxwYXRoIGlkPSJNSlgtMjEtVEVYLU4tNkQiIGQ9Ik00MSA0Nkg1NVE5NCA0NiAxMDIgNjBWNjhRMTAyIDc3IDEwMiA5MVQxMDIgMTIyVDEwMyAxNjFUMTAzIDIwM1ExMDMgMjM0IDEwMyAyNjlUMTAyIDMyOFYzNTFROTkgMzcwIDg4IDM3NlQ0MyAzODVIMjVWNDA4UTI1IDQzMSAyNyA0MzFMMzcgNDMyUTQ3IDQzMyA2NSA0MzRUMTAyIDQzNlExMTkgNDM3IDEzOCA0MzhUMTY3IDQ0MVQxNzggNDQySDE4MVY0MDJRMTgxIDM2NCAxODIgMzY0VDE4NyAzNjlUMTk5IDM4NFQyMTggNDAyVDI0NyA0MjFUMjg1IDQzN1EzMDUgNDQyIDMzNiA0NDJRMzUxIDQ0MiAzNjQgNDQwVDM4NyA0MzRUNDA2IDQyNlQ0MjEgNDE3VDQzMiA0MDZUNDQxIDM5NVQ0NDggMzg0VDQ1MiAzNzRUNDU1IDM2Nkw0NTcgMzYxTDQ2MCAzNjVRNDYzIDM2OSA0NjYgMzczVDQ3NSAzODRUNDg4IDM5N1Q1MDMgNDEwVDUyMyA0MjJUNTQ2IDQzMlQ1NzIgNDM5VDYwMyA0NDJRNzI5IDQ0MiA3NDAgMzI5UTc0MSAzMjIgNzQxIDE5MFYxMDRRNzQxIDY2IDc0MyA1OVQ3NTQgNDlRNzc1IDQ2IDgwMyA0Nkg4MTlWMEg4MTFMNzg4IDFRNzY0IDIgNzM3IDJUNjk5IDNRNTk2IDMgNTg3IDBINTc5VjQ2SDU5NVE2NTYgNDYgNjU2IDYyUTY1NyA2NCA2NTcgMjAwUTY1NiAzMzUgNjU1IDM0M1E2NDkgMzcxIDYzNSAzODVUNjExIDQwMlQ1ODUgNDA0UTU0MCA0MDQgNTA2IDM3MFE0NzkgMzQzIDQ3MiAzMTVUNDY0IDIzMlYxNjhWMTA4UTQ2NCA3OCA0NjUgNjhUNDY4IDU1VDQ3NyA0OVE0OTggNDYgNTI2IDQ2SDU0MlYwSDUzNEw1MTAgMVE0ODcgMiA0NjAgMlQ0MjIgM1EzMTkgMyAzMTAgMEgzMDJWNDZIMzE4UTM3OSA0NiAzNzkgNjJRMzgwIDY0IDM4MCAyMDBRMzc5IDMzNSAzNzggMzQzUTM3MiAzNzEgMzU4IDM4NVQzMzQgNDAyVDMwOCA0MDRRMjYzIDQwNCAyMjkgMzcwUTIwMiAzNDMgMTk1IDMxNVQxODcgMjMyVjE2OFYxMDhRMTg3IDc4IDE4OCA2OFQxOTEgNTVUMjAwIDQ5UTIyMSA0NiAyNDkgNDZIMjY1VjBIMjU3TDIzNCAxUTIxMCAyIDE4MyAyVDE0NSAzUTQyIDMgMzMgMEgyNVY0Nkg0MVoiPjwvcGF0aD48cGF0aCBpZD0iTUpYLTIxLVRFWC1OLTMyIiBkPSJNMTA5IDQyOVE4MiA0MjkgNjYgNDQ3VDUwIDQ5MVE1MCA1NjIgMTAzIDYxNFQyMzUgNjY2UTMyNiA2NjYgMzg3IDYxMFQ0NDkgNDY1UTQ0OSA0MjIgNDI5IDM4M1QzODEgMzE1VDMwMSAyNDFRMjY1IDIxMCAyMDEgMTQ5TDE0MiA5M0wyMTggOTJRMzc1IDkyIDM4NSA5N1EzOTIgOTkgNDA5IDE4NlYxODlINDQ5VjE4NlE0NDggMTgzIDQzNiA5NVQ0MjEgM1YwSDUwVjE5VjMxUTUwIDM4IDU2IDQ2VDg2IDgxUTExNSAxMTMgMTM2IDEzN1ExNDUgMTQ3IDE3MCAxNzRUMjA0IDIxMVQyMzMgMjQ0VDI2MSAyNzhUMjg0IDMwOFQzMDUgMzQwVDMyMCAzNjlUMzMzIDQwMVQzNDAgNDMxVDM0MyA0NjRRMzQzIDUyNyAzMDkgNTczVDIxMiA2MTlRMTc5IDYxOSAxNTQgNjAyVDExOSA1NjlUMTA5IDU1MFExMDkgNTQ5IDExNCA1NDlRMTMyIDU0OSAxNTEgNTM1VDE3MCA0ODlRMTcwIDQ2NCAxNTQgNDQ3VDEwOSA0MjlaIj48L3BhdGg+PC9kZWZzPjxnIHN0cm9rZT0iY3VycmVudENvbG9yIiBmaWxsPSJjdXJyZW50Q29sb3IiIHN0cm9rZS13aWR0aD0iMCIgdHJhbnNmb3JtPSJzY2FsZSgxLC0xKSI+PGcgZGF0YS1tbWwtbm9kZT0ibWF0aCI+PGcgZGF0YS1tbWwtbm9kZT0ibW4iPjx1c2UgZGF0YS1jPSIzMyIgeGxpbms6aHJlZj0iI01KWC0yMS1URVgtTi0zMyI+PC91c2U+PHVzZSBkYXRhLWM9IjMwIiB4bGluazpocmVmPSIjTUpYLTIxLVRFWC1OLTMwIiB0cmFuc2Zvcm09InRyYW5zbGF0ZSg1MDAsMCkiPjwvdXNlPjx1c2UgZGF0YS1jPSIzMCIgeGxpbms6aHJlZj0iI01KWC0yMS1URVgtTi0zMCIgdHJhbnNmb3JtPSJ0cmFuc2xhdGUoMTAwMCwwKSI+PC91c2U+PC9nPjxnIGRhdGEtbW1sLW5vZGU9Im1zdXAiIHRyYW5zZm9ybT0idHJhbnNsYXRlKDE1MDAsMCkiPjxnIGRhdGEtbW1sLW5vZGU9IlRlWEF0b20iIGRhdGEtbWp4LXRleGNsYXNzPSJPUkQiPjxnIGRhdGEtbW1sLW5vZGU9Im1pIj48dXNlIGRhdGEtYz0iNkQiIHhsaW5rOmhyZWY9IiNNSlgtMjEtVEVYLU4tNkQiPjwvdXNlPjwvZz48L2c+PGcgZGF0YS1tbWwtbm9kZT0ibW4iIHRyYW5zZm9ybT0idHJhbnNsYXRlKDg2NiwzNjMpIHNjYWxlKDAuNzA3KSI+PHVzZSBkYXRhLWM9IjMyIiB4bGluazpocmVmPSIjTUpYLTIxLVRFWC1OLTMyIj48L3VzZT48L2c+PC9nPjwvZz48L2c+PC9zdmc+)

![image-20241115-074959.png](https://help.narva.net/__attachments/a_88a6a7280bd692380bd96545f62a9daacb084ecd89d92de9cefc76f65201f07d/image-20241115-074959.png?cb=937a2069155d0cf039b69a1992f03553)
LaTeX Math for Confluence unit example

For complete examples, please refer to MathJax reference documentation.

---
language: "en"
---
# Math Formula & Equations in Confluence

You can use **TeX** (LaTeX) syntax to write math formulas and equations in Confluence pages with [**LaTeX Math for Confluence**](https://marketplace.atlassian.com/apps/1226109/latex-math-for-confluence-math-formula-equations?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=math_formula)app by Narva Software.

Once [**installation**](https://help.narva.net/latex-math-for-confluence.md) is complete, you can go to any Confluence page and add mathematical content.

Follow this step-by-step guide:

1. Open Confluence page editor or create a new page

2. Type **/math to open Math macros** from the app and select one (see screenshot below)

3. Enter the math formula in TeX syntax and hit enter or save

That's it. Your formula will be beautifully rendered in the page.

The app has **two macros** which can be used according to your needs.  
![image-20241115-084017.png](https://help.narva.net/__attachments/a_806429b567f55acc5adb1a67206e62bafabba2eeab70b59a099a84294dc410ab/image-20241115-084017.png?cb=628d22f7ad973537d04f20d672153b2f)
LaTeX Math for Confluence Macros

## Easy Math - LaTeX Inline

This inline macro allows embedding math formula inline next to other content. This is handy for short expressions and units.  
![LaTex Easy Math Inline.gif](https://help.narva.net/__attachments/a_edaca905be00494f81ca45749379b16794cad36ad1b5d9da3ed73b05793add25/LaTex%20Easy%20Math%20Inline.gif?cb=89e967ac5303cba8b2e3bb07e9ccd0c1)

### Easy Math - LaTeX Block

As the name suggests, it renders formula in new block, creates newline and gives user the ability to adjust alignment in the page. This is a recommended macro for large equations and expressions.

![LaTex Block GIF-20241118-042417.gif](https://help.narva.net/__attachments/a_a30cbec2702981da33325d0540e42213a295fdfad92d04d30a90865aca8faa4d/LaTex%20Block%20GIF-20241118-042417.gif?cb=f443fe62cfa2f00d9b24c8120c1bfe36)
LaTeX Math for Confluence Block Macro

If you find any issues while using the app, please refer to our [Troubleshooting Guide](https://help.narva.net/latex-math-for-confluence/troubleshooting-guide.md)

---
language: "en"
---
# Migrate LaTeX from Confluence DC or Server to Cloud

If you have an LaTeX based app for math formula in Confluence Server or Data Center (DC), you can seamlessly migrate the data to cloud app [**LaTeX Math for Confluence - Math Formula \& Equations**](https://marketplace.atlassian.com/apps/1226109/latex-math-for-confluence-math-formula-equations?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=migration)

These apps are supported out of the box:

1. **Mathjax** by Keysight Technologies

These apps can be migrated following the migration process:

1. **LaTeX and Mathjax** by The Plugin People

2. **LaTeX Math** by Appfire

Other apps are also supported using the advanced migration feature, please contact our support team 💌 [support@narva.net](mailto:support@narva.net) for a quick assessment.

## Migration Steps

The migration process involves two steps.

1. Migrate Confluence DC/Server to Cloud

2. Migrate LaTeX based formula to our app **LaTeX Math for Confluence**

### 1. Migrate DC/Server to Confluence Cloud

You can use Atlassian Migration Assistant to migrate all data from DC/Server to Cloud. Atlassian has extensive documentation about this tool here: [Confluence Cloud Migration Assistant](https://support.atlassian.com/migration/docs/what-is-confluence-cloud-migration-assistant/)  
The important thing in this step is to **NOT include LaTeX app** in the migration. That is because these apps store data in the page itself and when a space is migrated, app data is also migrated to cloud.

You can mark these apps as '**Not needed in the cloud**' on assessment window. Again, this is because macro data from these apps is part of the page where they are inserted and will be included in the parent space migration.  
![Migration-Apps-Assessment-I.png](https://help.narva.net/__attachments/a_0a23928b39e03c846f157d1b5ee4b38989e02b3d0636c6ae03f575129ff05323/Migration-Apps-Assessment-I.png?cb=5f59b53fb1f1848a8f978b06796b6c5b)
Migration to cloud app assessment  
![Migration-Sellect-Apps.png](https://help.narva.net/__attachments/a_fb6654f22589329211d0474cd8163889ca232eebd18e40549dd30363eee0ba17/Migration-Sellect-Apps.png?cb=11d5c5be92179074e36feb35e8327091)
Migration to cloud app selection

These are the only important parameters in the migration process. Once migration is run, you can go to the cloud site, and it should display 'unknown macro' message in the pages where formula were included.  
![Migration-unknown-macro.png](https://help.narva.net/__attachments/a_88790948b1bf2321dac9ae1f78d502c8a57c9f2307deef2c3ed9d03a1c2b8299/Migration-unknown-macro.png?cb=c451cd0085899bab0f3aeef512e4a993)
Confluence page migrated from DC/Server

This is expected as the apps are not included. You can now proceed to next step in the migration process.

### 2. Migrate LaTeX based formula to **LaTeX Math for Confluence**

You can migrate these formulas to **LaTeX Math for Confluence** using the built-in migration feature. This feature can also be used to migrate from another cloud app.

* Install the app from Marketplace: [**LaTeX Math for Confluence - Math Formula \& Equations**](https://marketplace.atlassian.com/apps/1226109/latex-math-for-confluence-math-formula-equations?hosting=cloud&tab=overview)

* Go to Confluence Administration → LaTeX Math for Confluence → Migration from other apps

* Select the source app and macro types to migrate them one by one

![Migration-from-other-apps.png](https://help.narva.net/__attachments/a_0e0b518d4568c8765f46dbe4ba003550a543eac77cce7785cbd6c07e8db6afef/Migration-from-other-apps.png?cb=204a2714716685fed20ba56488808370)
Migrate LaTeX formula to LaTeX Math for Confluence

You can find all the pages and spaces where formula are included in Confluence Administration → Data Management → Macro Usage.  
**Restricted Pages**

If you have restricted (private) pages, migration does not work because the app cannot find those pages. To migrate restricted pages, you need to add both the **user doing the migration** and the **app user (LaTeX Math for Confluence)** to those pages.

* On top right, click on 🔐 share

* Find users and share

Please note, **it also does not work** if you are logged in with **admin key**. These pages need to be accessible to you without using admin key.

If you need any help before, during and after the migration, please feel free to reach out to us at 💌 [support@narva.net](mailto:support@narva.net)

---
language: "en"
---
# Troubleshooting Guide

[**LaTeX Math for Confluence**](https://marketplace.atlassian.com/apps/1226109/latex-math-for-confluence-math-formula-equations?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=troubleshooting) has known issues and possible workaround. Please go through this list before raising a support ticket.

## 1. Formula is not rendered, just shows black

When entering TeX formula, you might sometimes see black box instead of rendered formula like below:  
![latex-math-black-box.png](https://help.narva.net/__attachments/a_da3a6c6abe25249682ebe94cb08fe6fb44721f3db102545db629a16e0b575a31/latex-math-black-box.png?cb=a21a5fe108b03af4845a403ec07a8491)
Math macro render issue

This is most likely caused by unsupported or wrong syntax. You can test the TeX syntax in official MathJax demo <https://www.mathjax.org/#demo> which gives better error message.  
Unlike in the app, you need to wrap TeX with $$ symbols in MathJax demo!

You can also refer to complete reference here: <https://math.meta.stackexchange.com/questions/5020/mathjax-basic-tutorial-and-quick-reference/27212>

### 2. Line break / multi-line equations

If you need to add newline/line break in equations, you can use `\displaylines` for this purpose.

For example:

    \displaylines{x = a + b \\ y = b + c}

It will be displayed as:  
![LeTeX-Math-line-break.png](https://help.narva.net/__attachments/a_aea1a585a9ecefd04c88c2daaf0faf41bf5114e3a29b5e570cf876e0d5e5dc09/LeTeX-Math-line-break.png?cb=5825118966d08d97ef482f770d88e15d)
LaTeX Math for Confluence line break example

---
language: "en"
---
# v2.0 Runs on Atlassian

**Version**: 2.0.0

**Release date** : 2025-10-27

We have migrated **LaTeX Math for Confluence** to [**Forge**](https://community.developer.atlassian.com/), the Atlassian hosted app development platform, and released a new major version. Until now, this app was using Atlassian Connect framework.

## Features

The new platform enables some compelling features, especially when it comes to data security:

1. **Runs on Atlassian** : The app now qualifies for **Runs on Atlassian** badge, and this is already reflected in the Marketplace listing.

2. **Dark Mode Support**: It now supports Confluence dark mode, and LaTeX formula will be properly rendered when dark mode is enabled.

### Runs on Atlassian

Runs on Atlassian badge means this app is 100% hosted within Atlassian Cloud, in the same environment as Confluence.

* No data egress permissions outside Atlassian Cloud

* Hosted in Atlassian Cloud and data stored fully within Atlassian environment

* Data residency compliant

### Limitations

As a major platform upgrade, there are unfortunately some new issues that users need to be aware.

1. **Public pages (anonymous users)**

This issue is now fixed!

This app currently does not support public pages, which are open to users not logged into Confluence. Atlassian has communicated that they will fix [this issue](https://jira.atlassian.com/browse/CONFCLOUD-80208) by Nov, 2025.

Until then, if you are using the app to write public documentation, please do not upgrade and continue to use versions \< 2.0 which are fully functional.

2. **Export to Microsoft Word**

Exporting to Word is currently not supported out of the box. This is a limitation in Confluence Word export feature, as it still uses the very old .doc format instead of the standard, widely compatible .docx format.

To work around this issue, we have released a new FREE app: [Advanced Word (Docx) Exporter for Confluence](https://marketplace.atlassian.com/apps/156764753/advanced-word-docx-exporter-for-confluence?hosting=cloud&tab=overview) and suggest users to install this app instead of relying on the default Confluence export.

### Upgrading to v2.0

As this is a major version, Confluence admins need to manually upgrade it from Atlassian Admin. We have enabled automatic upgrade for customers who were on v1.2.4-AC.

If you are using an older version of the app, you need to manually upgrade.

In order to upgrade to the latest version:

1. Go to admin.atlassian.com

2. Select Apps → Platform Experiences → Sites (select your instance) → Connected apps

3. Find the app and upgrade

---
language: "en"
---
# HTML Macro for Confluence

[**HTML Macro for Confluence**](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=overview) is an add-on which allows users to add custom contents using HTML, CSS and Javascript in **Confluence** **Cloud**. It is also very handy when one needs to embed external web pages, forms, charts etc. as iframe.

## Install

If you haven't installed it, please install from Atlassian Marketplace here: [https://marketplace.atlassian.com/apps/1221472](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=overview)

### User Guide

Once installed, open the macro browser and select **HTML and Iframe Embed** macro (or simply type**/html** to open it).

Click on edit icon, and it should open the following window where you can enter your code. It accepts standard HTML, CSS and Javascript. If you have external iframe code, just copy and paste it in the text box.

Here are some example use cases:

#### Example 1: Add custom content using HTML, CSS and Javascript

![html-iframe-macro.png](https://help.narva.net/__attachments/a_ddc36a835de31196293f80f872584ab0a2ce85eb94a9cc3eef46edecf888e428/html-iframe-macro.png?cb=bc1652f0718acb8dcae1efa6e4199e56)

You can enter standard HTML document. It also accepts CSS for styling and Javascript for custom functionalities.

#### Example 2: Embed Google Forms

First, create form in Google Forms and copy iframe code which you can find by clicking send or share button.  
![google-form.png](https://help.narva.net/__attachments/a_4adf8c97ce21605fad5cd1cec8c68036d671e783baab16cceaa31d4978c86424/google-form.png?cb=46bed49d129ada83817941cf02af31c7)

Open **HTML \& Iframe Embed** in Confluence and enter the copied Iframe code in text box.  
![iframe-macro.png](https://help.narva.net/__attachments/a_d2ca4f63b9feb59df0e0682139466ddcf61b2b7ccbb831c2ab0265a951a6f3f5/iframe-macro.png?cb=3d707c0a85390d09a072cbcf407ce255)

Save and **don't forget to publish it**. Your Google form will be beautifully rendered in Confluence.  
![google-from-rendered.png](https://help.narva.net/__attachments/a_bbb49524c539644d06b726d401d02d1cc7137ffc26fd725070a14e7b77c3ea9b/google-from-rendered.png?cb=a6a95341cabd4b27ef525e8b2ee887b1)

That's it. Now users can fill the form without leaving Confluence. Their responses will be saved in Google Form.

#### Other Examples

For other usage examples, please check out Confluence space:

[HTML Macro for Confluence Examples](https://narva.atlassian.net/wiki/spaces/bit/pages/436568065/HTML+Macro+for+Confluence+Examples)

Or other usage specific guides:  
* [HTML Macro Security](https://help.narva.net/html-macro-for-confluence/html-macro-security.md)
* [Embed iframe in Confluence](https://help.narva.net/html-macro-for-confluence/embed-iframe-in-confluence.md)
* [Embed Google Sheets in Confluence](https://help.narva.net/html-macro-for-confluence/embed-google-sheets-in-confluence.md)
* [Embed HTML file in Confluence](https://help.narva.net/html-macro-for-confluence/embed-html-file-in-confluence.md)
* [Migrate HTML Macro from Confluence Server or DC to Cloud](https://help.narva.net/html-macro-for-confluence/migrate-confluence-html-macro-from-server-or-dc-to.md)
* [Common Issues and Limitations](https://help.narva.net/html-macro-for-confluence/common-issues-and-limitations.md)
* [HTML Macro Changelog](https://help.narva.net/html-macro-for-confluence/changelog.md)

---
language: "en"
---
# HTML Macro Changelog

Major updates and improvements in the **HTML Macro for Confluence** app are documented below.  
Please note that for major versions, admins need to manually upgrade the app.

## Upgrade to Latest Version

Go to Confluence **Settings** → **Atlassian Marketplace** → **Manage apps** (you might be redirected to Connected apps page in Atlassian admin)

Alternatively, use Atlassian Administration:

1. Go to [++admin.atlassian.com++](http://admin.atlassian.com/)

2. Select Apps → Platform Experiences → Sites (select your instance) → Connected apps

3. Find the app and upgrade

Minor version updates are automatically applied to all instances.

### v3.1 Fix for HTML Form Submissions

Version: v3.1.0

**Release date** : 2026-04-28

More details: [v3.1 Fix for HTML Form Submissions](https://help.narva.net/html-macro-for-confluence/v3-1-fix-for-html-form-submissions.md)

### v3.0 Fix for Links in Iframe Embed

Version: v3.0.0

**Release date** : 2026-04-03

More details: [v3.0 Fix for Links in Iframe Embed](https://help.narva.net/html-macro-for-confluence/v3-0-fix-for-links-in-iframe-embed.md)

### v2.0 Migration to Atlassian Forge

Version: v2.0.0

**Release date** : 2026-03-25

More details: [v2.0 Migration to Atlassian Forge](https://help.narva.net/html-macro-for-confluence/v2-0-migration-to-atlassian-forge.md)

---
language: "en"
---
# Common Issues and Limitations

These are common issues in HTML Macro for Confluence. Whenever possible, issues also have documented workaround to resolve them.

## HTML from Page Attachment: 404 Not Found

When you use **HTML from Page Attachment** macro to render an HTML file, you might sometimes encounter **404 Attachment Not Found** error.  
![HTML-Attachement-Not-Found.png](https://help.narva.net/__attachments/a_663a559f166910f0e5e125b9e5ac5336cc6113cae758d7aa1e4fb7295df2faf8/HTML-Attachement-Not-Found.png?cb=1ac5647a3d20dd5cf1128caca6c8139d)
Page attachment not found

There are multiple causes behind this issue, some of them are:

1. Page permissions

2. Site rename (changing Confluence URL)

### Page Permissions

You can inspect the page permission with following steps:

Go to page and click on Restrictions icon 🔓  
![HTML-Page-Permissions.png](https://help.narva.net/__attachments/a_5057ef0207ed5103d63f74027c34863b117d3bc3e3916b599aac6817a0e896d4/HTML-Page-Permissions.png?cb=3c1fbff09f3ec8fa7aaeceff08ec7561)

2. Click on Inspect permissions

![Inspect-Permissions.png](https://help.narva.net/__attachments/a_b6f479c3ac3c37f0e32bc04023c7986e1b862b92b7e7293c686dcde068995045/Inspect-Permissions.png?cb=2f993602b48eff549c73516f8ae929e9)

3. Select 'HTML \& Iframe Macro for Confluence'. The result should look like below.

![Inspect-Permissions-Detail.png](https://help.narva.net/__attachments/a_3cca0a6d6c25c9e2a956c57dc48b6a41bab027c6b77152a9cb938d60a690a76c/Inspect-Permissions-Detail.png?cb=a647d475a34551694b26d2fd0e8b343d)

If there is page permission **Denied** ![cross mark](https://help.narva.net/__attachments/a_e17bf0e022246a37c8f59523a3e1c190b09766088793b4be6f31fc3c3272b8ae/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) shown here, the app cannot access the page attachments as expected.

**In order to resolve this issue** , you can add app user to space from **Space Settings → Space permissions → Users**  
![Space-Permissions.png](https://help.narva.net/__attachments/a_a2edc13d8e583fb567a20122760a318aed235241e81a3cb5a74c9b1832022ea8/Space-Permissions.png?cb=540e177dee2f90c03cabdb2fc1684460)
Add HTML Macro to a space

The app needs only **view** permission to function, write permissions like add and delete are not needed.

This workaround is only needed if you have a customized permission system. By default, HTML Macro has read permissions and works out of the box.

If this still does not resolve, please contact us with a screenshot of Inspect permissions page (step 3).

### Site rename (changing Confluence URL)

We have noticed in **some rare cases** this issue occurs if you change your Confluence URL. If you have changed Confluence URL after the app was installed, sometimes apps don't get updated URL.

In this case, you can simply reinstall the app. Any data stored and used in the app is not affected, so this is a safe operation to do without causing any data loss.

### Empty frame in Safari and Firefox

Some browsers (e.g. Firefox, Safari) display empty frames in the macro when the whitelisting feature is enabled.  
![image-20241018-054422.png](https://help.narva.net/__attachments/a_bfb6948ea643ebc4d8239bc2d226aa7960ab3fbd4940e7651d179990b0528b5e/image-20241018-054422.png?cb=624e94b82073c12f29bc592035fc0bf3)
Empty frame

The most likely cause is that the embedded domain names are not in allowlist. In order to register it, please follow the steps or ask your Jira admin to follow the steps here: [HTML Macro Security \| Enable Whitelist Feature and Add Domains to the Whitelist](https://help.narva.net/html-macro-for-confluence/html-macro-security.md#Enable-Whitelist-Feature-and-Add-Domains-to-the-Whitelist).

---
language: "en"
---
# Embed Google Sheets in Confluence

Using the [**HTML Macro for Confluence**](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=google_sheets), you can embed Google Sheets directly in Confluence pages.

You can install the app from Atlassian Marketplace: [**HTML Macro for Confluence**](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=google_sheets)

Steps to embed Google Sheets in Confluence:

## Get embed code from Google Sheets

1. Go to Google Sheets and find the sheet you want to embed

2. Go to **File → Share → Publish to web** and click **Publish**

3. Once published, a new tab name embed is shown.

   ![google-sheets-embed-code.png](https://help.narva.net/__attachments/a_8b680595d6148b3e5f476f02833e0ac22f163cbf2377beb834cf7e9c3232ee8f/google-sheets-embed-code.png?cb=d4c982e6132170ac47317b1a709ab67d)
   Google Sheets embed code
4. Copy the shown embed code

### Use the embed code in Confluence page

1. Go to page editor and type **/html** to open **HTML \& Iframe Embed** macro.

2. Paste the embed code in the code block:

![image-20241018-105142.png](https://help.narva.net/__attachments/a_2285ceba3540b343960f2c9323b68d173f6a4723d57a426bc76f39142d0c5141/image-20241018-105142.png?cb=d9df01b5d2cbf0a91d86b16e611530b7)
Google Sheets iframe embed in Confluence page

Finally, save the macro and Google Sheets will be embedded in the Confluence page.

Depending on the size of sheet contents, you can also adjust iframe parameters like height and width like below:
HTML

    <iframe src="https://docs.google.com/spreadsheets/d/e/2PACX-1vSvUniY5v36XbQuDtsJO8RX__KChbqhaotsE1ftdj-t63QQ82sdzzEspTI1fTaQQfxwuvyn2s3VkOv3/pubhtml?gid=0&amp;single=true&amp;widget=true&amp;headers=false"></iframe>

Please note that when a sheet is published to the web, people who have the link can access and view the contents of the sheet.

---
language: "en"
---
# Embed HTML file in Confluence

If you have HTML files and simply need to render them in Confluence, you can do that using the [**HTML Macro for Confluence**](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=html_file)app.

This Confluence app can be installed from Atlassian Marketplace here: [**HTML Macro for Confluence**](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=html_file)

If you have the app installed, follow these steps to render HTML file in Confluence:

1. Go to Confluence page editor

2. Upload HTML files as page attachments (click **Add image, video or file** ) from page editor menu. Alternatively, you can upload attachments without opening the page in edit mode from **Page** **Actions (...) → Attachments → Files**.

3. Enter /html to open **HTML from Page Attachment** macro

4. Select the HTML file from the attachments on the right.

![HTML-from-Attachment-I.png](https://help.narva.net/__attachments/a_126f5effb4e99f1d4bcc2a3e557bb45e1b0f1b9cd2ed552e819d99f4166138d5/HTML-from-Attachment-I.png?cb=6b7b56cd38391cc9abffc210959d3266)
Embed HTML in Confluence example

The HTML file should be rendered as expected. You can adjust the height of the content in pixel if it is not automatically resized.

Once this is complete, you can remove the attachments from the page editor as not to clutter the page. They are still available in Confluence as attachments and can be managed from **Page** **Actions (...) → Attachments → Files**.

**HTML from Page Attachment**is recommended for complex and large HTML files with Javascript and CSS code like charts and visualizations, animations, and self-contained web apps.

---
language: "en"
---
# Embed iframe in Confluence

Confluence has an iframe macro that can be used to embed static web pages, e.g. blog posts. However, it does not support complex web apps and widgets like slides, videos, forms, charts etc.

[HTML Macro for Confluence](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=iframe) is a versatile app that allows embedding any type of web contents using iframe.

You can install the app from Atlassian Marketplace: [**HTML Macro for Confluence**](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=iframe)

1. Find the iframe embed code from the source and copy it.

2. Go to page editor and type **/html** to open **HTML \& Iframe Embed** macro.

3. Enter the embed code in the code block:

![image-20241018-104507.png](https://help.narva.net/__attachments/a_2e015f5c8956371da195ebbde3b9c6a2f9c12954e78e0d91d3549402b1ec09e6/image-20241018-104507.png?cb=ef71a5fb2bdac57648cd2f9db88df8fc)
iframe embed example in Confluence

Finally, save the content and it should be embedded in Confluence page.

It is recommended to use the embed code from sources that you know and trust. That means popular platforms and apps like Google Forms, Sheets, Docs, Microsoft Forms, YouTube etc.

As an example, check out the **Slideshare** embed in action in our Confluence space here: [Embed SlideShare presentation in Confluence](https://narva.atlassian.net/wiki/spaces/bit/pages/547520542/Embed+SlideShare+presentation+in+Confluence)

---
language: "en"
---
# HTML Macro Security

**HTML Macro for Confluence** runs on **Forge** , a fully **Atlassian**-managed app platform.

* **Hosted on Atlassian infrastructure** --- the app runs entirely within Atlassian's Forge platform, with no third-party servers involved.

* **Data stored in Atlassian Cloud** --- all data is stored natively in Confluence or Forge storage. Nothing leaves your Atlassian Cloud instance.

* **Data residency compliant** --- the app respects your Confluence data residency.

You can check the release notes here: [v2.0 Migration to Atlassian Forge](https://help.narva.net/html-macro-for-confluence/v2-0-migration-to-atlassian-forge.md)

Additionally, Narva Software is **SOC 2 Type II** certified, which means our security controls have been independently audited.

[**HTML Macro for Confluence**](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=security) has built-in security features that allow Confluence admins to define trusted domains (whitelisting) to control data egress and script execution. When a domain whitelist/allowlist is defined, Confluence users will be restricted to only interact with trusted domains with HTML, JavaScript, and third-party Iframe embed code.

This makes **HTML Macro** versatile yet**very secure**for enterprise usage.

## Admin Guide

### Domain Whitelisting

As a Confluence admin, you can add a list of trusted domains to the whitelist. The app uses [Content Security Policy](https://content-security-policy.com/) to block any interactions outside these trusted domains. Specifically, it implements three Content Security Policy (CSP) directives:

`frame-src`: This CSP directive blocks embedding any domains via Iframe that are not added in allowlist.

For example, if a user tries to embed not-secure-site.com in Confluence, but the domain is not in the allow list, the embed will be blocked.

`connect-src`: This CSP directive blocks any attempt to connect (send request) to domains not in allowlist.

For example, the following request will be blocked as `attacker-site.io` is not in allowlist:
JavaScript

    fetch('https://attacker-site.io', {
        method: 'POST',
        body: JSON.stringify({ "content": "Foo" })
    })

`script-src`: This CSP directive prevents users from loading scripts coming from unsafe sources that are not defined as trusted domains.

For example, the following script will be not be loaded and executed if `code.jquery.com` is not added in allowlist.
HTML

    <script src="https://code.jquery.com/jquery-2.2.4.min.js"></script>

The browser will throw an error message in console like below (message can slightly differ based on browser):  
Content Security Policy: The page's settings blocked the loading of a resource at <https://code.jquery.com/jquery-2.2.4.min.js> ("script-src").

### Enable Whitelist Feature and Add Domains to the Whitelist

1. Go to **Top Nav** (right side) → **Settings**

2. Find **HTML Macro Configuration**section

3. Enable HTML macro whitelist by switching the toggle to on

4. Add domains (you can use wildcard syntax like \*.example.com)

![Screenshot 2024-10-18 at 13.03.57.png](https://help.narva.net/__attachments/a_6831fbd36a92aac3806ed7ce2b0dbe26a119fff3bc99903861a9d78c24efaf33/Screenshot%202024-10-18%20at%2013.03.57.png?cb=b1b5730c1fbd4daebdab052247058941)
HTML Macro for Confluence domain whitelisting

Once it's enabled, you can access the configuration from the macro:

1. Open the macro on the Confluence page

2. On the information banner, click **See allowed domains**

3. Click **Open allowlist setting**

Alternatively, you can also find the configuration page from: **Manage apps** → **HTML Macro for Confluence** →**Configure**.

### Enabling whitelist in existing macros

If your organization is already using **HTML Macro for Confluence**, please be careful when enabling the security feature. It can possibly break existing macros.

You can find the app/macro usage in Confluence from **Settings** → **Macro usage**. Review the usage and make sure to add used domains to the whitelist.

### Identify if the whitelist is enabled

As a user, you can use HTML Macro as documented in [https://narva.atlassian.net/wiki/spaces/HTML/overview](https://help.narva.net/html-macro-for-confluence.md). If domain allowlisting is enabled, the app shows a short notice in the yellow panel as below:  
![Screenshot 2024-10-18 at 13.10.25.png](https://help.narva.net/__attachments/a_7cf5bc7e4e382a6ad8829e1eff49f51d5c9908bef4f20b81bd44cf0443f49f45/Screenshot%202024-10-18%20at%2013.10.25.png?cb=a1fbc085fc941b3b65e0e18c3823b892)
HTML Macro for Confluence with security feature

If a domain is not added to the list, you can find the error on the Confluence page as below:  
![image-20240927-071656.png](https://help.narva.net/__attachments/a_b67ea90be7d5855d05562e48a7d0cc8662792310af2ffa33c22f8b9a1c929914/image-20240927-071656.png?cb=bece7150d8a127165e2d19fcd6f460c4)
Error when a domain is not in the allowlist

Please check with your admin if the domains are whitelisted.

You can also check the content security policy (CSP) errors in browser console. Here is an example error message when embedding Google Forms:  
Content Security Policy: The page's settings blocked the loading of a resource at <https://docs.google.com/forms/d/e/xxx/viewform?embedded=true> ("frame-src").

---
language: "en"
---
# Migrate HTML Macro from Confluence Server or DC to Cloud

If you are planning to migrate to Cloud from Confluence DC (Data Center ) or Server and currently use **HTML Macro** in the on-premise version, this page will guide you through the migration process.

HTML Macro is included in Confluence DC and Server, but not in Confluence Cloud. This is why we built an app: [**HTML Macro for Confluence**](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=migration)

This is the migration path for migrating HTML Macro from DC or Server to Cloud:

1. **Migrate Confluence from Data Center or Server**

2. **Install HTML Macro from Atlassian Marketplace**

The HTML Macro in Confluence Cloud is a bit limited compared to DC or Server versions. This is because apps in Confluence Cloud are by default sandboxed and rendered within their own iframe to make them secure. In on-premise versions, app macros are rendered in the same page context and have greater permissions.

That means the macros from on-premise are not 100% compatible. Therefore, we suggest users try the migration in a sandbox instance or test environment before doing it in production.

## Migrate Confluence from DC or Server

Atlassian has an excellent guide about migrating from DC or Server: <https://support.atlassian.com/migration/docs/cloud-migration-methods-for-confluence/>

In short, you can use Atlassian developed Cloud Migration Assistant tool and it does an excellent job.

In this step, you can simply not worry about HTML Macro as it is Confluence built-in macro, the contents of the macros will be automatically included in the migration.  
![migration-assistant.png](https://help.narva.net/__attachments/a_fb3ac00678c1d51d73a069773cb6471ee53b7ab6e864ee5e935a33923e8b4d1b/migration-assistant.png?cb=e06670fceebfb27b82b25d956cbb1a1c)
Confluence Cloud Migration Assistant

Once the migration is complete, you can now go to cloud site. You will notice that HTML Macro is displayed as `unknown macro: 'html'`.  
![html-macro-migration.png](https://help.narva.net/__attachments/a_221d6acb39acddace094a330446ae11f9e4f330b19765183f0804326e655ef6f/html-macro-migration.png?cb=b73d23cdf728334f1619f6af9eeac586)
HTML Macro in Confluence Cloud just after migration

## Install HTML Macro for Confluence

You can now go to the Atlassian Marketplace and install [**HTML Macro for Confluence**](https://marketplace.atlassian.com/apps/1221472/html-macro-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=migration)by Narva Software.

Simply click **Try it free** and follow the process. Give it some time, and once the installation is complete, go back to pages where HTML Macro was used.

HTML Macro migration to the cloud is complete 🎉  
![html-macro-migration-chart-example.png](https://help.narva.net/__attachments/a_f2ace5ef287b7010aef2d0613160b19db693816318139c306d8dc4a829c034a2/html-macro-migration-chart-example.png?cb=fc61cc836d9db42d9a101595b26260d6)
HTML Macro in Confluence Cloud after app installation

If you need any help, let us know. You might also be interested in [HTML Macro Security](https://help.narva.net/html-macro-for-confluence/html-macro-security.md)  
Need pre-migration consultation? Book a free call with our team here: [cal.com/narva](http://cal.com/narva)

---
language: "en"
---
# v2.0 Migration to Atlassian Forge

**Version**: v2.0.0

**Release date** : 2026-03-25

**HTML Macro for Confluence** by Narva Software is now migrated to [Atlassian Forge](https://developer.atlassian.com/platform/forge/introduction/the-forge-platform/). **Forge** is a fully managed app hosting and deployment platform by **Atlassian** as part of the wider Atlassian Cloud.

This is a significant platform upgrade which brings some major benefits to our users.  
Update on April 3, 2026: **App needs to be manually updated to \>= 3.0** , see [v3.0 Fix for Links in Iframe Embed](https://help.narva.net/html-macro-for-confluence/v3-0-fix-for-links-in-iframe-embed.md)

## Hosting and Data Storage

This app is now hosted on Forge platform, which means:

* App runs 100% within Atlassian Cloud platform

* Data stored and processed fully within Atlassian environment

* Data residency compliant

### Iframe Embed and Content Security Policy (CSP)

This app was previously hosted on Heroku platform. As such, the app URL was `html-addon-bitwelt.herokuapp.com`. If you are embedding some web contents using iframe, it is likely you have added our Heroku URL as allowed domain.

After this update, the app URL will change as it is now hosted on Atlassian Cloud.

You need to update allowed domains in Content Security Policy to:

* `*.atlassian-dev.net`

### Upgrading to v2.0.0

We have enabled automatic upgrade for customers who were on on `v.1.1.x`. In next few weeks, all customers on this version will be automatically upgraded to latest version.

If you are using older version of the app, Confluence admins need to manually upgrade the app.

1. Go to [admin.atlassian.com](http://admin.atlassian.com/)

2. Select Apps → Platform Experiences → Sites (select your instance) → Connected apps

3. Find the app and upgrade

---
language: "en"
---
# v3.0 Fix for Links in Iframe Embed

**Version**: v3.0.0

**Release date** : 2026-04-03

This version fixes an issue where links and buttons inside embedded iframes were unresponsive i.e. clicking them had no effect.

This affected customers who embed external pages or widgets (such as support portals or product pages) using the `<iframe>` tag in the macro.

## Upgrading to v3.0

Since this is a major version, admins need to manually upgrade the app.

To upgrade the app:

Go to Confluence **Settings** → **Atlassian Marketplace** → **Manage apps** (you might be redirected to Connected apps page in Atlassian admin)

Alternatively, use Atlassian Administration:

1. Go to [++admin.atlassian.com++](http://admin.atlassian.com/)

2. Select Apps → Platform Experiences → Sites (select your instance) → Connected apps

3. Find the app and upgrade

---
language: "en"
---
# v3.1 Fix for HTML Form Submissions

**Version**: v3.1.0

**Release date** : 2026-04-28

This version fixes an issue where HTML forms inside the macro were unable to submit to external domains. This was caused by a recent Atlassian platform change enforcing a `form-action 'self'` Content Security Policy (CSP) directive, which blocks native form submissions to external URLs.

The app now intercepts form submissions and re-sends them via `fetch()`, which is not restricted by the `form-action` directive.

## Requirement

Because the submission now travels as a `fetch()` request rather than a browser navigation, the target server must include the following CORS response header:

    Access-Control-Allow-Origin: *

We have created an example server with a form:

<https://nameless-fire-3e46.narva-software.workers.dev/>

You can use this to test form submission from HTML Macro in Confluence.

---
language: "en"
---
# Open API (Swagger) for Confluence

Build interactive API documentations hub in Confluence using OpenAPI specifications and Swagger UI.

## Install

You can install the app from Atlassian Marketplace: [**Open API (Swagger) for Confluence**](https://marketplace.atlassian.com/apps/1604251172/open-api-openapi-swagger-for-confluence?hosting=cloud&tab=overview&utm_source=help.narva.net&utm_medium=referral&utm_campaign=overview)

### User Guide

1. Open a Confluence page in edit mode

2. Type `/openapi` or click **+** → **OpenAPI - Swagger UI**

3. The macro will appear with a "Configuration Required" message

### Configuring OpenAPI Spec

There are two sources to configure OpenAPI in Confluence:

1. Write or paste OpenAPI specifications directly using the **in-app editor**

2. [Publish OpenAPI specifications from Bitbucket](https://help.narva.net/open-api-swagger-for-confluence/publish-openapi-specifications-from-bitbucket.md)

The second option is recommended as it will automatically sync the specifications from Bitbucket and will always be up-to-date.

**Using App Editor:**

1. Click the **pencil icon** on the macro to open the configuration panel

2. You'll see a split-pane editor:

   * **Left:** Write or paste your OpenAPI/Swagger specification (JSON or YAML)

   * **Right:** Live preview of your API documentation

3. Click **Load Sample** to see an example spec

4. Once your spec looks correct in the preview, click **Save**

![Screenshot 2025-11-26 at 23.51.12.png](https://help.narva.net/__attachments/a_82275ba98a8d315156468c599a3cbbaaf1c7b6f12eca4e0ed9947bd4c2df404f/Screenshot%202025-11-26%20at%2023.51.12.png?cb=512a326087d156adf84537a35996d934)
Open API edit and preview example in Confluence

### Supported Formats

| Format |     Example Start     |
|--------|-----------------------|
| YAML   | `openapi: 3.0.0`      |
| JSON   | `{"openapi": "3.0.0"` |

The editor auto-detects your format --- no configuration needed.

### Tips

* **Get your spec:** Export from tools like Swagger Editor, Postman, or your API framework

* **Large specs:** The macro handles full OpenAPI 3.x and Swagger 2.0 specifications

* **Multiple APIs:** Add multiple macros to document different services on one page

---
language: "en"
---
# Publish OpenAPI specifications from Bitbucket

If you use Git to version control your OpenAPI specifications, you can utilize Bitbucket repository as source to keep the API documentations in Confluence always in sync.

## Setup Bitbucket Access Tokens

In order to use Bitbucket as source, you need to set up access first. This app requires[repository access tokens](https://support.atlassian.com/bitbucket-cloud/docs/repository-access-tokens/).

**Create Access Token:**

1. Go to Bitbucket repository where OpenAPI specification is stored

2. Click **Repository settings** →**Security** →**Access tokens**

3. Create access token by giving name and expiry date (you need to renew this token once a year)

![Bitbucket-repo-access-token.png](https://help.narva.net/__attachments/a_bd7e2ce36182deda9b27d8139d53deae3db25b7f288d54e6f6b57bcdbdf96aec/Bitbucket-repo-access-token.png?cb=7a917e184575616a1574be2b69b7fa17)
Permission for Bitbucket repository access token

This app only requires repository **Read** permission, and this will be limited to the current repository. Once created, copy the access token and go back to app in Confluence.

**Save Access Token:**

You can now save the copied access token to app settings.

1. Go to Confluence **Administration** → **Apps** → OpenAPI Git/Bitbucket Integration

2. Give the access token readable a name and save the token

![Bitbucket-token-setting-1.png](https://help.narva.net/__attachments/a_8d2a874647cb934f6d3d4381d7cbd897ed7e0f7b39afd2fb87d73b8aadb23bdd/Bitbucket-token-setting-1.png?cb=65ecd81aab0bfdf62dd6a7e7fd7b216a)
Store Bitbucket access token in OpenAPI for Confluence app setting

Access tokens are encrypted and stored securely in Atlassian Forge secret store.

**Use Bitbucket as Source:**

Once setup is complete, you can go to a page and use the macro with Bitbucket as source.

1. Hit `/openapi` and select '**OpenAPI - Swagger UI**'

2. Select Bitbucket as source (and saved token by name). It should be able to find the OpenAPI specification file stored in Bitbucket

![Bitbucket-source.png](https://help.narva.net/__attachments/a_061965ebcea9d671e2eb90bd588629ffc82c5b9791e83aa153d24c164ea94177/Bitbucket-source.png?cb=ba2d5b57603c11cdfb29f20a9d204f55)
OpenAPI documentation in Confluence from Bitbucket repository

3. Finally, save the macro and publish the page 🎉

---
language: "en"
---
# Issue Templates Pro - Description Templates for Jira

Streamline issue creation across projects in Jira with predefined issue templates.

Using [**Issue Templates Pro for Jira - Description Templates for Jira \& JSM**](https://marketplace.atlassian.com/apps/1228993/issue-templates-pro-issue-description-templates-for-jira), you can define templates for summary and description fields. The templates will be automatically pre-filled into the fields in the create issue screen.  
If you are using a version from**v3.0.0** to**v5.0.0** , you need to upgrade the app. Otherwise, the app will throw an error, and users will not be able to manage templates. Please contact our 👉 [**support**](https://get.support.narva.net/servicedesk/customer/portals)if you need help.  
<https://www.youtube.com/watch?v=3FBt2chGJlk>

This app works on both company-managed and team-managed projects.  
![Story-template.png](https://help.narva.net/__attachments/a_70b046944b94c06793e918a7c08f97bf36a9d23e6c18031c59c7985fbeb33b37/Story-template.png?cb=143ff0809ac67b734114f40915903ec3)
Story template example

**Issue Templates Pro** is available on the Atlassian Marketplace. You can try the app for 30 days for **FREE**!

1. Go to [**Issue Templates Pro for Jira**](https://marketplace.atlassian.com/apps/1228993/issue-templates-pro-summary-description-templates-for-jira?hosting=cloud&tab=overview)on **Atlassian Marketplace**

2. Click on **Try it free**

3. Choose your instance and click **Install app**

The app will be installed in your Jira instance.  
![issue-templates-pro-marketplace-listing-2.png](https://help.narva.net/__attachments/a_db66c456d800ffb4cb0db0c4b1ff31776efad628c0bee41ac048edc14a240abe/issue-templates-pro-marketplace-listing-2.png?cb=f0ffcaac0aa0a4870cae88c2b4c5f9dd)
Install Issue Templates Pro from Atlassian Marketplace

If **you are not the Jira admin, you can request the app** instead, following the same process above. Your Jira admin will be informed with the request to install this app.

Once the installation is complete, you can start using templates in your Jira projects.  
* [Using Issue Templates in Jira](https://help.narva.net/issue-template-for-jira/create-an-issue-template.md)
* [Known Issues and Limitations](https://help.narva.net/issue-template-for-jira/known-issues-limitations.md)
* [App Updates and Release Notes](https://help.narva.net/issue-template-for-jira/release-notes.md)

---
language: "en"
---
# Access prompt, templates limit and major upgrades

**Date: July 10, 2023**

Marketplace version number: **3.0.0**

We have worked hard to improve [**Issue Templates Pro for Jira**](https://marketplace.atlassian.com/apps/1228993/issue-templates-pro-issue-description-templates-for-jira?hosting=cloud&tab=overview) and as a result this version brings major changes in the way the app works.  
This release is a major version. That means Jira admins must manually update the app from **Top Nav → Apps → Manage your apps**

## 1. Per user access prompt is removed

Until now, all users had to go through the `allow access` process before using templates as documented in [Known Issues and Limitations](https://help.narva.net/issue-template-for-jira/known-issues-limitations.md).

This required access flow is completely removed and users will not see the prompt anymore.

### 2. Not limited to 100 templates anymore

The initial version of the app (V1) had 100 templates assignment limits. Many customers hit this limit, as one template could be assigned to many projects, easily reaching the 100 limit.

We are happy to announce that 100 templates limit is removed.

### 3. Major UX upgrade

Based on user feedbacks, we have made major UX improvements and simplified the overall template management.  
![issue-template-templates-list.png](https://help.narva.net/__attachments/a_d675e383db4cfb12e6b73a7a0a24e76de41c06f0dc80f75708021888bd999afa/issue-template-templates-list.png?cb=3add86d4e3d224a0a1924a4648e31255)
Issue Template for Jira V2 - Templates Overview  
![Issue-template-assignment.png](https://help.narva.net/__attachments/a_eff2213f798c24da650764895ff7b2280c8c72ddce43f8b56ae93e4ab5eefa8a/Issue-template-assignment.png?cb=8851cc2b10555ec04411369b4a03986c)
Issue Template for Jira - Template Assignment

The old V1 page will still be available initially, along with V2. Though, we recommend users to upgrade to V2.

One distinct change apart from UI/UX is that a template is not fixed to Issue Type like in V1. This means users will have more freedom to model templates as they wish. This also creates a pathway for an upcoming feature: multiple templates per issue type.

We also consolidated the template management to make it easier, which means project templates are removed.

### How to upgrade to V2?

This is a major release, which means Jira admins must manually update the version. They can do it from **Top Nav** → **Apps → Manage your apps** . Note that **3.0.0** is the Marketplace version number for this release, so version number should be updated to 3.0.0 or greater.

---
language: "en"
---
# Apply Templates to Existing Work Items

The main feature in [**Issue Templates Pro for Jira**](https://marketplace.atlassian.com/apps/1228993/issue-templates-pro-summary-description-template-for-jira) is to enable templating during issue creation. However, there are some cases where an issue might be created without templates.

We have now made it possible to apply a template even after an issue is created. For example, this feature can cover the following use cases:

* Apply templates to issues (requests) created by JSM customers

* Apply templates to existing issues in backlog

* Apply templates to issues created via API, Automation or other apps

**Open an issue → Click on More action (...) button** → **Apply template**  
![post-create-apply-templates-II.png](https://help.narva.net/__attachments/a_70ba66ff0814eaf156187e6fc7b331dfaba40bf0c12e11682c17494cd41ed487/post-create-apply-templates-II.png?cb=2e5e694ad32491ad5e399e0e21e2d592)
Apply template to existing issues

Proceed to **Select the template** → **Save** → **Proceed.**  
![image-20240717-070540.png](https://help.narva.net/__attachments/a_1cfd5df337b8b1f3e1be6fa06e571f354a5491fa9cfab9da0b4e8af70b5f7f46/image-20240717-070540.png?cb=cc84ba6d7a6ebd3abbbbe475a7e728a1)  
Please note: Issue's summary and description will be replaced.

## There is no template in the dropdown

If the dropdown is empty, it means that there is no template assigned to the project yet.

**Go to Issue Templates Pro app** → **Create Issue** → **Add template**.

Please refer to [Using Issue Templates in Jira](https://help.narva.net/issue-template-for-jira/create-an-issue-template.md) for a complete guide about setting up templates.

---
language: "en"
---
# Apply Templates via Automation or API

When creating issues through Jira Automation or an API, you might need to apply templates. For instance, if tests fail in Xray, an issue can be automatically generated.

Using this feature, templates can be seamlessly applied to the auto-created issues.

## Apply Templates via Automation

With Jira automation, you can apply templates to issues. Below are the steps:

**Generate token**

1. Go to "Apps" on the top navigation bar

2. Go to "Manage Your Apps"

3. Open "Issue Templates Config" from the left bar

4. Go to "API Tokens"

![Issue-templates-api-tokens.png](https://help.narva.net/__attachments/a_666700b06922890f5ba3505ce6873371df0fbb8f9902cfba0073751adb5d6ac1/Issue-templates-api-tokens.png?cb=12e56b733962634758055a89d47a3ece)
API Tokens

5. Click "Generate Token"

6. Fill in the token label and expiration date

7. Copy the token

Note: once the generate token window is closed, token cannot be viewed again.

**Create Automation Rule**

1. Create an automation that adds Web request URL after creating a new issue. Please see <https://www.atlassian.com/software/jira/guides/automation/tutorials#manage-automation-rules> for Jira automation tutorial.

2. Add a "Send web request" component as rule action.

![image-20241111-231618.png](https://help.narva.net/__attachments/a_36506a497820ee3b0675a2bea557b9bb53aabed20615326b143198148cbf32c4/image-20241111-231618.png?cb=be4cfd67e7effe914fc437157e36639a)
Web request component

3. Fill in the Action with the following:

![Screenshot 2024-11-12 at 14.47.46-20241112-065745.png](https://help.narva.net/__attachments/a_c732bdff58743a1979eb20fe9dcdc7a24996b70891eecd6bbf7a07ee1fd058de/Screenshot%202024-11-12%20at%2014.47.46-20241112-065745.png?cb=7e303441ff94d596df935b2176d898e0)
Web Request params

To ensure that **the rule does not overwrite important data**, you can add a condition to check if issue description field emply or has only short value.  
![check-description-length.png](https://help.narva.net/__attachments/a_b823d47a42d58c634b3a1ec1af4a4d2151473920b9b4580ccdbea10a2220efcc/check-description-length.png?cb=9c79affeccdfc4a6466cbb9b850af91b)
Add if condition to check description field

a. **Web request URL** : *\[URL\]*

To get the web request URL, go to back to API Tokens page: Top Nav → Manage Your Apps → Issue Templates Config → API Tokens and copy the Web request URL.  
![image-20241112-041146.png](https://help.narva.net/__attachments/a_4ff45e86e68f61b1d8b5fb1bb6dbca31e87a1f2b1f909b387c0b6a038e696be1/image-20241112-041146.png?cb=514ddf83b55abec92e59fa4045f41098)
Web request URL

b.**HTTP method**: POST

c.**Web request body**: Custom data

d.**Custom data**:

    { 
     "issueKey": "{{issue.key}}",
     "templateId" : "IT-V2-039e00da-3703-4d2f-a7d3-6490ece4880a" 
    }

* **issueKey** is the key of the newly created issue. It is auto-generated by Jira. You can leave this as is.

* **templateId** is the template you would like to apply. To get the templateId, please navigate to the Issue Templates Pro app → Click action (...) → Copy templateId.

![Issue Templates Pro menu](https://help.narva.net/__attachments/a_49ba479e6fd6bafde3d5c3767b97dac948068cc647dec57f0b7a17c5ce26eda1/Screenshot%202024-11-07%20at%2020.28.31-20241107-122900.png?cb=189c724ea0015dbafd54c0520b9d7b55)
Action menu

e.**Headers (optional):**

* Key: Authorization

* Value: Bearer *\[token\]*

Paste the generated token in Value field, after `Bearer`.  
![image-20241112-040433.png](https://help.narva.net/__attachments/a_69539baac8920dfbc3ac6380e0f7d9db67147699ca056430619abf6327f0e7bf/image-20241112-040433.png?cb=e7ede2bfb931effe1b847f90dd89053e)
Web Request authorization header

## Apply Template with API

Following similar approach, you can also apply template with API. In this example, we are using Postman.

**Generate token**

Please see above how to generate token: [https://narva.atlassian.net/wiki/spaces/IT/pages/2748678147/Apply+Templates+via+Jira+Automation+or+API#Generate-token](https://help.narva.net/issue-template-for-jira/apply-templates-via-jira-automation-or-api.md#Generate-token) .

**Configure the API**

1. Use the **POST** URL with the web request URL.

To get the web request URL, go to Apps on the top navigation bar → Manage Your Apps → Issue Templates Config from the left bar → API Tokens → Copy the Web request URL.  
![image-20241112-041146.png](https://help.narva.net/__attachments/a_4ff45e86e68f61b1d8b5fb1bb6dbca31e87a1f2b1f909b387c0b6a038e696be1/image-20241112-041146.png?cb=514ddf83b55abec92e59fa4045f41098)
Web request URL

2. Fill in the generated token.

![Screenshot 2024-11-07 at 20.41.17-20241107-124204.png](https://help.narva.net/__attachments/a_fcebcdcf7afd5c6141f5611c09d52cd080e38f716b2037ea5848ac1b5afff26d/Screenshot%202024-11-07%20at%2020.41.17-20241107-124204.png?cb=06c339727bb1dc3aed0a2201ef783df5)
Postman - Authorization tab

3. Use the following parameters inside Body.

    { 
     "issueKey": "{{issue.key}}",
     "templateId" : "ITT-V2-039e00da-3703-4d2f-a7d3-6490ece4880a" 
    }

**templateId** is the template you would like to apply. To get the templateId, please open the Issue Templates Pro app → Click action (...) → Copy templateId.  
![image-20241107-124753.png](https://help.narva.net/__attachments/a_701af8c79d6b54ec10e9bae661835b044cbeb0d0c8915734374cf2945f4b84c6/image-20241107-124753.png?cb=4c16105b8c6ed8e8bc7c55208589c8de)
Postman - Body tab

## HTTP Response and Error

The summary of the HTTP response codes is given below.  

| **HTTP Response Code** |                  **Remarks**                   |
|------------------------|------------------------------------------------|
| 200                    | Template is successfully applied to the issue. |
| 401                    | Wrong authorization or wrong token.            |
| 404                    | Template is not found.                         |
| 400/424                | Issue is not found.                            |

---
language: "en"
---
# Using Issue Templates in Jira

You can use templates in Jira when creating issues with[**Issue Templates Pro - Description Templates for Jira**](https://marketplace.atlassian.com/apps/1228993/issue-templates-pro-issue-description-templates-for-jira?hosting=cloud&tab=overview)app. Define standard templates with issue summary and description fields, and the templates will be automatically applied when users create new issues.

If you haven't installed the app, refer to [https://narva.atlassian.net/wiki/spaces/IT](https://help.narva.net/issue-template-for-jira.md) the guide for installation help.

Once the app is installed, setting up templates is easy.

1. Go to**Sidebar → Apps → Issue Templates**

2. Click on **Create Template**and an add template window will open.

![issue-templates-pro-dashboard.png](https://help.narva.net/__attachments/a_69a6ef0507833b3d7f93b40d126b4157538140a56563a67c05f5a358c31728ad/issue-templates-pro-dashboard.png?cb=335ae9ce359091e6ddb2ee86abbde10d)
Issue Templates Pro app dashboard

Enter template details in the form. The **template** **name** and **issue** **description** fields are required, whereas the summary field is optional.  
![issue-template-create-template.png](https://help.narva.net/__attachments/a_3130e6d5478767c51bf5fc33490d25e720a059bf22371caba5ee3d257e76d3aa/issue-template-create-template.png?cb=98e77c20d9c76aa913f7974470e96351)
Templates create form

## Using Issue Templates

Once a template is created, you can now assign it to project and issue type pairs. In order to activate the template, click on **Assign to project**.

### Assign Template to Issue Type

In the next window, you can select project and issue type (e.g Story, Task, Sub-task) or select project and component. Stay on 'Issue Type' tab . In order to assign a template to multiple projects and multiple issue types at once, click on + (add) button and click on **Save settings**.  
![image-20240710-052030.png](https://help.narva.net/__attachments/a_b3111d5f3106648a0236848def6b20bcc4a73e144bfc1db6fd928708f561900f/image-20240710-052030.png?cb=e92c86da22594d07ff3ce6f1862d9c77)

Once this step is complete, templates will be activated, which means template fields will be automatically pre-filled when users try to create new issues.

To test it out, try to create an issue:  
![Issue Template for Jira - Bug template example](https://help.narva.net/__attachments/a_06a21865a076bb13e7b11f54824540c526c940b94c55a24e3b6b713fed60fb07/Bug-template-issue-create.png?cb=372de9f3d8afa047d1b97b2e1939ce89)

If you want to deactivate a template, simply go back to project settings and remove the assignment setting.

### Manage Templates

Use the action button (**...**) to edit the existing templates or delete them entirely if a template is no longer needed.  
![image-20240710-053859.png](https://help.narva.net/__attachments/a_88127aa294172ed02e3051c4e57a943e5fe6fba7789a53b69e925d51e7c9f144/image-20240710-053859.png?cb=fa5da5a56ee051fc3dacc25530ed97e7)

### Templates Permissions

You can now restrict template management to only admins. This will make main templates app still visible to users in read-only mode, but they will not be able to edit and assign templates.

Admins include Jira administrator, site/organization admins and trusted users. You can check who is admin in Jira configuration from **Settings → System → Global Permissions** . Users that are in any groups under the Administer**Jira** section are considered administrators.

In order to enable this feature:

1. Go to **Settings → Marketplace Apps → Manage apps**

2. Click on **Issue Templates Pro Configuration** from the left sidebar

![issue-template-configuration.png](https://help.narva.net/__attachments/a_b65aa87c495fa574a228d49323206770bfe3d4dd2930df0142f2cd16b6739de6/issue-template-configuration.png?cb=230f0ab2880c5739b1e439def1c9867f)

### Further Guides

* [Using Templates for JSM Portal Requests](https://help.narva.net/issue-template-for-jira/using-templates-for-jsm-portal-requests.md)
* [Template Overwrite Rules](https://help.narva.net/issue-template-for-jira/template-overwrite-rules.md)
* [Apply Templates via Automation or API](https://help.narva.net/issue-template-for-jira/apply-templates-via-jira-automation-or-api.md)
* [Apply Templates to Existing Work Items](https://help.narva.net/issue-template-for-jira/apply-template-to-existing-issues.md)

### Known Issues and Limitations

This app has some limitations and possible workarounds. We have documented them in a dedicated page here: [Known Issues and Limitations](https://help.narva.net/issue-template-for-jira/known-issues-limitations.md)

---
language: "en"
---
# Issue Template for Jira is now paid app (free up to 10 users)

**Date: August 24, 2023**

Marketplace version number: **5.1.0**

[Issue Template for Jira - Summary \& Description Templates](https://marketplace.atlassian.com/apps/1228993/issue-templates-pro-issue-description-templates-for-jira?hosting=cloud&tab=overview) was first released on 1st September 2022. Initially, we released the app as free because it was a fun project for our small team to try out [Forge](https://developer.atlassian.com/platform/forge/), Atlassian's new managed platform for building apps. After the initial public release, the app received very positive feedback and now has thousands of customers.

As the app got popular, our support channel constantly got overwhelmed. Our aim is to not only release an app, but also support our customers and solve the day-to-day challenges faced by them. Therefore, by changing the app from free to paid, we want to invest in further development as well as on support resources.

Paid customers will get following benefits:

* Ongoing bug fixes and upcoming features

* Priority support with SLA

* Stay up to date with new releases including security patches

If you are an existing user, you can continue to use the old version for free. Though, we highly recommend you to upgrade (see above). If you are an early user and especially helped us by giving feedback, we are more than happy to upgrade for free. [Let us know](https://bitwelt.atlassian.net/servicedesk/customer/portals) 🙂

Pricing change is covered in our license agreement [here](https://help.narvaapps.com/support-licensing-data-security/end-user-license-agreement-eula). If you have any feedback about licensing, please let us know. You can contact us via email: [support@narva.net](mailto:support@narva.net) or directly via our [JSM support channel](https://bitwelt.atlassian.net/servicedesk/customer/portals).

---
language: "en"
---
# Known Issues and Limitations

Currently, [Issue Templates Pro - Description Templates for Jira](https://marketplace.atlassian.com/apps/1228993/issue-templates-pro-issue-description-templates-for-jira?hosting=cloud&tab=overview) has some known limitations. We are constantly working on to improve this app and these issues and limitations will be fixed whenever possible.

## 1. Conflict with ScriptRunner Behaviours and other apps

**Issue Templates Pro** can conflict with few other apps from the marketplace. As a result, it might not apply templates as expected.

The main conflicting apps are:

* **ScriptRunner Behaviours** from Adaptavist (only the **Behaviours** extension, not the main ScriptRunner app)

* Issue Templates Agent from appsvio

The conflict happens because all these apps utilize the same Jira module ([Atlassian docs](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-ui-modifications/#multiple-uim-apps)) and have similar features. If you are trying them out, **please do not use them all together** at the same time. **You also need to uninstall the other apps,** only disabling will not avoid the conflict.

### 2. App clears the user-entered data when changing issue type

This issue is now fixed in newer versions. However, there are few things to note:

* If you have typed or entered a long text, it will not apply template when you change issue type to prevent the user entered data loss. However, it will apply template when it is just a short text.

### It applies the same template to all Issue Types

This issue is now fixed in newer **versions** \> **5.26.0** . You can check the app version from Apps → Manage apps

### 3. Template is not applied when creating issue from Epic, Backlog etc.

Creating issue from places other than the main create button in the navigation bar is partially supported.

* **Creating from Epic**

In order to apply templates when creating issues from epic, at least one field needs to be set as required. You can, for example, set the description field to be required (by default, this field is optional).

You can do that with following steps (company managed projects):

* Go to **Project Settings → Fields → Actions (top right) → Edit Fields**

* Change the **Description** field to required

![IT-Description-Field.png](https://help.narva.net/__attachments/a_91f695e7337e35d486716d611433feea2d1b405f082bcb41492cf9c2f8af0892/IT-Description-Field.png?cb=a48353ae0e97a300c99bbe703418d43c)
Set the Description field to be required

Team managed projects currently do not allow description field to be set as required. However, this workaround works if you change any other field to be required.

If you want to use **Subtask** templates, the same workaround will also work for that use case.

* **Creating from Backlog**

Creating from backlog is currently not supported because of technical limitation. Therefore, we suggest using the main create button.

### 4. Error when creating issue after a template is assigned

Some users have encountered the following error when creating an issue after a template is assigned:  
We encountered an error while applying UI modifications to this form.  
![Jira-UI-Modifications-error.png](https://help.narva.net/__attachments/a_709f1a1cefd47a0eb8cf2f8dfc028406a509a1fb1ad54685863a97a1dfa6a85a/Jira-UI-Modifications-error.png?cb=2b1aa3739ae612b6ca0b7fcac2dd8808)
Error when creating an issue

This happens when the description field has a different renderer. The field renderer has to be **Wiki Style Renderer**.

If you see this error, you can go to Project Settings → Issues → Fields and change the renderer to Wiki Style Renderer for description field.

---
language: "en"
---
# App Updates and Release Notes

After the initial public release, the app is very well received. Thanks to our users for very positive feedback and suggestions for improvements. We are continuously working hard to improve it further and as a result, make frequent releases.

Major app updates are documented below:  
Please note, admins have to manually update major versions from **Apps → Manage your apps** in Jira setting. Minor versions are automatically applied.

## v8.0.0 Support for templates in JSM Portal

Release date: July 15, 2026

You can now use this app to create templates in JSM Portal which will be automatically pre-filled when portal customers create new requests.

### v7.10.0 Apply templates via Jira Automation or Webhook

Release date: November 18, 2024

You can now apply templates using Jira Automation or using Webhook / API. Check out to detailed documentation: [Apply Templates via Automation or API](https://help.narva.net/issue-template-for-jira/apply-templates-via-jira-automation-or-api.md)

### v7.0.0 Apply templates after issue is created

Release date: July 17, 2024

You can now apply templates even after an issue is created from issue action (...) → Apply template.

### v6.0.0 Components based templates

Release date: July 16, 2024

You can now assign templates to a Jira component along with existing issue type in company managed projects. This feature makes the app very flexible and cover a wide range of use-cases.

### v5.39.0 Data Residency

Release date: May 30, 2024

Issue Templates Pro now supports [Data Residency](https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/). For customers who have enabled data residency in Jira Premium, the app will store data in the same location/region as Jira.

### v5.27.0 Name changed to ++Issue Templates Pro++

Release date: January 31, 2024

We have slightly updated the app name to avoid the confusion with other similarly named apps.

Check out our updated Marketplace listing 👉 [Issue Templates Pro - Summary \& Description Templates](https://marketplace.atlassian.com/apps/1228993/issue-templates-pro-summary-description-templates-for-jira?tab=overview&hosting=cloud)

### v5.26.0 Prevent data loss when applying template

Release date: January 26, 2024

Until now, if you wrote a long text into an issue description but switched the issue type, it overwrote the description field with the assigned template, resulting in loss of manually entered text.

We have fixed this issue. The app will not apply templates if you have entered a long text into the description field.

### v5.18.0 Pagination (upgrade required for older versions)

Release date: December 11, 2023

We have added 20 templates per page pagination when there are more than 20 templates. This limit is enforced by Atlassian hosted Forge Storage used by the app.  
If you are using a version from**v3.0.0** to**v5.0.0** , you need to upgrade the app. Otherwise, the app will throw error and users will not be able to manage templates. This was not planned, therefore we will provide free upgrade to paid version. Please contact our 👉 [**support**](https://bitwelt.atlassian.net/servicedesk/customer/portals).

You can view versions and upgrade the app from **Top Nav → Apps → Manage apps**.

### v5.6.0 Templates search and filter by project

Release date: October 11, 2023

We have listened to feedback from Jira admins who have large instance and many templates. This version adds:

* Templates search bar and filter by project

### v5.4.0 Admin only templates management

Release date: September 18, 2023

We have now added permission which allows you to limit templates management to only Jira admins. Read more about this feature here: [Using Issue Templates in Jira](https://help.narva.net/issue-template-for-jira/create-an-issue-template.md)

### v5.3.0 Support for Jira Work Management

Release date: September 13, 2023

This version adds support for **business** (work management) projects.

### v5.1.0 Update the licensing model

Release date: August 24, 2023

[Issue Template for Jira is now paid app (free up to 10 users)](https://help.narva.net/issue-template-for-jira/issue-template-for-jira-is-now-paid-app-free-up-to.md)

### v4.0.0 Bug Fixes

Release date: July 12, 2023

This should have been a minor release, but we had to release it as a major version. We have fixed numerous bugs that were introduced in the initial release of V2:

* Display issue when a template was assigned to new project

* Show project icons and other minor bugs

### v3.0.0 Access prompt and other major upgrades

Release date: July 10, 2023

[Access prompt, templates limit and major upgrades](https://help.narva.net/issue-template-for-jira/access-prompt-templates-limit-and-major-upgrades.md)

Marketplace version number: 3.0.0

---
language: "en"
---
# Template Overwrite Rules

When switching issue types, it will replace text you have already typed --- but only up to a point. This page explains exactly where that point is.  
The app tries to not interfere once you have clearly started writing. Therefore, templates might not be applied when changing issue type after this point.

## Overwrite Rules

There are two checks that decide whether to replace user text or not:

### 1. The description check --- 200 characters

When you change an issue type (work item type), if you have added **more than 200 characters** of your own, the template is skipped entirely.

At 200 characters or fewer, it continues to the second check.

### 2. The summary check --- 5 characters

If you have changed **5 or more characters** in it, your summary is kept and the template's summary is ignored --- but every other field is still filled in.

Under 5 characters, the template's summary replaces what is there.

[Next Page](https://help.narva.net/llms-full.txt/1)
