What licenses do I need for a support team and a development team ?

[Dimitri Kalokyris]

I have a team of approx 5 first line support (FLS) + 35 developpers (DEV) + 15 infrastructure (INFRA) people.

Tickets (Incidents) are managed by the FLS team as Level 1 Support.

Depending on the situation, they may move them to Level 2 : INFRA or DEV.

Next to this, the DEV people are working on new developments requiring Project licenses.

Who needs what licenses : I am confused between Jira-Core, Jira-Service Desk and Jira-Project.

Regards

D Kalokyris

CIO Fedris

[Nic Brough -Adaptavist-]

There is no "jira project" and the phrase is too vague to work out if you might mean "Jira Software" or "Portfolio for Jira", but as you don't mention planning or scale, I am gong to assume you mean Software.

I think you are going to need two sets of licences.

• Agent licences for Jira Service Desk - 5 of these for your first line support people
• Jira (something) for the other people - Infrastructure and developers sounds like it is 50 people using similar projects.

If your developers and infrastructure want to use Kanban and/or Scrum boards, then you will need 50 Jira Software licences.  If they just want to use simple Jira projects without boards, then you need 50 Jira Core licences instead. 

It might also be that you want a mix, such as Developers want boards, but Infrastructure do not, so you actually want 35 Software and 15 Core (this is a false economy though, as the licences are tiered and you'll have to pay for 50 Software and 25 Core - might as well just get 50 Software and tell the Infrastructure team that they don't have to use boards if they don't want to)

[Craig Castle-Mead]

Hey Dimitri,

To add to the answer from @Nic Brough -Adaptavist-  - there's also 3 ways to run Jira (and most Atlassian products):

• Cloud - fully managed SaaS
• Server - you download and run it on your infrastructure (even if that's in someone else's cloud). Each application runs on one server - no auto scaling/high availability
• Data Center - Download and run as with Server, but supports multiple nodes to help with scale and availability

Given the relatively small numbers you're mentioning, Cloud or Server seem to make sense, however if this is absolutely mission critical, there may still be a case for Data Center as it supports 0 downtime upgrades with Jira and provides flexibility to do A/B changes without downtime etc. While you can relatively easily compare the pricing per user/per year for Cloud/Server/DC, there's other costs that should go in to your TCO calculations like infrastructure and OS admin for the self-hosted versions that don't apply with cloud, but self-hosted may need to be a consideration based on data sensitivity/geolocation/etc.

• Jira Software
  • https://www.atlassian.com/software/jira/pricing
  • https://www.atlassian.com/software/jira/pricing?tab=self-managed
• Jira Service Desk
  • https://www.atlassian.com/software/jira/service-desk/pricing
  • https://www.atlassian.com/software/jira/service-desk/pricing?tab=self-managed

You may also wish to consider Bitbucket (git hosting) for your development team.

• https://bitbucket.org/product/pricing?tab=cloud
• https://bitbucket.org/product/pricing?tab=self-hosted

CCM