JIRA Software 7.6 Long Term Support release change log

• Project-level administration.
  Delegate some admin responsibilities to project-level admins, allowing them to edit workflows.
• Rich text editing, or 'what you see is what you get'.
• Single sign-on for Data Center.
• Zero downtime upgrades for Data Center.

• Extended project-level administration.
  Project-level admins get more privileges when editing workflows and can also edit project's screens. You can also disable this feature.
• Backlog for your Kanban projects.
• Exporting issues to HTML.
• In-app notifications to help you stay up-to-date with license renewals, new versions, and critical changes.
• Garbage collection logs enabled by default to help you and our Support teams troubleshoot your issues.

• Improved Kanban backlog: versions and epics panels to let you better manage your releases.
• Sprint goals: add goals to your sprints to let your team know what you want to achieve.
• Renaming and deleting inactive or closed sprints.
• JIRA Software Data Center on Microsoft Azure.
• Events for creating and deleting issue links.
• Syntax highlighting for additional 25 languages.

• New Czech, Estonian, Danish, Icelandic, Norwegian, Romanian, Slovak, and Polish language packs.

• Project-specific priorities.
• Live monitoring of your JIRA instance with JMX.
• Subtasks drag 'n' drop.
• X-Frame-Options to prevent clickjacking.
• 7.6.11: Support for OpenJDK 8

• High CPU usage when accessing multiple project settings
• Issues sometimes do not transition correctly and appear stuck using Automation rules
• The bundled Atlassian OAuth plugin allows arbitrary HTTP requests to be proxied

• Launching a dialog makes the page unusable in a screen reader
• Attaching an Image to an issue in a Transition screen results in Unable to render embedded object
• Users able to access JIRA while Lock re-index is occurring
• JVM instability at one node affects whole JIRA datacenter cluster
• Users that had their usernames renamed after a cache flush event will not be able to log into other nodes
• Reopening IndexReader may lead to memory leak
• FixVersion and AffectVersion JQL is slow on large instances
• Loading values into version picker on basic issue search is very slow

• ehcache.listener.socketTimeoutMillis is not used during Naming.lookup of CachePeer
• Accessing a non-existent url in JIRA during startup will break access to the instance until a restart is performed
• [Data Center] Lock contention on ehcache in DefaultGlobalPermissionManager under high load with many users
• On large instances reports utilise memory inefficiently

• Duplicated Job IDs prevent JIRA from starting
• Upgrading Jira to 7.6 causes DVCS to fail on Oracle 
• JIRA becomes unresponsive because of growing recency queue in frequently used projectRoleActors cache
• Agile boards may be up to 50% slower on boards with 100+ epics
• JIRA applinks fail if SSL certificate uses Subject Alternative Name (SAN)
• Groups with more than 2000 users will fail to display correctly with SQL Server as the database
• JIRA Lucene indexes get corrupted under high load and ungraceful shutdown
• Internet Explorer (IE) 11 throws "TypeError: Object doesn't support this action" error in Agile boards
• Performance degradation due to a high number of requests to the table propertyentry
• Accessing a non-existent url in JIRA during startup will break access to the instance until a restart is performed

Added support for:

• MySQL 5.7
• PostgreSQL 9.5
• Apache Tomcat 8.5.6 (replacing 8.0.33)

Added support for:

• PostgreSQL 9.6

Ended support for:

• PostgreSQL 9.2

Added support for:

• Apache Tomcat 8.5.29 (added in Jira Software 7.6.9)

Important notes:

• If you're planning to use MySQL 5.7.6 or later, you'll need to grant your database user an extra permission (REFERENCE).
• If you're running JIRA over SSL, you'll need to update your server.xml with the correct protocol because of the Apache Tomcat upgrade.
• We've disabled automatic XML backups. Use your native database tools to create a backup.

Important notes:

• New options added to the startup files to enable garbage collection. Just a heads up, no actions required.

Important notes:

• New JDBC driver for Microsoft SQL Server requires a new URL. If you didn't modify the original URL, you can fix it with JIRA configuration tool. If you customized the URL, you might need to change it manually.

Important notes:

• Changes to priority schemes (project-specific priorities feature) will not affect your current configuration.

Known issues:

• A fix for duplicated job IDs requires extra steps in some instances, just to be sure (checking the database if the index was created; restarting your JIRA instance.)