/jira.log

description: Log a new Jira issue to RHOAIENG with Team (Ambient team) and Component (Agentic) pre-filled.

User Input

$ARGUMENTS

You **MUST** consider the user input before proceeding (if not empty).

Goal

Create a new Jira Story in the RHOAIENG project with the correct Team and Component pre-filled for the Ambient team.

Execution Steps

1. Parse User Input

Extract the following from `$ARGUMENTS`:

• **Summary** (required): The title/summary of the issue
• **Description** (optional): Detailed description of the work
• **Issue Type** (optional): Defaults to `Story`, but can be `Bug` or `Task`. Tasks are tech debt related and not user facing. Normalize case before use (e.g. "bug" → "Bug", "TASK" → "Task") and validate against this allowlist; reject unrecognized values with a prompt to the user.
• **Priority** (optional): Defaults to `Normal`

If the user provides a simple sentence, use it as the summary. If they provide multiple lines, use the first line as summary and the rest as description.

2. Gather Cold-Start Context

**IMPORTANT**: To make this Jira actionable by an agent, gather the following context. Ask the user for any missing critical info:

**Required for Stories:**

• What is the user-facing goal? (As a [user], I want [X], so that [Y])
• What are the acceptance criteria? (How do we know it's done)
• Which repo/codebase? (e.g., `vTeam`, `ambient-cli`)

**Required for Bugs:**

• Steps to reproduce
• Expected vs actual behaviour
• Environment/browser info if relevant

**Helpful for all types:**

• Relevant file paths or components (e.g., `components/frontend/src/...`)
• Related issues/PRs/design docs
• Screenshots or mockups (as links)
• Constraints or out-of-scope items
• Testing requirements

3. Build Structured Description

Format the description using this **agent-friendly template**:

## Overview
[One paragraph summary of what needs to be done and why]

## User Story (for Stories)
As a [type of user], I want [goal], so that [benefit].

## Acceptance Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

## Technical Context
**Repo**: [repo name or URL]
**Relevant Paths**:
- `path/to/relevant/file.ts`
- `path/to/another/area/`

## Related Links
- Design: [link if any]
- Related Issues: [RHOAIENG-XXXX]
- PR: [link if any]

## Constraints
- [What NOT to do]
- [Boundaries to respect]

## Testing Requirements
- [ ] Unit tests for [X]
- [ ] E2E test for [Y]

## Bug Details (for Bugs only)
**Steps to Reproduce**:
1. Step 1
2. Step 2

**Expected**: [what should happen]
**Actual**: [what actually happens]
**Environment**: [browser/OS if relevant]

4. Confirm Details

Before creating the issue, confirm with the user:

📋 About to create RHOAIENG Jira:

**Summary**: [extracted summary]
**Type**: [parsed issue type — Story/Bug/Task]
**Component**: Agentic
**Team**: Ambient team

**Description Preview**:
[Show first 500 chars of formatted description]

This description is structured for agent cold-start. Shall I create this issue? (yes/no/edit)

5. Create the Jira Issue

Use the `mcp__jira__jira_create_issue` tool with:

{
  "project_key": "RHOAIENG",
  "summary": "[user provided summary]",
  "issue_type": "[validated issue type: normalize to Story|Bug|Task — reject and re-prompt if unrecognized]",
  "description": "[structured description from template]",
  "components": "Agentic",
  "additional_fields": "{\"labels\": [\"team:ambient\"]}"
}

Then **update the issue** to set the Atlassian Team field (must be done as a separate update call — cannot be set on create):

{
  "issue_key": "[CREATED_ISSUE_KEY]",
  "fields": "{}",
  "additional_fields": "{\"customfield_10001\": \"ec74d716-af36-4b3c-950f-f79213d08f71-1917\"}"
}

Then **add to sprint** (sprint field `customfield_10020` is screen-restricted, use the sprint API instead):

mcp__jira__jira_add_issues_to_sprint({
  "sprint_id": "[ACTIVE_SPRINT_ID]",
  "issue_keys": "[CREATED_ISSUE_KEY]"
})

To find the active sprint ID, use:

mcp__jira__jira_get_sprints_from_board({ "board_id": "1115", "state": "active" })

6. Report Success

After creation, report:

✅ Created: [ISSUE_KEY]
🔗 Link: https://redhat.atlassian.net/browse/[ISSUE_KEY]

Summary: [summary]
Component: Agentic
Team: Ambient team
Sprint: [sprint name]

📋 Agent Cold-Start Ready: Yes

Examples

Quick Story (will prompt for more context)

/jira.log Add dark mode toggle to session viewer

The command will then ask you for acceptance criteria, relevant files, etc.

Detailed Story (agent-ready)

/jira.log Add dark mode toggle to session viewer

As a user, I want to toggle dark mode in the session viewer, so that I can reduce eye strain during long sessions.

Acceptance:
- Toggle persists across sessions (localStorage)
- Respects system preference by default
- Smooth transition animation

Repo: vTeam
Files: components/frontend/src/components/session-viewer/
Related: RHOAIENG-38000 (design system tokens)

Constraints:
- Use existing Shadcn theme tokens, don't create new colours
- Must work with existing syntax highlighting

Tests:
- Unit test for toggle logic
- E2E test for persistence

Bug Report

/jira.log [Bug] Session list doesn't refresh after deletion

Steps:
1. Create a session
2. Delete the session via UI
3. Observe the list

Expected: Session disappears from list
Actual: Session remains until page refresh

Repo: vTeam
Files: components/frontend/src/components/session-list/
Browser: Chrome 120, Firefox 121

Fix should invalidate the React Query cache after mutation.

Tech Debt Task

/jira.log [Task] Migrate session queries to use React Query v5 patterns

Current queries use deprecated `onSuccess` callbacks.
Need to migrate to the new `select` and mutation patterns.

Repo: vTeam
Files:
- components/frontend/src/services/queries/sessions.ts
- components/frontend/src/hooks/

Constraints