Hardened by default.
Setup code
A new installation can only be claimed with a one-time code from the server.
Two-factor sign-in
Authenticator apps and recovery codes; required for administrators if you wish.
Account locking
Repeated wrong passwords lock the account; a password policy refuses common ones.
Single sign-on
Google, Microsoft, Okta or any OpenID Connect provider (Enterprise).
Strict browser policy
A content security policy and hardened headers on every page.
Encrypted secrets
Jira tokens and sign-in secrets are encrypted at rest.
Signed, compiled builds
Shipped as native code with a signed file list; a modified install is detected.
Activity log
Every sign-in and change with who, when and from where, never vote values.
Administration that stays out of the way.
- Users, projects, rooms and sessions in one place; a setup wizard for the first administrator.
- Install a license key offline: CHIPS never phones home. Remove it and CHIPS drops back to Community without losing any data.
- On Linux, Apache in front with HTTPS from Let's Encrypt; on AWS, behind an Application Load Balancer if you like.
Fits the way you already work.
Jira Cloud and Data Center / Server Team and Enterprise
Import issues with JQL, send points, assignee, priority, versions and labels back, and read delivery dates.
REST API Team and Enterprise
Personal access tokens for scripts and dashboards: projects, rooms, capacity, results, the backlog, requirements, risks, the relationship map and analytics. API documentation.
CSV in, CSV out
Import a backlog of up to 10 columns, or requirements, from a spreadsheet, and download the results of any session.