> For the complete documentation index, see [llms.txt](https://fulstech.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fulstech.gitbook.io/docs/markdown/markin-markdown-editor-for-jira/jira-cloud/create-a-markdown-enabled-custom-field.md).

# Create a Markdown-enabled Custom Field

Since it is impossible for a Jira Cloud's app to create its own custom field type, Markin provides Markdown Editor for fields of Jira Cloud’s built-in types. This gives you important benefits:

* All Markdown data is stored securely in your Jira Cloud the same way other Jira data is stored. **Your data will never be stored on our site.**
* Search, JQL, export, API, email notifications, and other field-related utilities will work the same way other fields work.

Please follow the instructions below to create a Markdown-enabled custom field.

## Create a new custom field

### Company-managed projects (classic projects)

#### New Jira Cloud UI

Create a new custom field of type **Paragraph (supports rich text)**. Configure the custom field (name, description, screens) normally. The renderer must be **Default Text Renderer.**

![Markdown for Jira](/files/XJMxe0UAuvHafZMzMGIK)

![Markdown for Jira](/files/rRhX1iclBIxrIPaSEviI)

#### Old Jira Cloud UI

Create a new custom field of type **Text Field (multi-line)**. Configure the custom field (name, description, screens) normally**.**

![Markdown for Jira](/files/-Ma8B0yx6P3rvej6oQOL)

### Team-managed projects (nextgen projects)

Create a custom field of type **Paragraph**.

![Markdown for Jira](/files/C8Re0exX6rWs7NwVMikK)

## Configure the newly created custom field as a Markdown field

Go to the **Project Settings** page of the corresponding project. Select **Markdown Fields** under the **Apps** menu. In the configuration page, select the field created in Step 1 along with all issue types in which you want it to appear as Markdown content.

Optionally you can turn on/off highlighting Gherkin keywords.

<figure><img src="/files/h9nJTl8ruOUQD5at7jWE" alt=""><figcaption><p>Markdown for Jira</p></figcaption></figure>

## Create an issue for testing

Create an issue for testing. Click on the **More Options (three-dots)** button. You should see the **Markdown Fields** section. The fields configured in the above steps should be displayed in the section.

![Markdown for Jira](/files/-Ma8B0z-ShZ3a7DY9jGW)

Click on the fields inside the **Markdown Fields** panel to edit the content.

{% hint style="warning" %}
DO NOT edit the fields using Jira's built-in editors outside the **Markdown FIelds** panel.
{% endhint %}

<figure><img src="/files/MryPn1c55c6ZqgXqs0Tw" alt=""><figcaption><p>Markdown for Jira</p></figcaption></figure>

<figure><img src="/files/nz75C8PVw9rCswnPtAyD" alt=""><figcaption><p>Markdown for Jira</p></figcaption></figure>

## Hide the original field editor

**If your project is company-managed (formerly classic),** you can also hide the original field editor. Please see the instructions here <https://support.atlassian.com/jira-software-cloud/docs/configure-field-layout-in-the-issue-view/#Configurefieldlayoutintheissueview-Hiddenfields>.

![Markdown for Jira](/files/-Ma8B0z4-W1q9tNPNHCy)

## Fulstech AI Copilot for Writing (Preview)

AI Copilot leverages OpenAI's ChatGPT to help you revise the content effectively.

{% hint style="info" %}
This feature is powered by OpenAI's ChatGPT. The data you submit and the responses you receive are not used to fine-tune or improve OpenAI’s models or services. Each data request is sent to OpenAI individually, over an SSL-encrypted service, to process and send back to your Jira. OpenAI does not store the data you submit or the responses you receive.
{% endhint %}

<figure><img src="/files/WAh4q9UPpokoIsQSc0BD" alt=""><figcaption><p>Markdown for Jira</p></figcaption></figure>

To disable the feature, please click on the **Configure** button on the Jira Plugin Manager page.

<figure><img src="/files/maiVTeuCRYJMg2JDd96I" alt=""><figcaption><p>Markdown for Jira</p></figcaption></figure>