Jira Software

On this page

Summary

Jira Software is an issue tracker and agile project management application. Portfolio for Jira Portfolio is a separate add-on that enables portoflio management in Jira Software. Jira Service Desk is a separate application to enable IT and customer service capablilities. Jira Core is a scaled down version of Jira Software that contains the general project managment capabilities without the software and agile-specific functionality of Jira Software.

Jira is available via 3 deploment models:

Comments/Anecdotes

From customer comment on why they won't switch from Jira: > Probably some of these features could be worked around in GitLab (e.g. by using labels exclusively). In particular for our organization we have been using Jira for much longer than GitLab. Migrating to another issue tracking system for existing project would be less than trivial, i.e. if one wants to maintain the history.

Resources

Integrations

GitLab has Jira integration that allows Jira Software to be used as an issue tracker for the planning stage while using GitLab for the rest of the DevOps lifecycle: source code managment, CI/CD, and monitoring.

Pricing

Jira Software pricing - Cloud - Flat $10 per month for up to 10 users - $7 per user/month for 11-100 users - Server: $3,600 one-time payment (50 users) - Data Center: $12,000 per year (500 users)

Portfolio for Jira pricing - Cloud - Flat $10 per month for up to 10 users - $3.50 per user/month for 11-100 users - Server: $9,900 one-time payment (500 users) - Data Center: n/a

Jira Service Desk pricing - Cloud - Flat $10 per month for up to 3 agents - $20 per agent/month - Sever: $13,200 one-time payment (50 agents) - Data Ceneter: $60,000 per year (500 agents)

Jira Core pricing - Cloud - Flat $10 per month for up to 10 users - $5 per user/month for 11-100 users - Small teams: $10 One-time payment for up to 10 users - Growing teams: $13,200 one-time payment (500 users)

Comparison

Compare to GitLab

A few missing features in GitLab that JIRA has from this comment - The concept of "Components" with a configurable set of default assignee's and associate component watchers (this is separate from "Labels", which also exist in Jira) - Multiple issue types - Configurable set of fields and screens for each issue type - Workflow definition (e.g. allowed transitions for each issue status) for each issue type - Fine-grained notifications control for each issue action