Files

T

ankn a5f8fb49ab Migrate all repos into monorepo context folders

Bahn: aisupport, Analyse-O2C-C2S, awesome-bahn-mcp-servers, beam-mcp,
      Confluence_Bot, db-planet-mcp-server, O2C-Harness, project-audit,
      Projekt-KIQ-HP, teamlandkarte-mcp
Dhive: Jury-Voting
Privat: CV, NoteGraph (NOTE: NoteGraph needs complete redo after consolidation)
Shared: AI-Orchestrator, OrgMyLife, power_skills_and_more
Shared/references: symphony (read-only)

Bahn repos remain available as independent remotes - this monorepo
pulls them in via subtree, the originals are untouched.

2026-06-30 20:39:52 +02:00

2.7 KiB

Raw Blame History

Wissensfragment: BSSUPPORT Jira Dashboard

Erstellt: 2026-04-30 | Kontext: Andre moechte ein Dashboard fuer gefixt Bugs aus Releases

Zweck

Dashboard das zeigt welche Kunden-Bugs (BSSUPPORT) in den letzten 2 Kalenderwochen durch Releases auf KTU/Prod gefixt wurden.

JQL-Abfragen

Im ReTest (aktuelles Release)

project = BSSUPPORT AND issuetype = Bug AND status = ReTest ORDER BY fixVersions DESC, updated DESC

Gefixt in letzten 2 Kalenderwochen

project = BSSUPPORT AND issuetype = Bug AND statusCategory = Done AND updated >= startOfWeek(-1w) ORDER BY updated DESC

Bugs mit FixVersion (alle Status)

project = BSSUPPORT AND issuetype = Bug AND fixVersions is not EMPTY AND updated >= startOfWeek(-1w) ORDER BY fixVersions DESC, status ASC

Kombiniert (Fertig + ReTest)

project = BSSUPPORT AND issuetype = Bug AND (status = ReTest OR (statusCategory = Done AND updated >= startOfWeek(-1w))) ORDER BY status ASC, fixVersions DESC

Spalten-Konfiguration

Spalte	Jira-Feld	Zweck
Key	key	Ticketnummer mit Link
Summary	summary	Titel
Created	created	Geoeffnet am
Resolved	resolved	Geschlossen am
Fix Version/s	fixVersions	Release (z.B. R37 04.05 KTU)
Status	status	Fertig / ReTest
Labels	labels	Team-Zuordnung
Assignee	assignee	Bearbeiter

Team-Erkennung ueber Labels

Label	Team
o2c, portal, Portal-UI	Team 404
c2s, ifp	Team CIB
ci, CI, Stammdaten	Team Zero
ujBau	Uebergreifend (CIB + Zero)
Support_Kunde_DBCargo	Cargo-relevant
Support_Kunde_DBFernverkehr	FV-relevant
Support_Kunde_DBRegio	Regio-relevant

Dashboard-Gadgets

Gadget	Typ	JQL
Im ReTest	Filter Results	`status = ReTest`
Gefixt (2W)	Filter Results	`statusCategory = Done AND updated >= startOfWeek(-1w)`
Trend (4W)	Created vs Resolved	`resolved >= startOfWeek(-4w)`

Release-Namenskonvention

Format: R{nr} {dd}.{mm} {Umgebung}

Beispiel: R37 04.05 KTU = Release 37, deployed am 04.05 auf KTU
Umgebungen: KTU (Kundentestumgebung), Prod

Verlinkung zu Umsetzungstickets

BSSUPPORT-Tickets sind oft verlinkt mit:

O2CCIB-xxx (CIB Umsetzung)
O2C404-xxx (404 Umsetzung)
O2CZERO-xxx (Zero Umsetzung)
TTTI-xxx (Integrationstest)

Falls ScriptRunner verfuegbar:

issueFunction in linkedIssuesOf("project = BSSUPPORT AND issuetype = Bug AND updated >= startOfWeek(-1w)", "is caused by")

Issue-Typen im Projekt BSSUPPORT

Bug (Fehler im System)
Serviceanfrage (Kundenfrage/Konfiguration)
Support (Allgemeine Unterstuetzung)

Nur Bug ist relevant fuer das Release-Dashboard.

2.7 KiB Raw Blame History