[FEATURE] Implement test case generation directly inside TestPlanIt for Jira plugin

[therealbrad]

Feature Summary

Add a "Generate Test Cases" button directly in the TestPlanIt Jira plugin
panel so users can trigger AI test case generation from a Jira issue without
leaving Jira.

Problem Statement

The current workflow for generating test cases from a Jira issue requires
the user to context-switch into TestPlanIt, find or import the issue, and
trigger generation from there. For QA engineers and developers who live in
Jira, this friction reduces adoption of one of TestPlanIt's most compelling
features.

Current Situation

• Test case generation from Jira issues is available inside TestPlanIt
• Users must leave Jira, navigate to the correct project in TestPlanIt,
  locate the linked issue, and trigger generation manually
• The Jira plugin panel is already embedded on issue pages but does not
  expose this workflow
• Teams that primarily work in Jira may never discover the feature exists

Desired Outcome

• A "Generate Test Cases" button appears in the TestPlanIt panel on any
  Jira issue
• Clicking it triggers the existing AI test case generation workflow using
  the issue's summary, description, and acceptance criteria as context
• Generated test cases are created in the linked TestPlanIt project and
  immediately visible in the panel without requiring the user to leave Jira

Proposed Solution

Extend the existing TestPlanIt Jira plugin panel to include a "Generate Test
Cases" button that calls the existing test case generation API endpoint,
passing the current Jira issue as context.

User Story

As a QA engineer or developer working in Jira, I want to generate test
cases from a Jira issue directly within the Jira issue panel so that I
can create test coverage without interrupting my workflow or switching to
another tool.

Acceptance Criteria

• A "Generate Test Cases" button is visible in the TestPlanIt Jira plugin
  panel on issue pages
• Clicking the button triggers test case generation using the issue's
  summary, description, and acceptance criteria as input
• User can select the target TestPlanIt project and folder before
  confirming generation (if not already linked)
• A loading/progress state is shown while generation is in progress
• Generated test cases are displayed in the plugin panel upon completion
  with a link to view them in TestPlanIt
• If no TestPlanIt project is linked to the Jira project, the user is
  prompted to link one before proceeding
• Works in both Jira Cloud and Jira Server/Data Center
• Button respects TestPlanIt permissions — only users with canAddEdit
  on TestCaseRepository see it

Design Mockups

Panel layout (existing → proposed):

Existing panel:
┌─────────────────────────────────┐
│ TestPlanIt │
│ Linked Test Cases: 3 │
│ [View in TestPlanIt] │
└─────────────────────────────────┘

Proposed panel:
┌─────────────────────────────────┐
│ TestPlanIt │
│ Linked Test Cases: 3 │
│ [✨ Generate Test Cases] │
│ [View in TestPlanIt] │
└─────────────────────────────────┘

On click → inline confirmation/options:
┌─────────────────────────────────┐
│ Generate Test Cases │
│ Project: [My QA Project ▼] │
│ Folder: [Sprint 12 ▼] │
│ [Cancel] [Generate] │
└─────────────────────────────────┘

Alternative Solutions

Option 1: Jira Automation Action

Expose test case generation as a Jira Automation action so it can be
triggered by rules (e.g., "when issue moves to In Progress, generate test
cases"). More powerful but significantly more complex to implement and
harder for users to discover.

Option 2: Link in Issue Description

Add a deep link in the TestPlanIt panel that opens TestPlanIt pre-loaded
with the issue context, reducing clicks but still requiring a context switch.
Faster to build but doesn't solve the core problem.

Technical Considerations

Dependencies

• Requires API changes (plugin must be able to call generation endpoint
  with Jira issue context)
• Requires UI/UX design review (panel layout, loading states, error
  handling)
• Requires third-party integration (Jira Cloud Connect / Forge framework,
  Jira Server plugin API)

Performance Impact

Test case generation is an async AI operation. The panel should show a
non-blocking progress indicator and poll for completion rather than holding
the request open. Consider using the existing BullMQ worker architecture
with a job status endpoint the panel can poll.

Security Considerations

• The plugin must authenticate to TestPlanIt using the existing OAuth/API
  token mechanism — no new auth surface needed
• Permission check must happen server-side in TestPlanIt before generation
  begins, not just in the panel UI
• Issue content (summary, description) sent to the generation endpoint
  should follow the same data handling path as existing generation workflows
• For customers using local LLM (Ollama), issue content never leaves their
  network — this is a significant advantage for security-conscious enterprise
  customers in regulated industries such as banking, healthcare, and government

Business Value

Priority

• High - Significant improvement

Affected User Groups

• Test Managers
• QA Engineers
• Developers
• Project Managers

Expected Usage

• Daily
• Weekly

Implementation Effort

• Large (1-2 weeks)

(Plugin UI changes, API endpoint for plugin-triggered generation, polling
mechanism, project/folder selection UI, Jira Cloud + Server compatibility
testing)

Related Issues/Features

• Related to: Jira integration (JiraAdapter.ts)
• Related to: AI test case generation from issue workflow
• Related to: Atlassian Marketplace app approval

Additional Context

This feature is particularly high-value for enterprise prospects evaluating
TestPlanIt as a replacement for Xray. Xray's core value proposition is that
test management lives inside Jira — teams never leave. This button directly
closes that perceived gap by bringing TestPlanIt's most differentiating
feature (AI generation) into the Jira interface.

For enterprise customers in regulated industries using local LLM support,
the ability to generate test cases from Jira without data leaving their
network is a unique selling point no other Jira-integrated test management
tool currently offers.

Examples from Other Tools

• Xray: Native Jira panel with test creation directly on the issue —
  this is the primary UX pattern Xray users are accustomed to
• Zephyr Scale: "Create Test" button available from the Jira issue panel
• qTest: Jira panel supports test case creation inline

Checklist

• I have searched for similar feature requests
• I have provided a clear problem statement
• I have described at least one solution
• I have considered alternatives
• This feature aligns with TestPlanIt's goals