What JIRA/JIRA Agile functionality is removed or restricted from JIRA Software?

[Eunice Mora]

In the Licensing Changes page: https://confluence.atlassian.com/migration/jira-7/server_jira+agile_upgrade

has this paragraph:
"JIRA Software provides boards, backlogs, and epics that make it incredibly powerful for managing projects. In fact, over 70% of our customers currently use these features to release their software projects.
However, you might find that some of your users don't need access to these types of features. For example, users on business teams like HR or asset management might need access to only the basic issue tracking features in JIRA. These users can work on business projects by using your existing JIRA/JIRA Software license. If your existing license for JIRA Software is fully used by software users, or if you want to use JIRA Core only, you can add a license and add users of JIRA Core."

Does the above statement indicate that the boards, backlogs, and epics are now restricted/accessible only to users with JIRA Core licenses?

It seems that your road-map is to start charging for this functionality separately; however, this functionality was included on installations that have JIRA and JIRA Agile. Are you now forcing customers to pay extra for this functionality?

[Nic Brough -Adaptavist-]

No, it's the other way around - boards, backlogs and Epic functions are only available to people with JIRA Software/Agile licences.

Think of it this way (it's not quite accurate, but it will do).  "JIRA Software" in 7 is what you get when you install JIRA 6.x and then add the Agile add-on to it.  With JIRA 3.something to 6.4, if you licenced an add-on, you had to licence it at the same level that you licenced JIRA.  What they're doing now is to have you licence JIRA Core for a number of users, but you can licence the Software part at a lower level.  So 500 JIRA users, but only 250 use "Software"

[Sarah Karp]

JIRA Software is our dedicated offering for software development teams and contains the following JIRA features.

• 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

I recommend checking out the Migration Hub for more information about product, licensing, and user management changes. 

I hope that helps!

[Christian Studer CST]

Wait, what's the difference between "releases" and "versions"? I welcome the Migration Hub for it's wealth of information, but I am missing a clear and definite Core vs. Software features list.

[Andre Lehmann]

In our company also Business-Teams are using Agile-Boards. They love the Kanban-Baords. That means everyone in our company needs the board-function. Agile is not only for Software-teams! For our company that meens we jump from $10.000 renewal (jira+Jira-Agile) to $ 20.000 renewal (Jira-Software+Jira-Core). My manager doesn't know that yet but they will be very ##### and I think they are trying to find an other issue tracker -.- Double the price for the same function is not really for Atlassians-Value "Don't #### the customer"

[Stefan Ernst]

I understand Jira Software includes Jira Core for the User tier so you wont pay extra for that.

[Marek Parfianowicz]

Hi Andre, new JIRA Software is (moreless) JIRA + JIRA Agile, so it's rather unlikely that you will have to buy JIRA Core on top of this. You can see JIRA Core as a simplified version of JIRA, much easier to use by non-technical teams.

[Eunice Mora]

Are our customized workflows and other customizations supported in JIRA Software when we upgrade?
We have special status and triggers in the workflow that enforce our process.

Also, the release note has very little information and no details on what changed. Is there an upgrade note available?
https://confluence.atlassian.com/jirasoftware/jira-software-7-0-0-release-notes-776997721.html

[Nic Brough -Adaptavist-]

If you did your customisations in the UI, then the easy answer is "yes". Atlassian have always tried to make sure an upgrade leaves your system with all of your desired setup. Things like workflows, fields, screens, schemes, and all the rest of your configuration is supported and won't change (unless you've used a feature that Atlassian have changed and mentioned in the release notes). Your status are definitely going to upgrade and be supported. Triggers should be fine, I don't think they've changed anything in 7 in a way that would require you to do anything.