JIRA Workflows for Red Hat AI
This skill provides comprehensive knowledge about Red Hat AI story type workflows, including STRAT feature refinement and RFE processes.
Story Types
Red Hat AI uses different story types, each with specific workflows:
- STRAT (Strategic Features) - RHAISTRAT, RHOAISTRAT
- RFE (Request for Enhancement) - RHAIRFE, RHELAIRFE, RHOAIRFE
- RHAIENG - Engineering stories
- Standard Stories - Regular development work
STRAT Feature Refinement Workflow
Overview
Timeline: 1 week from initial doc creation to completion
Dashboard: https://issues.redhat.com/secure/Dashboard.jspa?selectPageId=12386400
Projects:
- RHAISTRAT - Red Hat AI Strategic Features
- RHOAISTRAT - Red Hat OpenShift AI Strategic Features
Process Steps
1. Initial Setup
Ensure the RFE has been approved and properly cloned:
- Clone to relevant STRAT projects as a 'Feature':
- Ensure Feature is properly linked to the associated RFE:
- RHAIRFE-xxx
- RHELAIRFE-xxx
- RHOAIRFE-xxx
2. Feature Refinement Document Creation
Create the document:
- Create a copy of the feature refinement template
- Name format:
FeatureRefinement - RHAISTRAT-# - TITLE OF FEATURE
- Store in feature refinement documents folder (location configurable)
Document Workflow:
- PM and PO/Staff Eng fill in their sections first
- Rest of team and stakeholders provide answers in their sections:
- Scrum Team Engineers
- UX
- Docs
- QE
- Other pillar stakeholders:
- AIPCC (AI Platform Components & Capabilities)
- RHAIIS (Red Hat AI Inference Service)
- AI Platforms (RHOAI)
- Perf / Scale
- Support
- Technical Marketing
3. Key Sections in Refinement Document
Metadata:
- Feature JIRA link
- Status (Not started / In Progress / Complete)
- Slack channel/thread
- Feature Owner, Delivery Owner, RFE Council Reviewer
- Product (RHOAI managed/self-managed, RHAIIS, RHEL AI)
Feature Details:
- Feature Overview (Who benefits, current state vs future state, user narrative)
- The Why (Why now, what value, customer impact, supporting data)
- High Level Requirements (As a [role], I want [capability], So that [benefit])
- Non-Functional Requirements (performance, security, disconnected env, upgrades)
- Out-of-Scope (Define boundaries)
- Acceptance Criteria (Given/When/Then format)
- Risks & Assumptions
- Supporting Documentation (links to designs, workflows, wireframes, technical docs)
Prerequisites & Dependencies:
- Architecture Review Check
- ODH/RHOAI Build Process Onboarding
- License Validation
- Accelerator/Package Support (AIPCC)
- Documentation Support
- UXD Support
- Additional dependencies
High Level Plan:
- Teams involved in delivery
- Start dates
- Work to deliver (EPICs)
- Team dependencies
- T-shirt size estimates
- Approvals/comments
4. Approval & Finalization
- Get approval from all relevant stakeholders in the refinement doc
- Copy information from refinement doc to associated JIRA feature
- Link the refinement doc in the JIRA issue (add comment with path)
- Mark refinement doc as 'Final' in title
- Make document 'Read Only' (by JIRA owner)
Best Practices
- Timeline compliance: Complete within 1 week
- Stakeholder engagement: Ensure all required teams are consulted
- Architecture review: Required if label "requires_architecture_review" is set
- License validation: Preference is Apache 2.0
- Documentation: Always link, never copy content
- Clarity: Use clear, testable acceptance criteria
RFE (Request for Enhancement) Process
Overview
RFE is the process for requesting significant new features or enhancements to Red Hat AI products.
Projects:
- RHAIRFE - Red Hat AI RFE
- RHELAIRFE - RHEL AI RFE
- RHOAIRFE - Red Hat OpenShift AI RFE
Process (High Level)
Note: Detailed RFE process will be added when the RFE Council Charter document is processed.
Key Stages
- Submission: RFE submitted to appropriate project
- Council Review: RFE Council reviews and approves/rejects
- Cloning to STRAT: Approved RFEs cloned as STRAT features
- Feature Refinement: Follow STRAT refinement process
- Implementation: Execute based on refinement plan
RFE to STRAT Linkage
- Approved RFEs must be cloned to STRAT projects (RHAISTRAT, RHOAISTRAT)
- STRAT feature must link back to original RFE
- Link types: "clones", "is cloned by", "relates to"
Common JIRA Fields for Red Hat AI
Story Types
- Feature: High-level capability (STRAT issues)
- Story: Implementation work
- Epic: Collection of related features/stories
- Bug: Defects and issues
- Task: General work items
Custom Fields
- Product Documentation Required: Yes/No
- Requires Architecture Review: Yes/No
- Feature Owner: Person responsible
- Delivery Owner: Engineering lead
- Sprint: Current sprint assignment
- Release: Target release version
- Components: UXD, Documentation, AIPCC, etc.
Labels (Common)
requires_architecture_reviewdocumentationuxdperformancesecuritydisconnectedupstream
Status Transitions
Typical Flow:
- New/Open
- In Progress
- Code Review
- Testing/QE
- Done/Closed
STRAT-Specific:
- Not Started
- Refinement In Progress
- Refinement Complete
- In Development
- Done
JQL Patterns for Red Hat AI
Find My STRAT Features
project IN (RHAISTRAT, RHOAISTRAT) AND assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC
Find RFEs Pending Review
project IN (RHAIRFE, RHELAIRFE, RHOAIRFE) AND status = "Pending Review" ORDER BY created DESC
Find Features Needing Refinement
project IN (RHAISTRAT, RHOAISTRAT) AND status = "Refinement In Progress" ORDER BY updated ASC
Find Issues Requiring Architecture Review
labels = requires_architecture_review AND resolution = Unresolved ORDER BY priority DESC
Integration with /jira:strat Command
The /jira:strat command uses this workflow knowledge to:
- Guide users through feature refinement process
- Create refinement documents from template
- Link documents to JIRA issues
- Track stakeholder approvals
- Validate completeness before finalization
Integration with /jira:rfe Command
The /jira:rfe command uses this workflow knowledge to:
- Display RFE details and status
- Show linkage to STRAT features
- Guide through RFE submission (future)
- Track RFE Council review status (future)
Tips for Using Red Hat AI JIRA
- Always link RFEs to STRAT features - Maintain traceability
- Use consistent naming - Follow "FeatureRefinement - STRAT-# - Title" pattern
- Engage stakeholders early - Don't wait until end of refinement period
- Architecture review is mandatory - If label is set, must present to forum
- Document everything - Use JIRA comments and linked docs
- Update status regularly - Keep issue status current
- Watch dependencies - Track AIPCC, UXD, Docs dependencies closely
Troubleshooting
Issue: Can't find STRAT feature for RFE
- Check if RFE is approved
- Look for "clones" link type
- Search both RHAISTRAT and RHOAISTRAT projects
Issue: Refinement taking longer than 1 week
- Identify blockers
- Escalate to Feature Owner
- Document delays in JIRA comments
Issue: Missing stakeholder approval
- Tag stakeholder in refinement doc
- Send Slack message to team channel
- Escalate to Delivery Owner if no response
Last Updated: Based on STRAT_PROCESS.md (2025-12-15)
References: