How to make custom field labels bold/larger in Issue View?

[Chen Shasho]

We use several custom fields in addition to the Description field, to structure our Bug template.

Problem: all field labels use the same small, uniform font. When the issue is opened, everything blends into one continuous block with no visual separation between sections.

Is there a supported way (Field Configuration / Issue Layout) to make field labels bold/larger, or add a divider between fields — without a marketplace app?

[Cristian Quiroz Garcia]

Hello @Chen Shasho ,

You can use the "Message" Custom Field (also known as "Message Custom Field for view") to achieve this effect natively in Jira — no marketplace app needed.

This field type accepts wiki markup, which gives you a couple of useful tricks:

Simulating a visual divider:
Place four dashes (----) in the field's default value — Jira renders them as a horizontal line, creating a clear visual separation between sections.

Making the label stand out:
Since you control the field's name, you can write it in ALL CAPS (e.g., STEPS TO REPRODUCE) so it naturally draws the eye without needing any formatting.

How it looks in practice:
The field name acts as the section header, and the rendered horizontal line (from ---- in the default value) acts as the divider — giving the issue form a structured, sectioned appearance without any styling plugins.

Steps to set it up:

1. Create a new custom field of type "Message"
2. Set the field name to your desired section label in ALL CAPS (e.g., STEPS TO REPRODUCE)
3. In the field's default value, add ---- so it always renders the divider line
4. Add it to your Bug Issue Layout in the desired position between other fields

⚠️ This field is display-only — it won't accept user input. That's ideal here since its only purpose is visual structure.

[Thanasis Nikolaou]

Hey @Chen Shasho 

Short answer: no, there's no supported way to change label font size/weight or insert dividers in the issue view — no Field Configuration or Issue Layout option touches typography, and Cloud gives you no CSS hook at all.

What I'd actually do instead:

• Put the bug fields on a second screen tab. Field tabs do render in the issue view and they're the only native "section divider" you get — a tab named "Bug details" holding Steps / Current / Expected separates cleanly from everything else.
• In the issue layout, group the three fields together and away from the noise — order is the one lever you fully control.
• Honestly consider collapsing them into headings inside Description, prefilled by an automation rule on create. Headings are bold and large; three separate paragraph fields never will be.

I hope this helps!

Kind regards,

Thanos