df667e0db8
- web/: Local chat UI (Express + WS → Codex bridge) - openwebui/: Preset, pipelines, knowledge manifest - Dockerfile + docker-compose.yml - Updated README with 3 frontend options - CLI-agnostic: works with Codex, Claude Code, Kiro, Gemini
39 lines
1.3 KiB
Markdown
39 lines
1.3 KiB
Markdown
---
|
|
name: rp-ticket-ops
|
|
description: Create and update RP Jira tickets in reltio.jira.com with the standard IaC setup. Use when you need to batch-create or normalize RP tasks to match the reference ticket (labels, sprint, status, assignee, and verification).
|
|
---
|
|
|
|
# RP Ticket Ops
|
|
|
|
## Jira Context
|
|
- Domain: `https://reltio.jira.com`
|
|
- Cloud ID: `444c13e0-0faa-4055-b053-501700bae7b0`
|
|
- Project: `RP`
|
|
- Reference ticket: `RP-175518`
|
|
|
|
## Standard RP IaC Values
|
|
- Sprint field key: `customfield_10320`
|
|
- Sprint value shape: numeric sprint id in `fields` (example: `4936`)
|
|
- Sprint in this workflow: `4936` (`IAC Sprint 8`)
|
|
- Labels:
|
|
- `Project_Cloud_Platform_IaC`
|
|
|
|
## Update Pattern
|
|
1. Find all target issues by key or summary.
|
|
2. Ensure labels are set exactly to the 3 standard labels.
|
|
3. Set sprint with:
|
|
- `fields: { "customfield_10320": 4936 }`
|
|
4. Verify with JQL.
|
|
|
|
## Verification JQL
|
|
- Sprint check:
|
|
- `key in (...) AND sprint = 4936`
|
|
- Assignee check:
|
|
- `key in (...) AND assignee = "Yevhen Fesyk"`
|
|
- Status + labels check:
|
|
- `key in (...) AND status = "Prioritized" AND labels in ("Project_Cloud_Platform_IaC","Project_Cloud_Platform_IaC_v0.4","qa-foxtrot")`
|
|
|
|
## Notes
|
|
- For sprint assignment, prefer the numeric `fields.customfield_10320` payload.
|
|
- If sprint is not visible on board after update, re-check via JQL first; board views can lag.
|