Dashboard for reviewing ideas published to JIRA from IdeaBot sessions.
- Backend: Express + TypeScript (Port 3002)
- Frontend: React + Vite + PatternFly 6 (Port 5174)
- Data Source: JIRA REST API (read-only)
npm installCreate backend/.env:
JIRA_URL=https://your-company.atlassian.net
JIRA_API_TOKEN=your-jira-api-token
JIRA_PROJECT_KEY=IDEA
PORT=3002Getting a JIRA API Token:
- Go to https://id.atlassian.com/manage-profile/security/api-tokens
- Click "Create API token"
- Copy the token to your
.envfile
All JIRA field mappings are centralized in backend/src/jira-fields-config.ts. This is the single source of truth for field IDs.
Current field mappings:
| Field Name | Field ID | Type | Status |
|---|---|---|---|
| Session ID | customfield_10060 |
Text | ✅ Configured |
| Checklist State | customfield_10061 |
Text (JSON) | ✅ Configured |
| Artifacts | customfield_10062 |
Text (JSON) | ✅ Configured |
| Products | customfield_10868 |
Multi-select | ✅ Configured |
| Strategic Priority | null |
TBD | ⏳ Not configured |
| Catcher Org | null |
TBD | ⏳ Not configured |
To update field mappings:
-
Find the correct field ID in JIRA:
curl -u email:token https://your-company.atlassian.net/rest/api/3/field | \ jq '.[] | select(.name=="Strategic Priority")'
-
Update
backend/src/jira-fields-config.ts:export const JIRA_FIELDS = { // ... other fields ... STRATEGIC_PRIORITY: "customfield_XXXXX", // Replace with actual ID CATCHER_ORG: "customfield_YYYYY", // Replace with actual ID }
-
Restart the backend for changes to take effect
Note: Fields with null mappings will display "—" or "Not specified" in the dashboard until configured.
npm run devThis starts:
- Backend API at http://localhost:3002
- Frontend at http://localhost:5174
# Backend only
npm run dev:backend
# Frontend only
npm run dev:frontendList all ideas from JIRA
Response:
{
"ideas": [
{
"id": "IDEA-123",
"ideaName": "OAuth Authentication System",
"owner": "John Doe",
"state": "In Review",
"completeness": 85,
"lastUpdated": "2026-04-30T10:30:00Z"
}
]
}Get detailed idea information
Response:
{
"idea": {
"id": "IDEA-123",
"ideaName": "OAuth Authentication System",
"description": "Implement OAuth 2.0 authentication...",
"sessionId": "uuid-here",
"sessionLink": "/sessions/uuid-here",
"checklistState": [...],
"artifacts": [...],
"comments": [...],
"owner": "John Doe",
"state": "In Review",
"completeness": 85,
"createdAt": "2026-04-28T09:00:00Z",
"updatedAt": "2026-04-30T10:30:00Z",
"jiraUrl": "https://your-company.atlassian.net/browse/IDEA-123"
}
}Table showing all ideas with:
- ID (clickable link to JIRA)
- Idea Name (clickable link to detail view)
- Owner
- State (badge with color coding)
- Completeness (progress bar)
- Last Updated
Comprehensive idea details:
- Main Content:
- Description
- Validation checklist (grouped by category)
- Comments from JIRA
- Sidebar:
- Owner
- State
- IdeaBot session link
- JIRA link
- Artifacts (attachments + external links)
| Dashboard Field | JIRA Field | Notes |
|---|---|---|
| ID | key |
Story key (e.g., IDEA-123) |
| Idea Name | summary |
Standard summary field |
| Strategic Priority | TBD (null) | Mapping to be configured |
| Product | customfield_10868 |
Products (multi-select) |
| Owner | assignee.displayName or reporter.displayName |
Falls back to reporter if no assignee |
| Catcher Org | TBD (null) | Mapping to be configured |
| State | status.name |
JIRA workflow status |
| Completeness | Calculated from customfield_10061 |
% of checklist items passed |
| Description | description |
Standard description |
| Session ID | customfield_10060 |
Session UUID |
| Checklist State | customfield_10061 |
JSON array of checklist items |
| Artifacts | attachment + customfield_10062 |
JIRA attachments + external links |
| Comments | comment |
Standard JIRA comments |
| Created/Updated | created / updated |
Standard timestamps |
npm run typechecknpm run buildThis builds both backend and frontend for deployment.
For deploying to OpenShift, see DEPLOYMENT.md.
Quick deploy:
# Build and deploy to OpenShift
make all
# Get application URL
make get-routeSee the Deployment Guide for full instructions.
When users complete an IdeaBot session and publish to JIRA:
- Session data is posted to JIRA as a new Story
- Custom fields store session ID, checklist, and artifacts
- Dashboard fetches from JIRA and displays
- Reviewers can click through to view full details
- Comments and state changes happen in JIRA
- Add filtering/search on list view
- Add pagination for large idea lists
- Add JIRA webhook sync for real-time updates
- Add PostgreSQL caching layer (Option 2 - Hybrid)
- Add state transition actions (approve/reject from dashboard)
- Add analytics view (ideas by status, completeness trends)