Custom field similar to Description field (Rich Text + Large Content)

[Kranthi kumar Girri]

Hi Team,

I have a requirement to create two custom fields in Jira:

• Acceptance Criteria
• Knowledge Transfer

I would like these fields to have the same capabilities as the standard Description field, such as:

• Rich text formatting
• Images/screenshots
• URLs/hyperlinks
• Multiple paragraphs
• Large content support (around 20,000+ characters)

I couldn't find a custom field type that provides the same functionality as the Description field. I tried the Paragraph/Text Area custom field, but it appears to support only around 4,000 characters and does not provide the same rich text experience.

Has anyone implemented a similar requirement?

Looking for guidance on:

1. Is there a custom field type that supports the same rich text functionality as the Description field?
2. Can Jira's rich text editor be enabled for custom fields?
3. Are there any Marketplace apps or recommended approaches to achieve this?
4. What would be the best practice for maintaining large Acceptance Criteria and Knowledge Transfer content within Jira issues?

Any suggestions would be appreciated.

Thanks!

[Lalithesh]

Hi @Kranthi kumar Girri 

Welcome to the Atlassian Community!

Yes, you can change your multi line text field from Default Text Renderer to Wiki Renderer

To configure this, navigate to Project Settings → Fields → search for the field → click the Edit icon → enable the 'Use wiki renderer' option

Cheers!

P.S. If it's a JSM project, you'll find the Fields setting under 'Request management' tab OR it's available under "Work items' tab on Jira software projects

[Kranthi kumar Girri]

Hi , I haven't see those options 

[Lalithesh]

@Kranthi kumar Girri It looks like you're on the Admin Settings page rather than the Project Settings page

Please open the Jira Space (Formerly known as Projects) where you're using these fields, then navigate to Project Settings → Fields → search for the field → click the Edit icon → enable the 'Use wiki renderer' option

Hope this helps!

[Mike C]

Wiki renderer is a Server and Data Center setting. Jira Cloud doesn't have it — there's an open feature request for exactly this (JRACLOUD-42832), so that menu will never show up no matter which settings page you're on. Paragraph (supports rich text) is the right field type on Cloud, and your screenshot shows you already have it. Jean's point about ADF storage covers the length worry.

For the 20,000 character requirement I'd push back on the design. Acceptance Criteria is fine in a Paragraph field because it stays short. Knowledge Transfer at that length belongs on a Confluence page linked from the issue. You get version history and comments there, and the issue stays readable.

[Jean Horn]

Hi there! Welcome to the Atlassian Community! 👋

You are spot on! The field type that closest matches the formatting capabilities of the Description field is indeed Paragraph (supports rich text).

Here is a quick breakdown of how this field works along with its storage limits:

1. Which Field to Use

To get a rich text editing experience for your custom field:

1. Go to Jira Settings (gear icon in the top right corner) > Issues.
2. Select Custom fields from the left menu.
3. Click Create custom field and choose Paragraph (supports rich text).
4. Associate the new field with the appropriate Screens for your project.

2. Character vs. Storage Limits

Unlike simple text fields, rich text fields in Jira do not enforce a standard character limit. Instead, they operate under a data storage limit:

• No explicit character limit: There isn't a hard limit on the number of individual letters or words you can type.
• Storage cap: The absolute limit per field is 1 MB of data.
• Behind the scenes: Jira stores this data in ADF (Atlassian Document Format)—a JSON format used internally by Jira to store rich text, embedded links, and formatting specs.

Pro Tip: In practical terms, 1 MB of ADF payload is massive for a single field. It holds a substantial amount of formatted content, so users rarely hit this ceiling during day-to-day documentation!

Hope this helps clear things up! If you run into any questions about field permissions, screen schemes, or automation rules related to custom fields, feel free to reach out.

If this response solved your question, please consider marking it as Accepted Answer so other community members facing the same question can find the solution easily! 🚀

Cheers and happy configuring!

[Jean Horn]

This way, you can create something similar to this visualization.