Work Items
Work Items bridge the gap between requirements engineering and implementation. When a requirement is approved, it can become a trackable work item with status, priority, and optional Jira integration.
Overview
Work Items provide lightweight implementation tracking directly within NirmIQ:
- Status tracking: To Do, In Progress, In Review, Done
- Priority levels: Low, Medium, High, Critical
- Source tracking: Where the work item originated (Code Intelligence, Knowledge Base, Manual)
- Jira integration: Push work items to Jira as issues with one click
- AI context export: Copy rich requirement + FMEA + knowledge base context for AI coding tools
Creating Work Items
Automatic Creation (Recommended)
When a requirement reaches Accepted status, NirmIQ automatically creates a work item for it. This is the standard flywheel:
AI generates requirement suggestion
-> Engineer reviews and approves
-> Requirement reaches "Accepted" status
-> Work item auto-created (status: todo, source: code_intelligence)
Manual Creation
You can also create work items manually for any Approved or later requirement.
Work items can only be created for requirements with status Approved, Accepted, Implemented, or Verified. Draft and In Review requirements cannot have work items — this prevents premature implementation tracking and ensures only reviewed requirements enter the implementation pipeline.
From the Requirements View
- Select a requirement with Approved+ status
- The Work Items panel shows a Create Work Item option
- Set priority and add optional notes
Accessing Work Items
From the Sidebar (Project-Level)
Access the Work Items panel from the sidebar navigation (Work Items icon). This shows all work items across the entire project.
From the Tracking Tab (Requirement-Level)
Select any requirement, then click the Tracking tab in the detail panel. This shows the work item for that specific requirement with quick status transitions and external tool links.
Work Items Panel (Sidebar)
Summary Dashboard
The top of the panel shows:
- Total count of work items
- Status breakdown: To Do / In Progress / In Review / Done (click to filter)
- Progress bar: Percentage of work items completed
Work Item Cards
Each work item card displays:
- Requirement ID (e.g.,
SYS-001) with link back to the requirement - Status badge (color-coded)
- Priority indicator (Low/Medium/High/Critical)
- Requirement text (truncated)
- Source (Code Intelligence, Knowledge Base, or Manual)
- External tool link (Jira badge if pushed)
Quick Actions
- Start / Review / Done: One-click status transitions
- Copy to AI: Copies rich context (requirement + FMEA + knowledge base) to clipboard for AI coding tools (Claude, Copilot, Cursor)
- Push to Jira: Creates a Jira issue from the work item (when Jira is configured)
- Edit: Change status, priority, or notes
- Delete: Remove the work item
Push to Jira
When Jira is configured for your project, each work item shows a Push to Jira button.
How to Push
- Click Push to Jira on any work item that isn't already linked
- Enter the Jira Project Key (e.g.,
PROJ,DEMO) - Select Issue Type: Task, Story, or Bug
- Click Create Issue
What Happens
- A Jira issue is created with the requirement text, ID, and metadata
- The work item is automatically linked to the Jira issue
- The Jira issue key (e.g.,
PROJ-123) appears as a clickable badge on the work item - Priority is mapped: Critical -> Highest, High -> High, Medium -> Medium, Low -> Low
Requirements
- Jira must be configured at the project or user level (see Jira Integration)
- The "Push to Jira" button only appears when Jira is configured
- Each work item can only be pushed once (the button disappears after linking)
Demo Flow
A typical demonstration flow showing the full requirements-to-implementation lifecycle:
1. Create a requirement (or accept an AI suggestion)
2. Review and set status to "Approved"
3. Accept the requirement -> work item auto-created
4. Open Work Items panel -> see the new work item
5. Click "Push to Jira" -> enter project key -> create issue
6. View the Jira badge on the work item
7. Progress through: Start -> Review -> Done
8. Check FMEA coverage for the requirement
9. Generate a new requirement from FMEA findings
10. Accept it -> new work item -> push to Jira
Tier Requirements
| Feature | Required Tier |
|---|---|
| Work Items CRUD | Basic+ |
| Batch Work Items | Basic+ |
| Push to Jira | Basic+ (with Jira configured) |
Troubleshooting
"Work items require Approved+ status"
This error appears when trying to create a work item for a Draft or In Review requirement. Move the requirement to Approved status first.
"Push to Jira" button not visible
- Verify Jira is configured: check Settings -> Integrations -> Jira
- Ensure the work item isn't already linked to a Jira issue
- Check that your subscription tier is Basic or higher