So next year when I renew my license do I just sign up for JIRA software and will everything from JIRA core and agile migrate over?
I am also a bit curious about what license we will be using. Being a software developing company, who also use JIRA for HR-projects, compliance and day to day tracking of issues and task for none-technical users, what license will fit us or will we be forced into splitting JIRA into 3 different deployments?
It's not a replacement, it's the next new version. 6.4 is superceded by 7.0. It's not quite as simple as "JIRA Software is the new name for JIRA + Agile", but it is close and it might be easier to think of it in those terms.
The main difference in terms of licences is the split between Core and Applications now. Let's say you've currently got JIRA 6.4 and the Agile add-on. You've got 100 JIRA licences, so you've licenced Agile at 100 users as well, because you have to.
When you upgrade to JIRA 7, to answer the main point of the question, yes, it is pretty much an "upgrade", similar to what you do for JIRA 6.1 to 6.4 for example.
After the upgrade though, you'll find you can licence the Core for 100 users still, but as you've only got 25 developers, you can licence Agile for 25 - the other 75, non-technical people don't need Agile, so you can drop their licence now.
There's a really good explanation from @Dave Meyer somewhere, but this airport wi-fi isn't letting me find it!
Hello Dawn,
Since Cloud instances are always on the latest update, changes will happen to improve JIRA .
There is a page where you can find all the changes on this release and get information about the update and the changes on every application.
Here it is the migration hub, with information of JIRA new update as a whole:https://confluence.atlassian.com/migration/jira-7
Paulo MiguelAtlassian Support | Cloud
Thanks Nic, wow, great news. Will install 7.0 on a test machine and give it a spin, but i like this idea. Will it go for all addons or only the Atlassian? We now have a 500-user license, and some plugins (think gliffy) are licensed for all 500 but really just used by 15 people..
My understanding is that some add-ons will remain add-ons (and work the same way they do now) and others can be migrated to become "applications" which can have the varying levels of licence. I don't know how difficult this would be, but I can see how some things would definitely fall out - things like script-runner or the JIRA toolkit would be add-ons because they're effectively global, but Gliffy is a prime candidate to become an application (as you say - 15 "authors" and 500 people who can just see the resulting pictures)
@Jonas Andersson,
Currently.. If you have a plugin for JIRA you need to buy licenses for the biggest license that you have. Example: JIRA Core 25 users, JIRA Software - 50 Users = Gliffy for 50 users ..
if you add one single person to Software you will go above your license .. you will have to buy an upgrade for Software and Gliffy, so you tier will look like - Core 25 Users, Software 100 Users = Gliffy 100 Users
In your case if you have 500 users you can probably break your JIRA Software into JIRA Core and JIRA Software (Example - Core: 15 Users .. Software: 400 Users) but even that you think that you will pay less, in most cases you actually pay more comparing to old JIRA + JIRA Agile pricing (if not now then in the future when you go above the limit). You will need to examine how many users you exactly have and is this a good change or not.
So this means i will be forced to know how many people are using every single add-on on JIRA? In our organization people from HR and software use gliffy, a handful use "The scheduler", 2 people use Risk Management plugin, 40 people use Agile, 10 people use "Email This Issue Plugin" among all the plugins i can think of from the top of my head. How do i know a) which users uses what. b) What category a add-on belongs to (agile is obvious but most others not.)? Do i classify every user to which license they belong? This seems like a logistical nightmare to keep track of, seeing that Jira itself does not (so far) log this? I am more confused now than before Is there a page describing the model in more detail?
I recommend keeping JIRA Software (JIRA + JIRA Agile) for long as you can .. and customize it with plugins to fit for HR-projects and all non-technical users..
I'd recommend the opposite - upgrade and licence the Software application for the tech users and Core for the non-technical ones. The only problem with that is that your non-tech users may be using Kanban boards for reporting. If they are, they'll lose them, as Kanban is part of Software.
Hmmm, this is disappointing to hear about Kanban board loss. We currently have JEMH, JIRA, Agile, Crowd (for user management) and JIRA Portfolio
Thank you Paulo but we are using JIRA server version, not cloud.
@Nic Brough [Adaptavist],
In reply to my recommendation to stay with JIRA Software as long as we can you mentioned in the comment: "I'd recommend the opposite - upgrade and license the Software application for the tech users and Core for the non-technical ones"
I am asking you then.. If you have JIRA Software that ALLOWS you tho have access to ALL Agile features and ALL Business features (that are in JIRA Core) .. why you want to upgrade and reduce number of features for all business users? Why they cannot use Agile if they still can (as JIRA Software users).. What is wrong with that thing, that non-technical users see a new tab called Agile or something specific for software teams? As soon as they have access to business projects what is bad in this?
If you can have more for LESS price then why you want to change it? I say LESS price because in most cases when you break down like you propose you will pay more (if not now then on the first tier upgrade).
I added a one, simple example already in my question: https://answers.atlassian.com/questions/30955568/what-you-think-about-jira-7-software-core-and-service-desk-in-general
Everything is on below pages:
https://confluence.atlassian.com/migration/jira-7/server_jira+agile_license-upgrade
https://www.atlassian.com/licensing/jira-software.html
https://www.atlassian.com/licensing/jira-core
Just grab a calculator and verify by yourself.
I did. In most cases for split usage (some with Agile and some without), it's cheaper. It's even better when you've got other add-ons as well.
Oh, and if you read what Dave Meyer said on your question: JIRA Core costs exactly the same as the price of JIRA. The cost to renew with a JIRA Software license is the same as the price of JIRA and JIRA Agile added together. Finally, we have reduced the price of JIRA Service Desk, so many customers will see a price decrease.
Thank you Nic, I don't see Dave's response in this chain. Perhaps he had commented in a similar post?
@Dawn Fama, This page is also for server version. You just need to switch tab in order to see it.
JIRA Software = JIRA Core (Bussiness) + JIRA Agile.
Currently your payment for 100 tier:
JIRA 100 - $4000JIRA (Agile) 100 - $2000
Sum: $6000
You can then buy JIRA Software and that is right - price is the same
JIRA Software - $6000
Let's then do a detailed analysis...
45 developers + 45 non-technical users = 90 Users
JIRA Software 50 - $3,300JIRA Core 50 - $2,200
Sum: $5,500 (+$500)
51 developers + 39 non-technical users = 90 users
JIRA Software 100 - $6,000JIRA Core 50 - $2,200
Sum: $8,200 (-$2,200)
39 developers + 51 non-technical users = 90 users
JIRA Software 50 - $3,300JIRA Core 100 - $4,000
Sum: $7,300 (-$1,300)
75 developers + 20 non-technical users = 90 users
JIRA Software 100 - $6,000JIRA Core 25 - $1,200
Sum: $7,200 (-$1,200)
20 developers + 75 non-technical users = 90 users
JIRA Software 25 - $1,800JIRA Core 100 - $4,000
Sum: $5,800 (+$200)
How much you can earn? How much you can lose? The probability that you have more developers than non-technical user is much higher than opposite. This mean that you can in most cases pay more than now only for JIRA Software.
We can continue... Let's assume that 56 people joined and you need to buy a bigger license. What then?
JIRA + JIRA(Agile)
JIRA 250 - $8,000JIRA Agile 250 - $4,000
Sum: $12,000
JIRA Software 250 - $12,000
101 developers + 45 non-technical users = 146 users
JIRA Software 250 - $12,000JIRA Core 50 - $2,200
Sum: $14,200 (-$2,200)
45 developers + 101 non-technical users = 146 users
JIRA Software 50 - $3,300JIRA Core 250 - $8,000
Sum: $11,300 (+$700)
20 developers + 126 non-technical users = 146 users
JIRA Software 25 - $1,800JIRA Core 250 - $8,000
Sum: $9,800 (+$2,200)
126 developers + 20 non-technical users = 146 users
JIRA Software 250 - $12,000JIRA Core 25 - $1,200
Sum: $13,200 (-$1,200)
How about very slight change .. add 6 more users? ...
107 developers + 45 non-technical users = 152 users
51 developers + 101 non-technical users = 152 users
JIRA Software 100 - $6,000JIRA Core 250 - $8,000
Sum: $14,000 (-$2,000)
26 developers + 126 non-technical users = 152 users
126 developers + 26 non-technical users = 152 users
What you think now? Still want to break it even that JIRA Software is including JIRA Core?
Nope. You're now arguing against tiering, which has been in place for many years. You're still not getting the point that the licences for 7 *can* work out cheaper and will if you split it up. The more expensive stuff you are using as an example here happens because of tiers, not because of the change to version 7 licencing.
Tiers have nothing to do here .. Those did not change.. I am showing you in this example that in most cases you will pay more for combination JIRA Core + JIRA Software instead of just having JIRA Software (that is having Core features included!).. Look at the numbers and scenarios.. Everything now depend on how many technical and non-technical users you will have .. if you have 45 and 45 then you pay $500 less comparing to JIRA Software .. if you have 126 developers and 26 business then you pay $2,200 more! It is simple math.. That is why I recommend staying with JIRA Software for long as people can.. You get Agile/Kanban and have business features .. What is wrong with that?
Thank you Micheal for clarifying that.
Unfortunately migration hub is not saying a word about plugins licensing. The idea is like I explained. If you have JIRA Software 100 Users, JIRA SD - 15 agents, JIRA Core 2000 users you need to buy addons licenses for 2000 users or higher ... if you have JIRA Software 100 users, JIRA SD 15 agents then addons must be 100 users or higher .. etc. And I agree with you.. if addons will start to use also a new model like JIRA right now .. it will be a nightmare to keep track of.
I don't understand why you can't see that your numbers prove that it's tiers causing the problems you're describing.
Not sure Dawn when you will renew however until then a lot o things might change. For now if you are using JIRA and JIRA Agile you are moving to JIRA Software and if you renew the price do not change and all data should be there (you are using cheaper path because new licenses are higher starting from 500 tier; this was done in order to match Cloud licenses).
It looks like you're new here. Sign in or register to get started.
