# Feature OP-20005 - Render code identifiers with backticks in Work Package subjects

Project: OpenProject
Status: in specification
URL: https://community.openproject.org/work_packages/OP-20005

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Work packages, Frontend components and Primer design system |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a developer
**I want to** put code identifiers in Work Package subjects, e.g. `ProjectIdentifierCache`
**so that** bug, feature and maintenance tickets read the way the code does.

**Acceptance criteria**

*   A subject typed as ``Fix `ProjectIdentifierCache` in main module`` displays `ProjectIdentifierCache` in monospace everywhere the subject is shown — WP table, full view, cards, breadcrumb, notification centre — the same way GitHub renders an issue or PR title.
*   Only inline code spans (single backticks) are interpreted. No other Markdown — bold, italics, links, images, headings — renders in a subject.
*   The raw text including the backticks stays on the record: editing shows the backticks again, and search, filters and sorting keep matching the raw string.
*   Contexts that demand plain text keep the raw string: page `<title>`, email subject lines, CSV/XLS export, API `subject` value.

**Technical notes**

*   Rendering is display-time only; nothing is stored pre-rendered. Escape the subject before injecting the `<code>` element.
*   GitHub's scope is the reference: code spans in titles, nothing else.

**Permissions and visibility considerations**

*   Visible to anyone who can already see the subject. No new permission.
*   Not applied in the plain-text contexts listed above.

**Translation considerations**

*   No new user-facing strings.

**Out of scope**

*   Any Markdown beyond inline code spans.
*   Markup in other short-text fields (project names, version names, custom-field values).

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
