Heads up! On March 5, starting at 4:30 PM Central Time, our community will be undergoing scheduled maintenance for a few hours. During this time, you will find the site temporarily inaccessible. Thanks for your patience. Read more.
×Does anyone else find the JIRA 7 Migration Hub absolutely useless?
It doesn't provide a migration path.
We use JIRA 6.4 for software development, does that mean we upgrade to JIRA Software?
No, somewhere else it say's that's only for JIRA Agile.
So does JIRA Core include all the functionality of JIRA 6.4?
Seems like Migration Hub has useless and is mostly a Marketing page, not an Information page.
Hi there,
Thank you for your feedback regarding the JIRA 7 Migration Hub. I'm sorry to hear you are not satisfied with the information provided on the Hub. I'm happy to answer your questions below.
We use JIRA 6.4 for software development, does that mean we upgrade to JIRA Software?No, somewhere else it say's that's only for JIRA Agile.
If you are using JIRA and JIRA Agile for software development, you will want to upgrade to JIRA Software. As an existing customer, if your JIRA license is under active maintenance as of Oct. 6th, 2015, you are eligible to move to JIRA Software at no additional cost. Your existing license key with active maintence will work with JIRA Software. When it comes time to renew support, you will simply renew your JIRA license as JIRA Software as JIRA Agile is already built into the product. The only difference you'll see is that your renewal quote will now only have one license, JIRA Software, instead of two.
So does JIRA Core include all the functionality of JIRA 6.4?
JIRA Core is our new purpose-built offering for business teams. The majority of business teams do not need the software specific features of JIRA Software. Thus, they've been removed. If you're familiar with JIRA today, the features that have been removed to simply the business user experience are:
* Development tools integration panel (released in JIRA 6.3)
* Releases tab (from JIRA 6.4)
* JIRA Core will still have all the existing Versions functionality
* Automatic issue transitions (from JIRA 6.3)
* Builds, Source, and Reviews project tabs
* Software development project templates
* Roadmap gadget
* Roadmap project tab
Hope this explains!
Cheers,
Loren
Atlasisan Customer Advocate
Hi if you migrate from jira 5.2(jira+jira agile) with active license to JIRA 7 ,
will their be any additional cost of licenses for JIRA 7 software
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, your licence entitles you to run any Jira versions 4.0 to 6.4 with the Agile add-on, and Jira Software 7.x.
The easier way to think of it is that Jira Agile has simply moved from being a plugin to being an App, and been renamed. The licence entitlement has not changed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
bharat > They did increase the costs of the JIRA product line. Even if you stay with the current 5.2, when renewing will require using the JIRA Software license.
Here is some information that could help:
https://confluence.atlassian.com/migration/jira-7/server_jira+agile_license-upgrade
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is not quite true, but the way to think of it is:
JIRA Core = JIRA
JIRA Software = JIRA + Agile
JIRA Service Desk = JIRA + Service Desk
The main question is not what you're using JIRA for, but how. If you're using Agile, then you need to go to JIRA Software. If you're not, then no, you can just use JIRA Core.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This was the concept.
To clarify the answer; JIRA 6.4 (and earlier) has functionality that was removed in JIRA Core.
So if you are using JIRA 6.4 (or earlier), you may need to use JIRA Software.
Hence the reason that the older JIRA license works on JIRA Software.
As stated, it will depend on what features were previously used.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>To clarify the answer; JIRA 6.4 (and earlier) has functionality that was removed in JIRA Core.
No, that is wrong. Some minor functions were tidied up, and some already deprecated stuff completely removed from the API, but no functionality was really removed from Core.
If you are using Jira 6.4, you need to check if you are using the Jira Agile add-on. If you are, then you should move to Jira Core + Jira Software. If you are not, then you can just get Jira Core.
The reason that the older Jira licence works on Jira Software is that Atlassian made the licences for Jira Software and Jira Agile compatible, as they're equivalent.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> [..] no functionality was really removed from Core.
This statement implies functionality was removed.
If you read the statement from the Atlassian Team member:
> [..] the features that have been removed [from] the business user experience are:
> * Development tools integration panel (released in JIRA 6.3)
> * Releases tab (from JIRA 6.4)
> * JIRA Core will still have all the existing Versions functionality
> * Automatic issue transitions (from JIRA 6.3)
> * Builds, Source, and Reviews project tabs
> * Software development project templates
> * Roadmap gadget
> * Roadmap project tab
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
mmm, you'll notice that those were not "removed", they were chosen to be part of Software, not Core, although they did change shape a bit.
No functionality was removed from Core, it was decided that as the applications split, some things needed to be in Software, rather than Core.
So, while that quote is sort of technically accurate, in this context where we're talking about Jira Software, nothing has gone. You just need Software to provide Software related functions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We integrate JIRA with Fisheye and Crucible.
JIRA 6.4 (and earlier) allowed integration with Fisheye and Crucible.
JIRA Core does not support "development tools" i.e. Fisheye and Crucible.
JIRA Software does support integration with Fisheye and Crucible.
There was functionality removed when moving to JIRA 7 at the same price point.
JIRA 6.4 cost $600.
JIRA Core cost $600.
JIRA Software cost $900.
In order to get the same functionality as JIRA 6.4 (without Agile) we had to move to JIRA Software.
I spent a long time with support on resolving this.
They don't want to use the word "removed" because it sounds bad. "Decided to no longer be part of the base JIRA product anymore." sounds better than removed from base product.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am afraid you are still missing the point - Jira Core is what you used to get with Jira, Jira Software is what Agile used to add to it. A couple of functions from Agile were moved into Software because they made no sense to keep in Core when they were Software related functions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You have missed the point.
We used JIRA (without Agile), and still required moving to JIRA Software.
Agile was not the only thing lost in JIRA Core.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So does JIRA Core include all the functionality of JIRA 6.4?
No. It does not, read Loren Siegel answer for details.
Simple way to look at it.
JIRA Core = JIRA (if using business functionality)
JIRA Software = JIRA (if using software functionality)
JIRA Software = JIRA + Agile
JIRA Service Desk = JIRA + Service Desk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.