Complexity Prism Documentation

Complexity Prism helps teams assess how effectively AI tools can handle work tracked in Jira. The app introduces two core concepts:

  • AI Complexity Score - a team-voted signal from 1 to 5 that captures how ready a ticket is for AI-assisted delivery
  • AI Blockers - structured reasons why AI may struggle, such as missing documentation, weak acceptance criteria, or complex integration points
Complexity Prism issue panel showing a saved result
Issue panel after saving a complexity score with blockers

What You Can Do

  • Run collaborative voting sessions directly inside Jira issues
  • Reveal scores and discuss divergence with your team
  • Capture blockers and notes explaining why complexity is high
  • Save final results back to Jira custom fields
  • Use Quick Score for async workflows without live sessions
  • Review active sessions from project and global dashboards
No external backend
Complexity Prism stores all data in Jira custom fields and entity properties. There is no external database or external analytics pipeline for customer issue data.

Key Screens

Voting Session

Participants vote privately. The facilitator reveals scores when the team is ready.

Voting session in progress
Live voting session - scores are hidden until the facilitator reveals

Quick Score

Save a score without running a live session using the async Quick Score workflow.

Quick Score async workflow
Quick Score - select a score, add optional blockers, and save directly

Dashboards

Review active sessions and complexity trends at both project and cross-project levels.

Project dashboard showing sessions and trends
Project-level dashboard with active sessions and scoring trends

Documentation Sections

Getting Started

Installation, team member workflows (voting, Quick Score), and facilitator workflows (sessions, reveal, blockers).

Admin Setup

Field mapping, behavior settings, privacy, dual-track estimation, custom blockers, and project/global dashboards.

Security

Where app data is stored, what is retained, how permissions are enforced, and what the architecture does not send outside Atlassian.

  • Getting Started - Install, vote, facilitate, and run your first session
  • Admin Setup - Field mapping, dashboards, dual-track, and privacy settings
  • Security - Architecture, data storage, permissions, and retention
Next: Getting Started →