Important changes to our server and Data Center products
We’re making changes to our server and Data Center products, including the end of sale for new server licenses on February 2, 2021 and the end of support for server on February 2, 2024. Learn what this means for you.
Server product investments
What have we shipped?
This past year we’ve been hard at work making sure you have a platform you can depend on, across all of our products. Learn about some of the key improvements we shipped over the past year in our server products below.
Jira Software & Jira Core
- License check performance improvements: Checking users against license tier had been affecting product performance. We improved performance for limited tier licenses by improving the average response time by 65%.
- Favorite Filters gadget control: For large filters, counting all of the issues can impact performance. To give you more control, we've added a global setting that lets you control the max timeout for this popular gadget. If the issues take too long to load, we’ll stop counting them and instead display a “Too many issues” message.
- Refreshed Velocity Chart: Our completely reimagined Velocity Chart allows you to see more than seven sprints and shows up to 120 sprints. This new chart also lets you choose a pre-defined timeframe or custom date range, shows the average velocity of your team, and has a new look-and-feel with some cool features like focus that lets you zoom in on the right sprint.
- Ability to restrict sprints: To limit the possibility of linking issues to the wrong sprint, we’ve enabled a new admin option to restrict the sprint selection (available in the Sprint drop-down) to the sprint the project user selects. With Relevant sprints selected, you’ll only see the sprints that belong to the project you select on the page. To see sprints that aren’t linked to any project you can select Show all to have all sprints display.
Improved reliability and stability
- Fix to ‘View Board’ function: We fixed a pesky bug in which the ‘View Board’ function would break upon the removal (or disabling) of an LDAP directory with a group that had been added to the Board Administrator. Now, View Boards shows all the boards as expected regardless of any LDAP directory changes.
- Safeguarding performance in massive spaces: When loading a page tree, lots of permission checks are needed to make sure people don’t see pages that are restricted. In a very large space, these checks can consume a lot of memory and CPU and have an impact on the overall performance of your site. Now when you visit a space, we'll load a maximum of 200 pages at each level of the hierarchy. You can then hit the Show all pages button to load all the pages in the space in one go.
- Less log spam: Tired of receiving erroneous error messages about a failing LaasPerformanceLoggingJob job in your test instances of Confluence? The LaasPerformanceLoggingJob job has been removed on startup to avoid confusion, log spam, and conserve resources allocated to running the job.
File editing enhancements
- Companion keeps getting better: We overhauled Companion (the app that enables you to edit any file type in Confluence) and we haven’t stopped improving it since! We’ve made it easier for you to upload files with confidence. You’ll be warned if a new version of a file has been uploaded since you started editing a file. You can either discard your changes or continue to upload your changes as a new version in the file history. You can even set trusted domains before rolling out the Companion app for all users.
User experience improvements
- More cell colors: You can now choose from 49 different table cell colors, including pure black and all the colors of the rainbow. The old colors are still available, so your existing tables will look just fine. And we hope you enjoy making table art as much as we have.
- Template page anchor link fix: We’ve fixed a bothersome bug that prevented you from adding anchors to a template. Now you can anchor link away!
- Automate business-critical tasks with webhooks: Webhooks are a way for one application to notify another application, in real-time, when an event happens. You could use a webhook to tell your chat application to create a new channel or room whenever someone creates a new space for their team or project. Confluence will listen for the 'create space' event, and send a message to the URL provided by your chat application (the endpoint).
Jira Service Management (formerly known as Jira Service Desk)
Scale and compliance improvements
- Improvements to SLA processing: For some customers with large datasets and frequent updates, the SLA calculation for all issues would either slow down or stop working entirely. To prevent this issue from occurring and to keep SLA calculation consistent, we made changes to the way the SLA calculation operations are serialized. Now, Jira Service Desk is much more resilient under high load.
Notification and email enhancements
- Enabling notifications for agents acting as customers: By default, agents and admins working on Service Desk projects and occasionally acting as customers would not receive any notifications about internal comments or changes unless these changes were publicly visible. Now, we prioritize the agent role when the agent also acts as customers or approvers. For help further managing notifications, please see this page.
- Fix to “View Request” link in email: Previously, when clicking on the “View Request” link in an email notification, a user was redirected to the instance rather than the issue in Service Desk. With this fix, the “View Request” link in emails will now redirect to the Jira issue link (accessible to licensed users).
- No more duplicate attachments: When customers raise requests over email, the email body is added to the request’s description. You’ve told us that this often includes some unwanted media like marketing images, company logos, and everything else from the email’s footer. You can now detect and ignore any duplicates, leaving your requests nice and clean.
Better experience for agents and users
- Keeping your requests private: From now on, any new requests created in the customer portal will be set to private by default, and you’ll need to specifically choose to share it. As for requests raised over email, we created a new option in the Jira Service Desk configuration to let you choose- keep them private or share away with your customers.
- Request Participants from the Create Issue screen: Previously, the only way to request participants was from within an issue. Now, users are also able to request participants from the create issue screen.
- Multilingual customer support: Help your customers in their preferred language with our multilingual customer portal and help center. You can add additional languages to your service desk and provide translations for the most important items- these translations will be displayed in portal names, request types, and announcements.
Compliance and security improvements
- Push traceability: We introduced push logs to bring you a more streamlined audit of information whenever you need to quickly find specific information about how the branches in a repository have changed over time. Your admins now have visibility into details such as who pushed certain commits and who was responsible for creating or deleting branches.
Developer experience enhancements
- Integrated CI/CD: To help you streamline your workflow, we’ve given you two new ways to get continuous feedback on your code – a new Builds page and a new Builds tab on the Pull requests page. Now when you integrate your instance with Bamboo, Jenkins, or another CI application, you’ll see build results and additional related info on these two pages, right next to your code where it’s most valuable.
- New pull request experience: The pull request page has been redesigned and packed full of improvements to make your code review experience smoother, more enjoyable, and less of a tedious task. Some highly requested changes include commenting, syntax highlighting, task improvements, and file tree improvements.
- Fix for pull request in diff display: All changes in the diff view of a pull request are guaranteed to always be visible. If an initial request returns a truncated diff, it’ll fall back to fetching the diff with minimal context (10 lines each side of the change). This will guarantee that you will see all changes in the diff, provided this new diff with minimal context doesn’t exceed 10,000 lines (a warning will show if this is the case).
- View hidden comments: Want more context on why code has changed throughout a pull request? By selecting the other comments counter when it appears on your pull request you now have the ability to view a file’s activity stream showing comments that are outdated or appear on another diff.
- Disable keyboard shortcuts: We introduced keyboard shortcuts a while back to provide a quick and easy way of navigating through Bitbucket and performing common actions without having to take your fingers off the keyboard. However, you’ve let us know that these keyboard shortcuts can be detrimental to usability and accessibility. To give you more flexibility, you now have the option to disable keyboard shortcuts in your account settings.
Developer experience enhancements
- Conditional tasks: You can now mark your tasks as conditional by using variables and regular expressions to create conditions that have to be met to run a task. By deciding which tasks aren’t mandatory, you can skip build steps in plan branches. You can set conditions for tasks through Bamboo UI or by using Bamboo Specs.
- Remote agents' workspace cleanup: To make cleaning up build directories in remote agents easier, we’ve made it so now build and deployment workspaces are automatically removed from remote agents' home directories if corresponding entities are removed on Bamboo Server.
- Enhanced plan branch configuration: We’ve given you new configuration options for plan branches so that you can create a custom plan branch that differs from the default branch. This means you now can test your custom changes to your plan branch without needing to copy your changes to the master and have custom configurations for individual branches.
- Webhooks: Bamboo webhooks allow you to send selected real-time information about Bamboo to third-party applications. For example, you can display a Bamboo build status in your team’s chatroom or signal an alarm in case a plan fails.
- Export/View Plan as YAML: You can now you can export your existing plans and deployments to Bamboo YAML Specs automatically, which will facilitate the migration of your Bamboo plans to configuration as code. Moving to YAML Specs has never been easier! What’s more, you can now view a plan as YAML as well.
- Better logs: Excessive logging is known to cause serious performance problems including build result processing timing out (grey builds). That’s why we’ve made it possible to turn live log transmission off, which is one way to mitigate this problem.
Enterprise and scale improvements
- Customized Bamboo headers: Tired of how Bamboo looks? Now, you can change the color of the Bamboo header, introduce your own custom logo, and change the favicon. This can come in handy when navigating among multiple Bamboo instances or if you want to introduce your own branding.
- Project-level variables: Previously teams had to rely on a Bamboo administrator to add/remove/modify the global variables being used, which could lead to bottlenecks. That’s why we created project-level variables that do not require Bamboo administrator access to set up. Project variables are defined for a specific project and have the same value for every plan that belongs to the project.
- Universal Plugin Manager (UPM) included in Crowd: Crowd is now bundled with the Universal Plugin Manager (UPM), which allows you to manage apps from within Crowd. You can use UPM to find, install, manage, and configure apps from Atlassian Marketplace, to which UPM connects. Alternatively, you can also point UPM to an app's location on your computer.
Performance and scale improvements:
- Improved full sync performance of an application with multiple directories: Fetching non-aggregating memberships is now several times faster. Depending on the data size and shape full sync time should decrease by minutes for ~100k users or hours for ~1M users.
- Improving authentication performance for multiple directories: You can now speed up authentication by optimizing the priority of cached directories. If the authenticating user doesn’t exist in any of your cached directories, Crowd will move them to the end of the queue. This helps Crowd focus on the right directories and save your users some time.
- Improved performance of nested groups: We've improved the efficiency of how Crowd handles nested groups. This small change brings significant performance improvements for user authentication, permission checks, and the user groups screen.
Viewing and sharing your plans
- Save a view of your plan: Save multiple configurations of filters, view settings, fields, and more. Use this to establish a default view for your plan, convey the appropriate information for all viewers, or pick up planning where you last left off.
- Export a plan to CSV: Exporting plan data by CSV allows for a deeper analysis of information for even greater insight. You now have the option to Export plan data, making it available to work with using external tools. The exported data can also be used to support third-party integrations.
- Roll-up dates in plans: By rolling up dates in your plan, you can see, at a glance, when an Epic or higher-level issue in your hierarchy is due to start and finish based on the dates of its children. If there’s an arrow in the date field or stripes on the schedule bar, you’ll know it’s rolling up.
Plan with your team’s capacity in mind
- Edit sprint capacity directly on your timeline: Adjust your team's future sprint capacity for a more accurate read on the feasibility of the work you’ve scoped out over time.
- New velocity insights in sprint capacity details: When viewing sprint capacity details, you now get graphical insights on your team's velocity at a glance. We've also added the View velocity chart link so you can quickly view your team's historical velocity. This lets you get a more realistic sense of whether or not planned work can be delivered on time.
- Edit dates for future sprints in Jira: In addition to planning future work, you now have control to set specific start and end dates, allowing you to put space between sprints, or change the duration of a sprint.
- Enhanced capacity distribution: Distribution for sprint capacity is now "smarter" because it takes into account sprint assignment followed by end dates, hierarchy levels, and issue ranking if there is no sprint assignment.
We’ve made a number of bug fixes and have several upcoming improvements to resolve issues where events aren’t reflecting/updating with the correct details, actions that have unexpected results, and issues that affect Team Calendars when used at scale, check out our community post for more details.
Questions for Confluence
We’ve made several updates over the past year. Learn more in our release notes.
The information on this page contains forward-looking statements which involve uncertainties when providing estimated effective dates. All forward-looking statements involve known and unknown risks, uncertainties, and is subject to change.