**As** a developer Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion **I want to** Begin of the insertionput code identifiers in Work Package subjects, e.g. `ProjectIdentifierCache`
End of the insertion Begin of the deletion use OpenProject for tracking bugs and code-related tickets
End of the deletion **so that** Begin of the insertionbug, featureEnd of the insertion Begin of the deletion manage regressions, featuresEnd of the deletion and maintenance Begin of the insertiontickets read the way the code does.End of the insertion Begin of the deletion with ease.End of the deletion

**Acceptance criteria**

* Begin of the insertionA subject typed as ``FixEnd of the insertion Begin of the deletion Typing "FixEnd of the deletion `ProjectIdentifierCache` in main Begin of the insertionmodule`` displays `ProjectIdentifierCache` in monospace everywhere theEnd of the insertion Begin of the deletion module" for a Work PackageEnd of the deletion subject Begin of the insertionis shown — WP table, full view, cards, breadcrumb, notification centre —End of the insertion Begin of the deletion should then displayEnd of the deletion the Begin of the insertionsame way GitHub renders an issue or PR title.
* Only inlineEnd of the insertion code Begin of the insertionspans (single backticks) are interpreted. No other Markdown — bold, italics, links, images, headings — rendersEnd of the insertion Begin of the deletion identifierEnd of the deletion in Begin of the insertiona 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.

End of the insertion Begin of the deletion monospace - as GitHub does


End of the deletion **Technical notes**

* Begin of the insertionRendering 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.

End of the insertion Begin of the deletion <br>


End of the deletion **Permissions and visibility considerations**

* Begin of the insertionVisible to anyone who can already see the subject. No new permission.
End of the insertion Begin of the deletion _To whom is this feature visible?_

End of the deletion * Begin of the insertionNot applied in the plain-text contexts listed above.

End of the insertion Begin of the deletion _When is it not visible?_


End of the deletion **Translation considerations**

* Begin of the insertionNo new user-facing strings.

End of the insertion Begin of the deletion _Key terms and phrases in the key languages_&nbsp;


End of the deletion **Out of scope**

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

End of the insertion Begin of the deletion <br>


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