4 min read

Why Upgrade Your Atlassian Stack?

By Suze Treacy on Apr 16, 2021 11:18:00 AM

Blogpost-display-image_Why Jira-Confluence upgrades are importantOne key component of managing your Atlassian products is managing their upgrades. Upgrades can present a daunting and significant time investment for many companies, generally involving apps, custom-developed plugins, and integrations, with a large number of users dependent on their success.

You know what upgrades are and that they're important. So why am I talking to you about them? Imagine the scenario, you're busy, you haven't had a chance to check in on the latest Atlassian security vulnerabilities and the emails you've received about them have been missed. You have also had higher priority work eating up team time, which has prevented the planning and execution of your Atlassian upgrades. One day, your instance comes under attack through one of the vulnerabilities exposed in the CVE. Your data is potentially exposed. An urgent, large, expensive, complex effort ensues in order to secure the instance; after 3 days, 2 full sweeps of the instance and multiple upgrades, the vulnerabilities are mitigated and your instance is safe.

Are you confident in when your applications are due an upgrade? Let's review a few common reasons why an upgrade may be recommended:

End of Life Policy

Once Atlassian has released a major feature version, it, and all iterations related to that major version, are supported for two years. After that, the versions are considered End of Life, and you will no longer receive support from Atlassian for any issues which arise. It is when reaching this point, that many people start considering upgrading their instances.

Security Vulnerabilities

Every Wednesday, Atlassian releases any new security vulnerabilities which have been identified for their server/data center products. These vulnerabilities include a security level, which is based on an Atlassian-calculated CVSS score for each vulnerability.

Severity Rating System followed by Atlassian:

Atlassian_severity_rating_system

Although there may be opportunities to mitigate security vulnerabilities in your current version, it is recommended to patch or upgrade immediately when a Critical vulnerability is identified. Vulnerabilities with a critical score generally result in root-level compromise or servers or infrastructure devices, or are straightforward to exploit.

Current security advisories can be found here:

https://www.atlassian.com/trust/security/advisories

New Functionality/Capabilities

Did you know that there is a new feature release for Jira Software every 6 weeks alone? Atlassian encourage users to submit bugs and feature requests at jira.atlassian.com. This public forum allows users to vote for and comment on submitted issues, and the Atlassian team utilize this and other feedback as a factor in their decision for what to implement next.  Platform releases contain the most significant changes, while Feature releases contain new features, changes to features, changes to supported platforms and removal of features. Feature releases can be designated as Enterprise releases, which, generally designated annually, are preferred for companies who need time to prepare for upgrades, but still want to receive critical bug fixes.

Compatibility with other Server Components

From time to time, Atlassian add and deprecate support for other server component platforms which work alongside your Atlassian application. For example, did you know that in Jira Software 8.6 and Jira Service Desk 4.6, support was added for PostgreSQL 10 and deprecated for Internet Explorer 11, whereas in Jira Software 8.8 and Jira Service Desk 4.8, support was deprecated for Microsoft SQL Server 2012 and PostgreSQL 9.4 & 9.5. To ensure optimal operation of your Atlassian instances, it's just as important to upgrade components of your server architecture, as well as your instances themselves.

Plugin Support

If you are one of the many teams who utilize plugins within their Atlassian applications, plugin compatibility and support is another area to be aware of when considering upgrades. Has support been deprecated for the plugin with the Atlassian version you're running? Is the plugin still supported when you upgrade to your target version? Atlassian have developed the Universal Plugin Manager, available in both Jira and Confluence, to enable you to screen for any compatibility problems prior to starting your upgrade. There are 4 categories for Compatibility which plugins can fall into - Incompatible (the plugin is not compatible with the target version), Compatible, Compatible if updated (the plugin is not currently compatible, but will be once running the compatible version), and Compatible once both are updated (the new version of the plugin isn't compatible with your current instance version - you need to upgrade your instance prior to updating the plugin).

Unable to Skip a Platform Release

When considering which version you'd like to upgrade to, it's important to consider your current version and your target version. When upgrading, it is not possible to skip a platform release - therefore, for example, when considering a Jira Software upgrade, it is not possible to jump from a 6.X release to the 8.X release and skip the 7.X release, you would need to take an intermediate step to upgrade to a 7.X version. Due to the functionality changes being much greater between platform releases which are not adjacently sequenced, there are more edge cases, and thus, greater risk, when navigating an upgrade spanning multi platform releases.

For assistance with upgrading your applications, partner with Praecipio Consulting's Managed Services team! Our team, fully dedicated to the Atlassian stack, offer peace of mind through managing, supporting, and maintaining your Atlassian tools, enabling you to maximize the benefits of your Atlassian applications while allowing your team to focus on their core roles. Working with our Managed Services team offers tribal knowledge and best practice from over 10 years working in the tools, allowing us to enable your Atlassian stack is optimized and operating at peak performance.

For more information on Managed Services, or anything else Atlassian related, contact us, and one of our experts will be glad to talk with you.

Topics: blog managed-services marketplace upgrade version-control-system atlassian-products marketplace-apps
4 min read

Why You Should Upgrade Your Atlassian Stack

By Suze Treacy on Sep 4, 2020 12:15:00 PM

Blogpost-display-image_Why upgrade your Atlassian stack-

One key component of managing your Atlassian applications is managing their upgrades. Upgrades can present a daunting and significant time investment for many companies, generally involving applications, add-ons, and integrations, with a large number of users dependent on the success

You know what upgrades are and that they're important. So why am I talking to you about them? Imagine the scenario: you're busy, you haven't had a chance to check in on the latest Atlassian security vulnerabilities, and you've missed the email updates based on your subscription. 

You also had higher priority work eating up team time which has prevented the planning and execution of your Atlassian upgrades. One day, your instance comes under attack through one of the vulnerabilities exposed in the CVE. Your data is potentially exposed. An urgent, large, expensive, complex effort ensues to secure the instance; after three days, two full sweeps of the instance and multiple upgrades, the vulnerabilities are mitigated and your instance is safe.

Are you confident you know when your applications are due for an upgrade? Let's review a few common reasons why an upgrade may be recommended.

End of Life Policy

Once Atlassian releases a major feature version, it, and all iterations related to that major version, are supported for two years. After that, the versions are considered End of Life and you will no longer receive support from Atlassian for any issues which arise. This is when many Atlassian Administrators start considering upgrading their instances.

Security Vulnerabilities

Every Wednesday, Atlassian releases any new security vulnerabilities which have been identified for their server/data center products. These vulnerabilities include a security level, which is based on an Atlassian-calculated CVSS score for each vulnerability.

Severity Rating System followed by Atlassian:

Screen Shot 2020-06-03 at 8.40.10 PM

 

Although there may be opportunities to mitigate security vulnerabilities in your current version, it is recommended to patch or upgrade immediately when a Critical vulnerability is identified. Vulnerabilities with a critical score generally result in root-level compromise, servers or infrastructure devices, or are straightforward to exploit.

Current security advisories can be found here.

New Functionality/Capabilities

Did you know that there is a new feature release for Jira Software every 6 weeks alone? Atlassian encourages users to submit bugs and feature requests at jira.atlassian.com. This public forum allows users to vote for and comment on submitted issues. Then, the Atlassian teams review this and other feedback as a factor in their decision for what to implement next. Platform releases contain the most significant changes, while Feature releases contain new features, changes to features, changes to supported platforms, and removal of features. Generally designated annually, feature releases are preferred for companies who need time to prepare for upgrades, but still want to receive critical bug fixes.

Compatibility with other Server Components

From time to time, Atlassian adds and deprecates support for other server component platforms, which work alongside your Atlassian application. For example, did you know that in Jira Software 8.6 and Jira Service Desk 4.6, support was added for PostgreSQL 10 and deprecated for Internet Explorer 11? In addition, in Jira Software 8.8 and Jira Service Desk 4.8, support was deprecated for Microsoft SQL Server 2012 and PostgreSQL 9.4 & 9.5. To ensure optimal operation of your Atlassian instances, it's just as important to upgrade components of your server architecture as well as your instances themselves.

App (Plugin) Support

If you are one of the many teams who utilize Apps (plugins) within their Atlassian applications, plugin compatibility and support is another area to be aware of when considering upgrades. Has support been deprecated for the plugin with the Atlassian version you're running? Is the plugin still supported when you upgrade to your target version? Atlassian has developed the Universal Plugin Manager, available in both Jira and Confluence, to enable you to screen for any compatibility problems before starting your upgrade. There are 4 categories for Compatibility which plugins can fall into:

  • Incompatible: the plugin is not compatible with the target version
  • Compatible: No adverse impacts to the target version
  • Compatible if updated: the plugin is not currently compatible, but will be once running the compatible version
  • Compatible once both are updated: the new version of the plugin isn't compatible with your current instance version and you need to upgrade your instance prior to updating the plugin

Unable to Skip a Platform Release

When considering which version you'd like to upgrade to, it's important to consider your current version and your target version. When upgrading, it is not possible to skip a platform release. For example, when considering a Jira software upgrade, it is not possible to jump from a 6.X release to the 8.X release and skip the 7.X release. You must take an intermediate step to upgrade to a 7.X version. Due to the functionality changes being much greater between platform releases that are not adjacently sequenced, there are more edge cases, and thus, greater risk, when navigating an upgrade spanning multi-platform releases.

For assistance with upgrading your applications, partner with Praecipio Consulting's Managed Services team! Our team is fully dedicated to the Atlassian stack and can offer you peace of mind by managing, supporting, and maintaining your Atlassian tools. This allows you to maximize the benefits of your Atlassian applications and empowers your team focus on what they do best. Working with our Managed Services team offers you expertise and best practices that draw from our wealth of experience and from 15 years working with the tools. We take the maintenance process off your plate, making sure that your tools–and your team–run at peak performance.

If you're ready to hand upgrades off to our experts, get it touch with our team to learn more about our Managed Services offering.

 

 

Topics: managed-services upgrade atlassian-products
4 min read

7 Step Jira Upgrade Process

By Kristopher Hall on Oct 1, 2019 2:33:00 PM

Dreading the process of an Atlassian Jira software upgrade? Depending on how many issues you have and how large your instance is, we get it - it’s overwhelming.

Below are a list of steps to help walk you through the process of achieving a successful Jira software upgrade so that you can be free of bug fixes, access new features, and operate with improved performance. Keep in mind that every situation is different, so you may need to follow additional steps in order to meet the needs of your environment.

Jira-Upgrade-Process

Step 1: Evaluate the Backend

The first part of the upgrade process is checking to see if the current backend of Jira is going to be supported - backend platforms such as your java version, operating system version, and most importantly - the version of your database. If the backend is not supported, you're going to have to upgrade/downgrade it in order to align yourself with the correct version that's supported for that version of Jira. You can learn more about supported platforms via Atlassian’s documentation

Step 2: Validate Upgrade Path

Once you've identified the support platforms of your system, the next step is to validate the upgrade path. For instance, if you are running Jira Service Desk, previous versions of Jira before 6.9 require an upgrade path to 7.0 before upgrading to 7.1 and higher.

Step 3: Test, Test, Test

It's important to make sure that the upgrade you're performing isn't going to break your production system. Start with creating a new test machine and completing a refresh of production. This will help you identify any unforeseen issues with the upgrade.

Once you have your test environment established, the next step is to run through the test upgrade. You'll want to create a runbook that can be reused for your production system. Power off the application, take a snapshot, and back up the database. Powering off the application first allows you to get a complete backup of the system.

Step 4: Add-ons

The next step is powering on your system and validating the add-ons. The add-ons page, located under the system settings, has an upgrade checker that allows you to validate which add-ons are supported under the version you're upgrading to. It will provide a list showing which add-ons are Incompatible, Compatible if Upgraded, Compatible, and Unknown (in this order). You'll want to disable all add-ons except for the ones that appear on the list as Compatible. This ensures that the upgrade process will not fail due to unsupported plugins.

Step 5: Upgrade your Production

After disabling all required add-ons, you can shut off the application and perform the upgrade installation. Download the bin file of the new version and run it. It will either ask you if you want to install a new version of the application or upgrade a current installation (which it will default to if detected). It will also ask if you want a backup of the home directory. If you've taken a snapshot in a previous step, this backup is not necessary. The upgrade installation will also identify any changes to configuration files, i.e, server.xml changes for proxy information and setenv.sh changes for added heap size or extra arguments. After the installation is complete, you will need to reapply these changes.

Step 6: Validation 

When the installation of the bin file completes, you can start up the application and the application will make the required upgrade changes in the database. When the application comes up, you can validate the application state as well as re-enable and upgrade any disabled add-ons in the previous steps.

Step 7: Post-Upgrade

As a final step, it's always a good idea to do an integrity check of the database and a reindex of the application. 

Upgrade Complete

Congratulations, your upgrade is now complete! We strongly suggest not to wait until it is too late to upgrade your software and risk damaging your production system. It is crucial to protect your software from any potential security threats or lingering bugs in your system. You also don’t want to miss out on any new features that can help drive business growth and maximize ROI.

Praecipio Consulting works with companies across different industries and realize Jira Software is an instrumental part, not just within IT teams, but across the entire business operation. Read how we helped a fortune 20 medical supply company migrate and consolidate their Confluence and Jira instances. To ensure Jira is performing in an optimal manner, our Atlassian experts at Praecipio Consulting can help you execute a smooth and seamless Jira software upgrade. Feel free to contact us should you need any help. 

 

 

Topics: jira how-to upgrade
7 min read

Team Calendars 2.3 Released

By Praecipio Consulting on Jun 26, 2012 11:00:00 AM

We’re excited to announce the release of Atlassian Confluence’s Team Calendars 2.3. For this Team Calendars release Atlassian focused a lot on helping you stay up to date with upcoming events in your team.

Here’s a list of highlights for this release…

Upcoming Events View

Atlassian’s created a new upcoming events view in the Team Calendars macro. It’s great for keeping your team informed of leave, travel or upcoming Jira project milestones. Embed it on your team homepage, or your project status page: 

 

Upcoming Events In Confluence Summary Email

Confluence 4.2 introduced weekly/daily summary email, helping you stay on top of popular and important content right from your email. Team Calendars now integrates nicely to these summary emails so you can stay updated with upcoming events in your team, project or company events right in your inbox: 

Learn more about using Jira Calendars to track your upcoming releases and issue dates.

 

Improved Confluence 4 Editor Experience

As of Team Calendars 2.2, Atlassian’s stopped adding new features for Confluence 3.5.x. You can now start taking advantage of all the new 4.0 editor plugin points.

Quickly Switch Calendar Views

Now that newer versions of Team Calendars support Confluence 4.0 or greater, you can start to make use of some of the Confluence 4.0 editor plugin points. So you can now quickly change calendar views using the editor property panel.

See Calendar Names

Previously, when you embedded a calendar on a page you would see something like “calendarID=349834j232″ in macro parameter list for the macro – which wasn’t helpful in identifying what calendars were embedded. As of Team Calendars 2.3, you will now see a preview of the calendar name(s) that you have embedded.

 
 

Other Improvements

  • For People Calendars, we now show the event summary in month and week views for some more context
  • To avoid any silly mistakes, Atlassian’s added a delete confirmation if you try to delete an event from the edit event dialog

Release Notices

  • Reminder: Team Calendars 2.2 was Atlassian’s last feature release for Confluence 3.5.x. Only critical bug fixes will be ported back to Team Calendars 2.2.x. These new features are available on Confluence 4.0 or greater.
  • The Email Summary Integration feature requires Confluence 4.2 or greater.

Upgrading to Team Calendars 2.3

Upgrading from a previous version of Team Calendars is straightforward. We recommend that you back up your Confluence database (which includes Team Calendars data) before upgrading.

  • In Confluence, simply click ‘Upgrade‘ in the Team Calendars entry of the Plugin Administration screen.
    Alternatively, download the latest release from our plugin exchange and install it via the Plugin Administration screen. This should upgrade Team Calendars to 2.3.0 (or higher).

Issues Resolved in this Release

 

 

Type
Key
Summary
Assignee
Reporter
Priority
Status
Resolution
Created
Updated
Due

 

 

 
TEAMCAL-652
Integrate with daily/weekly summary email
Matthew Erickson [Atlassian]
Matthew Erickson [Atlassian]
 
 Resolved
Fixed
22/May/12
23/May/12
 
 
TEAMCAL-116
Add new “Compact List View” to macro
David Chui [Atlassian]
Sherif Mansour [Atlassian]
 
 Resolved
Fixed
11/Jun/11
10/Jun/12
 
 
TEAMCAL-246
Add month, week and list view to Team Calendars macro properties panel
David Chui [Atlassian]
Bill Arconati [Atlassian]
 
 Resolved
Fixed
27/Jul/11
16/May/12
 
 
TEAMCAL-664
Constructing a mail should not result in resolving resources over HTTP
David Chui [Atlassian]
Fabian Kraemer [Atlassian]
 
 Resolved
Fixed
25/May/12
04/Jun/12
 
 
TEAMCAL-533
Adding a new calendar UX – clicking OK should give “Adding…” feedback.
Matthew Erickson [Atlassian]
Sherif Mansour [Atlassian]
 
 Resolved
Fixed
21/Feb/12
30/May/12
 
 
TEAMCAL-642
Macro placeholder image
David Chui [Atlassian]
Sherif Mansour [Atlassian]
 
 Resolved
Fixed
13/May/12
10/Jun/12
 
 
TEAMCAL-33
People calendar should show event description in month and week views
Matthew Erickson [Atlassian]
Sherif Mansour [Atlassian]
 
 Resolved
Fixed
24/Apr/11
10/Jun/12
 
 
TEAMCAL-634
Space picker when creating a new calendar should span the full width of the field
David Chui [Atlassian]
Sherif Mansour [Atlassian]
 
 Resolved
Fixed
08/May/12
28/May/12
 
 
TEAMCAL-605
Delete Confirmation Required in Event Edit Window too
Matthew Erickson [Atlassian]
Mark Russom
 
 Resolved
Fixed
12/Apr/12
30/May/12
 
 
TEAMCAL-668
‘Unable to format date/time’ error when viewing an event anonymously
David Chui [Atlassian]
Foo Guan Sim [Atlassian]
 
 Resolved
Fixed
28/May/12
28/May/12
Topics: jira atlassian blog calendars confluence release teams upgrade integration macros marketplace-apps
3 min read

GreenHopper 5.8 Now Available: Rapid Board for Kanban

By Praecipio Consulting on Oct 19, 2011 11:00:00 AM

GreenHopper 5.8 is now available, delivering a huge win for everyone: the new Rapid Board.

A major innovation for GreenHopper, the Rapid Board’s a flexible new board for managing and reporting on work in progress. The Rapid Board also provides multiple project support, which alone satisfies a whopping 255 votes - the most requested feature in GreenHopper’s history!

What’s the Rapid Board?

The Rapid Board provides a new way to view issues in GreenHopper by creating Rapid Views.  Creating new Rapid Views is simple:

  1. Save a Jira search
  2. Layout status columns
  3. Set Swimlanes & Quick Filters

This brilliant simplicity calls upon the most powerful search in issue tracking: Jira’s Query Language (JQL). The power of Jira’s advanced search is behind every aspect of the new GreenHopper Rapid Board. The Rapid View, horizontal Swimlanes, and button Quick Filters are all based on JQL search parameters:

This means large teams can collaborate on a single Rapid View, while individuals can use Swimlanes and Quick Filters to see just the issues that matter most to them.

Work Smarter

The new Rapid Board has several smart features in the background. Atlassian’s focused this first release of the Rapid Board on Kanban-specific features, and will continue to work on features for Scrum and all types agile teams as the Rapid Board evolves.

  • Kanban presets: an Expedite swimlane, 3 Quick Filters, default columns (To Do, In Progress, Done), and issues ordered by Global Rank.
  • Permanent links mean ‘what you see is what they get’ when emailing or IM’ing URLs – and include not only you exact view, but also the selected issue or report.
  • Keyboard shortcuts let you perform any issue operation, including selecting an issue and ranking actions, without touching a mouse.
  • Drop zones indicate the available transitions when moving an issue.
  • Column headers stay with the board when scrolling down the page, so there’s no need to scroll back up to find information or take action. 
  • Issue cards have gotten an uplift: avatars show up indicating the card assignee, and the number of days in current status are indicated by dots across the card.
  • Columns can have both a min and a max constraint: limit the amount of work in progress (WIP) for each column to keep the team moving things along.

Keep Issues Moving Across the Board

We’ve added a new Control Chart to show the mean cycle time and trends. Control Charts, along with the “time in status” dots across issue cards, help teams spot outliers and understand which issues spend a long time in flight. 

The Rapid Board views are also available as gadgets, so it’s easy to display this information on a Jira dashboard or a Confluence page. GreenHopper 5.8 is a huge step forward in understanding your teams work andcommunicating priorities and progress to the rest of the org. If you aren’t yet using GreenHopper or you want to see the new features in action, check out the short overview video.

Upgrade Jira & GreenHopper

GreenHopper 5.8 is available today, you’ll just need to upgrade to Jira 4.4.3 to take advantage of all the great new stuff! After you upgrade Jira, search your Jira plugin manager for the latest GreenHopper release.

Topics: jira atlassian blog scaled-agile kanban upgrade control greenhopper jql rapid-board

Praecipio Consulting is an Atlassian Platinum Partner

This means that we have the most experience working with Atlassian tools and have insight into new products, features, and beta testing. Through our profound knowledge of Atlassian environments and their intricacies, we can guide your organization as you navigate these important changes.

atlassian-platinum-solution-partner-enterprise

In need of professional assistance?

WE'VE GOT YOUR BACK

Contact Us