J01-116: Make public Jira issue pages consistent

Stand: 2026-03-24

J01-116 Öffentliche Jira-Issue-Seiten: Metadaten und Unteraufgaben konsistent spiegeln

Type

Task

Status

Zu erledigen

Priority

Medium

Assignee

Dani Y.

Sprint

-

Sprint role

Sprint-Admin

Resolution

-

Updated

2026-03-24T11:56:48.308+0100

Parent

J01-84

Related issues

Relates to: J01-107 — Jira-Metadaten: Migrationsvorgänge aus J01-91 präzise verlinken — Erledigt

Relates to: J01-31 — Preview Readiness: System-Source-Verarbeitung — Zu erledigen

Relates to: J01-104 — GitHub Pages: Link-Regel für öffentliche Schrittseiten — Zu erledigen

Contents key

This page

• Source basis
• Goal
• Current status
• Verification plan
• Links

Canonical public work status for J01-116. This issue sharpens the public Jira area so an issue page reflects Jira state clearly again without blurring the split between Jira and GitHub Pages.

Source basis

• Area: Jira and docs tooling and Jira overview: GitHub Pages remains the public documentation place, Jira remains SSOT for issues and status.
• J01-91: status/plan (snapshot): the same SSOT split is stated there as a public work rule.
• J01-107: refine Jira metadata for migration issues from J01-91: relations should be visible in Jira metadata, not only in prose docs.
• J01-108: public Jira issue pages without overview box: issue pages should show real context, not a second navigation box.
• Runbook: update public Jira area: subtasks without additional details remain visible on the parent and do not get a detail page.

Goal

• Parent pages like J01-31, J01-9 and J01-13 no longer show dead subtask links.
• Public issue pages show the needed Jira metadata: assignee, priority, active sprint, sprint role and linked issues.
• The Jira description becomes visible on generated parent pages instead of the placeholder -.
• The context bar stays compact and only shows real issue context.

Current status

• A new issue J01-116 was created, added to the active sprint and linked with J01-31, J01-104 and J01-107.
• The public generator now pulls description and issuelinks from Jira into the cache and public projection.
• Parent pages only link subtasks when a real public step page exists.
• The public projection now also contains active sprint, sprint role, labels and normalized Jira links.
• Issue pages now bundle Jira metadata and Jira relations in a single top state and relations block.
• The separate context block below that is now reserved for real page navigation such as public steps.

Verification plan

Check	Expectation	Proof / place	Status
Dead subtask links removed	J01-31, J01-9 and J01-13 show unlinked subtasks without a detail page	public Jira issue pages	open
Metadata visible	Assignee, priority, active sprint and sprint role are visible	_includes/jira-state-head.html and generated issue pages	open
Relations visible	Issue pages show Jira issue links in the top state and relations block	_data/jira_pages/issues.json, _includes/jira-state-head.html, issue pages	open
Description mirrored	Jira description appears on generated parent pages	public Jira issue pages	open
DE/EN consistent	EN derivation keeps the same structure and terms	/en/jira/issues/...	open

Links

• J01-31
• J01-107
• J01-108
• Jira work docs