Home
DESIGN.mdStar on GitHub
Copied!

Project management for the AI era

Plan, track, and release great software — the #1 project-management tool agile teams trust to move fast and stay aligned.

Colors
Primary — Atlassian Blue
Blue
#0C66E4
Brand, links, primary
Blue Bold
#1558BC
Hover
Blue Classic
#0052CC
Legacy brand
Blue Subtle
#E9F2FF
Tinted bg
Status
To Do
#626F86
Neutral
In Progress
#0C66E4
Blue
In Review
#5E4DB2
Purple
Done
#22A06B
Green
Priority & Issue Types
Highest
#C9372C
Priority / Bug
High
#E56910
Priority
Story
#63BA3C
Issue type
Epic
#904EE2
Issue type
Surfaces — Dark (real ADS neutrals)
Page
#1D2125
Dark background
Surface
#22272B
Panels
Raised
#282E33
Cards
Border Light
#DFE1E6
Dividers (light)
Typography — Inter ≈ Charlie · JetBrains Mono
h1
Your team's board
38px700Inter
h2
Sprint 24 backlog
24px600lh 1.2
h3
Issue details
18px600lh 1.3
body
Break work into issues, group them into sprints, and track progress across the board in real time.
14px400lh 1.5
subtle
Updated 3 minutes ago by Priya
12.5px400muted
key
KAN-142 · move to In Progress
13pxJetBrains Mono
Signature — Board
KAN board Sprint 24 · Kanban
Click a card to advance → PS MK AJ
Components
Buttons
Search
Status Lozenges
To Do In Progress In Review Done
Assignees
PS MK AJ RT
Guardrails
DO
Keep the Jira mark's blue gradient intact and upward-facing
Use ADS status colors consistently — To Do neutral, In Progress blue, Done green
Pair issue-type and priority with an icon, never color alone
Set issue keys and metadata in the mono stack
Keep the board neutral so colored cards and lozenges lead
DON'T
Don't flatten or recolor the Jira gradient mark
Don't invent dark surfaces; anchor on the real ADS neutral scale
Don't reuse a status color for an unrelated meaning
Don't set issue keys in a proportional font
Don't put more than one primary button in an action group