News

Content:

June 30, 2025

June 30, 2025:

New YouTrack Prices Starting from October 2025

We’re introducing a few changes to YouTrack prices, which will take effect on October 1, 2025.

What’s not changing

YouTrack remains free for teams of up to 10 users.
Helpdesk projects remain free for teams of up to 3 agents with unlimited reporters.
The full feature set, support, and AI Assistance continue to be included at no additional cost with the YouTrack subscriptions.

What will be changing

All active upgrade and support subscriptions will continue to work until the expiration date.
You can renew your subscription at the current pricing, but only until October 1, 2025.
After October 1, any renewal or addition of users/agents will be at the new prices.

Read on to learn about the reasons for this change, how to prepare, and what it means for YouTrack Cloud and Server customers.

Why are we making this change?

Our current pricing has remained unchanged since 2020. In fact, many long-time customers have been using YouTrack under legacy pricing introduced more than a decade ago, with full access to all features.

Since then, we’ve added significant value – Knowledge Base, Helpdesk functionality, AI Assistance, apps, and much more. The new prices reflect these enhancements and our continued investment in YouTrack.

We’re grateful to the teams that have chosen YouTrack over the years. This update will help us continue to improve YouTrack Cloud and Server for small teams and large enterprises alike.

How to prepare

Here’s what license administrators need to know to plan ahead:

Your existing Cloud or Server subscription will work at the current price until its expiration date. No immediate action is required on your side.
However, you can renew early at the current pricing. This is only possible one last time until October 1, 2025.
After that date, all renewals and user/agent additions will be at the new prices.

Below are details depending on your subscription type.

Updates for YouTrack Cloud Customers

YouTrack Cloud per-user subscriptions

If you started using YouTrack Cloud in 2020 or later, you most likely have a per-user subscription. Here’s what the price change means for your team.

YouTrack will continue to be free for teams of up to 10 users – no changes here.

If your team has more than 10 users, subscription prices will be adjusted starting October 1, 2025. For monthly plans, the new pricing starts at USD 5.40 per user per month. If you prefer an annual subscription, you’ll get two months free – the new starting price will be USD 4.50 per user per month. The larger your team, the lower your price, thanks to discount increasing as you add users. You can explore updated pricing examples in our FAQ.

Helpdesk functionality remains fully included with your subscription. It stays free for teams with up to 3 support agents and unlimited reporters. For teams with 4 or more agents, new pricing will apply: USD 6 per agent per month with a monthly plan, or USD 5.50 per agent per month with an annual plan.

All features – including AI Assistance and support – continue to be part of the subscription at no extra cost. We’re also keeping all our discounts for startups, non-profits, educational institutions, and open-source projects.

YouTrack Cloud legacy user-pack subscriptions

If you’ve been using YouTrack Cloud since before 2020 and haven’t switched to the per-user billing model, you may still be on a legacy plan with user packs.

These subscriptions will continue to work as usual until their expiration date, even after October 1, 2025. There’s no immediate action required on your side.

However, this will be the last opportunity to renew under your current pricing. If you’d like to extend your subscription one more time on legacy terms, you can do so only until October 1, 2025. After that, renewals will require switching to the new per-user pricing.

To make this transition easier, we’re offering three extra months free when you switch to an annual per-user subscription.

This plan gives you access to more flexibility and features than legacy plans could offer:

You’ll be able to add or remove users as needed – no fixed-size user packs.
You’ll also get more cloud storage – 3 GB per user.
You gain access to Helpdesk projects, starting with 3 agents free and unlimited reporters.

The new per-user pricing will take effect on October 1, 2025. After that date, monthly plans will start at USD 5.40 per user, and annual plans at USD 4.50 per user, with increasing discounts as your team grows. You can check our FAQ for examples to estimate your cost.

As always, the full set of features, support, and AI assistance are included at no extra charge. Discounts for startups, educational and non-profit organizations, and open-source projects will remain available.

Updates for YouTrack Server customers

If you’re using YouTrack Server, here’s what will and won’t change starting October 1, 2025.

What’s not changing

YouTrack Server will remain free for teams of up to 10 users – no changes there.

If you’ve purchased a license, you still own it: all existing YouTrack Server licenses are perpetual and will continue to work. Your current upgrade and support subscription will also remain valid until its expiration date.

As always, every active subscription includes the full feature set, support, and AI Assistance at no additional cost. Discounts for startups, non-profit and educational institutions, and open-source projects remain unchanged.

What will be changing

You can still extend your subscription at the current pricing, but only until October 1, 2025. After that, all renewals and the addition of new users or agents will be available only at the new prices.

We’ll continue to offer flexible user pack options, starting from 15 users and scaling up through 25, 50, 100, 250, 500, 750, 1,000, 1,500, 2,000, and more. After October 1, 2025, these will be offered only at the new pricing.

If your team is larger than 2,000, feel free to reach out to the YouTrack team to get a custom quote.

Renew and save 50%

If your support subscription is still active – or expired less than 12 months ago – you can renew it at 50% of the new license price. We’ll continue offering this renewal discount going forward.

If more than a year has passed since the expiration of your subscription, the discount no longer applies, but you can still purchase a new license and continue using YouTrack Server with all your data intact.

Helpdesk prices

Helpdesk projects remain free for 3 agents and unlimited reporters.

Starting October 1, 2025, for teams with 4 or more agents, the price will be USD 72 per agent per year.

June 18, 2025:

TeamCity 2025.03.3 Is Now Available

he major TeamCity 2025.07 update is just around the corner! But first, we’re rolling out another bug-fix release for the current version: TeamCity On-Premises 2025.03.3. Here’re some of the bugs resolved in this update:

Premature expiration of GitHub.com refreshable access tokens;
Poor build trigger performance on large TeamCity instances;
Users with read-only access to configurations cannot view their settings as code;
UI glitches like persistent popups and broken message layouts.

Bug-fix updates also include performance and security improvements, so we recommend installing them promptly. See TeamCity 2025.03.3 Release Notes for the complete list of resolved issues.

Why update?

Staying up to date with minor releases ensures your TeamCity instance benefits from the following:

Performance improvements.
Better compatibility with integrations.
Faster, more stable builds.
Enhanced security for your workflows.

Compatibility

TeamCity 2025.03.3 shares the same data format as all 2025.03.x releases. You can upgrade or downgrade within this series without the need for backup and restoration.

How to upgrade

Use the automatic update feature in your current TeamCity version.
Download the latest version directly from the JetBrains website.
Pull the updated TeamCity Docker image.

May 27, 2025:

Run Qodana Directly on Your Local or CI Machine Without Docker Containers

Until now, Qodana linters have run exclusively in Docker containers. While this approach provided consistency and isolation, it also required significant effort for environment configuration, particularly for complex project setups or highly secured systems.

Users have had to rely on the bootstrap mechanism to set up custom environments inside the Docker container, often duplicating the configuration work already done for other builds. This redundancy could be cumbersome, which is why the Qodana team got together to create a solution.

Introducing native mode in Qodana

To address these challenges, we’ve introduced native mode. First available in version 2024.1 for qodana-dotnet and Windows OS, native mode is now supported across all Qodana linters and ready to use for configuration.

Starting with version 2025.1, all Qodana linters besides third-party ones (such as qodana-cdnet and qodana-clang) can run directly on your local machines or CI environments without requiring Docker containers.

The benefits of native mode

Seamless integration: Native mode allows you to run Qodana linters directly in your pre-configured environment, which is particularly beneficial for projects with non-trivial dependencies.
Reduced setup effort: By eliminating the need to configure environments within Docker containers, native mode simplifies the setup process and reduces redundant configuration work making it easier and faster to get started.
Flexibility: While Docker remains a powerful option – especially for standardized setups – you now have the full flexibility to either set up your own Docker images using Qodana’s native mode or reuse images that already exist.

How to use native mode

If your project’s environment is already set up for compilation or testing, running Qodana in native mode can save you time and effort, making it an excellent choice for complex projects where Docker setups may not be ideal.

In this case, to launch Qodana in native mode, you need to use qodana-cli with the --ide argument.

The possible values for --ide are QDJVM, QDJVMC, QDPY, QDPYC, QDGO, QDJS, QDPHP, QDAND, QDANDC, QDNET.

qodana-cli:

qodana scan --ide QDJVM

You can run native mode on all common operating systems, including Linux, MacOS, and Windows, and in Github Actions:

jobs:

qodana:

runs-on: ubuntu-latest

permissions:

contents: write

pull-requests: write

checks: write

steps:

- name: 'Qodana Scan'

uses: JetBrains/qodana-action@v2024.2

with:

args: --ide,QDJVM

env:

QODANA_TOKEN: ${{ secrets.QODANA_TOKEN }}

If you require multiple linters for one project, we currently recommend running qodana scan multiple times and referencing separate Qodana config files per language via the –config argument.

Native mode is in Early Access

Native mode is currently in Early Access, which means it may not be reliable, may not work as intended, and may contain errors. We wanted to make this feature available as early as possible, based on the frequent user feedback we received, but we also want to fully make sure that its capabilities meet your needs and expectations.

If you run into any kind of problem, please file a ticket in YouTrack with the steps to reproduce it. This way we can make sure to address the issue in a timely manner.

May 8, 2025:

TeamCity 2025.03.2 Is Out

Today we’re rolling out TeamCity On-Premises 2025.03.2, the second bug-fix update for the major TeamCity version released in back in March. This update addresses a few product issues, such as:

Builds getting stuck in the build queue due to agent cloud profile errors;
Hanging Kubernetes Executor builds that run cross-platform msbuild commands;
“Failed to copy artifacts” errors in the Artifact Migration tool;
The project-config.xml file missing from large project clones.

Bug-fix updates also include performance improvements and security patches, so it’s always a good idea to install them as they come out. See TeamCity 2025.03.2 Release Notes for the complete list of resolved issues.

Why update?

Staying up to date with minor releases ensures your TeamCity instance benefits from the following:

Performance improvements.
Better compatibility with integrations.
Faster, more stable builds.
Enhanced security for your workflows.

Compatibility

TeamCity 2025.03.2 shares the same data format as all 2025.03.x releases. You can upgrade or downgrade within this series without the need for backup and restoration.

How to upgrade

Use the automatic update feature in your current TeamCity version.
Download the latest version directly from the JetBrains website.
Pull the updated TeamCity Docker image.

May 8, 2025:

New Single Sign On Is Here!

Configure SSO in Qodana Cloud with just a few clicks.

If you have a Qodana license with at least 10 users, you can now configure custom single sign on (SSO) support for Qodana Cloud. Quick and easy sign-ons are just another way to make access easier and improve the login experience for your team. Watch the video below and see how easy it is to implement.

Enable SSO from the organization settings, add your desired auth module, and assign users or groups to the configured Qodana roles. User states will be automatically synced if your auth module supports it.

Using your custom Qodana URL, users can now log in to Qodana Cloud or the IDE plugin via your configured identity provider.

Please note: Soon this feature will only be available for users with Ultimate+ licenses.

Talk to the Qodana team about code quality done right

If you have any questions or suggestions – or simply want to learn more about how Qodana can help your team and your business – post a comment here, tag us on X or LinkedIn, or contact us at qodana-support@jetbrains.com.

May 2, 2025:

Qodana 2025.1 Release

As we continue improving Qodana, we’re excited to introduce a set of powerful updates that enhance performance, improve security analysis, and offer better integration opportunities for you and your team. Let’s take a look at some of the most exciting changes with the Qodana 2025.1 release!

Try Qodana

OWASP Top 10: covering even more categories

At Qodana, we take security very seriously, and recently discussed inspections that commonly make it to the OWASP Top 10.

We also know that configuring taint rules for the security analyzers can be a difficult and time-consuming task, often requiring manual effort to detect rules and correctly configure it.

To simplify this process, we provide predefined taint configuration, built on various benchmarks and external providers, automatically covering common sources and sinks.

Qodana now includes predefined taint rules for the most common categories of OWASP Top 10:2021 vulnerabilities: (A01, A03, A07, A08, A10). This significantly improves issue detection out of the box, minimizing user effort while ensuring broad security coverage.

To address issues with the problem’s trace reconstruction, we had to rethink the way issue propagation being shown to the user. Now we’re capable of showing even more complex cases including tricky aliasing.

Feedback received and addressed: for those who need deeper customization, taint rules can be configured using KTS files, allowing users to define both library and user codes as sources or sinks. This flexibility ensures that security analysis adapts to project-specific needs without unnecessary complexity.

TL;DR

Automatic detection for common security flaws.
700+ new configuration entries covering common frameworks and libraries.
The ability to add configuration on your own: customize via KTS files to define sources and sinks.

Enhanced Azure & GitLab CI/CD Integrations

To improve adoption beyond GitHub, we’ve made major enhancements to Azure and GitLab integrations. These changes streamline workflows and enable better visibility into analysis results.

Azure improvements

In Azure, it’s now possible to reduce the time spent on PR analysis by only analyzing files that were changed using pr-mode. Also, instead of getting results in the build log, the Qodana extension provides you with a summary in the Extensions tab.

This release also integrates the powerful Qodana Quick Fix feature into your analysis. This allows you to fix some problems in your code and apply them to the branch you’ve analyzed or create a pull request with suggested fixes. To use this feature you will need to update the Qodana pipeline configuration.

TL;DR

Get faster PR analysis by checking only modified files.
Results now appear in the Extensions tab instead of cluttering the build log.
Auto-apply fixes to the analyzed branch or create a PR with suggested changes.

GitLab enhancements

Now you can use the new Qodana component to perform analysis in your repository. This means that instead of using the linter container directly, you can configure Qodana with a predefined set of needed arguments (there is no need to understand all the steps to launch Qodana; the component does it for you).

The new component supports mr-mode (the same as pr-mode in Azure) for fast analysis in merge requests, which analyses only the changed files, summary comments in merge requests and quick fixes. To use it you’ll need to include the Qodana component in your pipeline configuration file.

TL;DR

Use the new Qodana component for simplified configuration.
It supports merge request (MR) mode to analyze only changed files.
it provides summary comments and quick fixes.

Pro C++ Linter [EAP]

Based on demand, especially from our .NET, and Rider communities, we’re introducing Qodana for C/C++. This advanced linter goes beyond Clang-Tidy to detect critical issues like memory leaks, null dereferences, and uninitialized memory usage to name a few.

The old community-licensed linter that was previously known under this name is now called “Qodana Community for C/C++”.

Why upgrade?

The new C++ paid linter for professional teams:

Includes MISRA, and Data Flow Analysis for error tracking during value propagation.
Is a more powerful option than Clang-Tidy for bug detection.
Has easy integration with Qodana CLI and Docker.

What are DFA inspections?

DFA (or data flow) inspections are based on a more thorough code analysis, such as tracking possible variable states through possible execution paths. Such introspection allows DFA to catch some of the more sneaky errors in your code. For example, these inspections are capable of finding nullptr dereferences, memory leaks, out of bounds memory accesses, and more.

You can try this new linter using Qodana CLI or by manually running the jetbrains/qodana-cpp docker image with a token from Qodana Cloud.

Switching to Kotlin K2 Mode

We’ve enabled K2 mode for qodana-jvm and qodana-jvm-community linters. This update aligns with JetBrains’ move towards K2 in IntelliJ IDEA 2025.1 and offers improved performance and stability, along with support for new Kotlin 2.1 features.

Potential issues to be aware of:

Third-party plugins might not support K2 yet.
Some inspections are still being implemented (see details).

Need to switch back?

There are a number of ways to do this depending on the way linter is configured. But you could simply set the property “idea.kotlin.plugin.use.k2” to “false” in your linter configuration.

What to do next

If you’re using the latest tag, you don’t need to do anything to enjoy the benefits of our new Qodana 2025.1 release. If not, please change from 2024.4 to 2025.1 to update. Users of GitHub Actions, Azure DevOps, and Circle CI can find the latest version of the extension here.

With these new enhancements, you have greater potential to substantially improve your coding experience. For further information, including detailed setup instructions for each feature, please refer to our official documentation.

We’re continuously improving Qodana to provide better inspections, integrations, and security features. Stay tuned for more updates in upcoming releases. You can also stay up to date with Qodana by joining our communities on Reddit, LinkedIn, and X.

Other Qodana releases this month:

Insights Dashboard
Native Mode
Visual Studio Plugin
SSO
Qodana On-Prem Lite

April 17, 2025:

Datalore 2025.2 Is Out With Report Tabs, Extended DuckDB Support, and Snowflake Key Pair Authentication

Datalore 2025.2 introduces several new features, including report tabs, DuckDB as a data source for SQL cells, Snowflake key pair authentication, and the possibility to use a custom JDBC driver for the Datalore server, which is particularly relevant for the On-Premises version.

Datalore Cloud users have already received the new updates automatically, and Datalore On-Premises users can upgrade by following these instructions.

Before diving into this release’s features, please take note of an important upcoming change:

Starting with the next major update (Datalore 2025.3), the default Python interpreter will be upgraded to Python 3.11. This means that new notebooks will be created using Python 3.11, while existing notebooks will need to be updated manually. If no action is taken, existing notebooks will remain on Python 3.8, but they will no longer run.

For On-Premises users, we’re not planning to update previous baseline images with Python 3.8 or any previously custom-released images (Python 3.10). If you need another runtime version or if you’d like to install a third-party library to your standard environment, consider building a custom agent image.

Report tabs

Report tabs are the sections within a report that allow you to organize content into multiple views. Similar to sheets in Excel or pages in Power BI, tabs help structure complex reports by grouping related information. You can add tabs and assign selected cells and outputs to one or more of them. Each element can appear in only one tab at a time. Report viewers can navigate through the report using these tabs for a more structured and intuitive experience.

Learn more about how to build a report.

DuckDB as a data source for SQL cells

Datalore now supports DuckDB as a data source for SQL cells. With this addition, you can seamlessly query local files (CSV, Parquet, or any format supported by DuckDB) and leverage the full extent of DuckDB’s capabilities.

Snowflake key pair authentication

Following a recent announcement from Snowflake, Datalore’s Snowflake connector now supports key pair authentication, allowing you to securely connect to Snowflake without using passwords. This authentication method leverages public-private key cryptography for enhanced security.

Another noteworthy improvement to Datalore On-Premises

Custom JDBC drivers can now be used not only for data sources but also for the Datalore server itself. In certain cases, a custom PostgreSQL driver may be required to connect to the PostgreSQL database used internally by Datalore, for example, when using Amazon RDS with IAM authentication.

April 3, 2025:

Introducing TeamCity’s New Design, Phase 1

TeamCity is introducing a batch of UX/UI improvements and more in its latest release.

With the December release of TeamCity 2024.12, we updated the main navigation and breadcrumb trail. Now, we’re excited to introduce the Settings view and updated page headers, making managing your projects and builds easier.

By observing how people use TeamCity and talking to them, we discovered a common struggle – new users often get stuck when creating projects. Many resort to copy-pasting just to get through the setup, and frustration with navigation only adds to the challenge.

The new design is all about fixing these pain points and making the experience smoother and more intuitive. Here are the main changes:

A new left-hand navigation panel improves access to key TeamCity sections, adds consistency, and reduces clicks, resulting in a faster workflow.
A redesigned breadcrumb trail improves clarity by showing the current location and enhancing navigation with visible controls.
New page headers add structural clarity and navigation with a structured layout, clearer status, a Settings button, and interactive elements for key actions.
The new Settings view improves navigation in TeamCity by providing a consistent layout, allowing users to keep the Settings view open while moving through the project tree, and making settings easier to compare.

Hundreds of thousands of teams rely on TeamCity daily to handle their CI/CD process. We know that even small changes can impact your workflow, so we’ve designed every update to be valuable and seamless. Whether handling a single build or managing multiple projects, the new TeamCity experience aims to improve your work.

We hope the revamped TeamCity enhances your productivity. Now, let’s dive into the new design.

Side navigation to streamline your work

Access key TeamCity elements from the left-hand panel

Everything previously found in the TeamCity main menu at the top of the page has moved to a new panel on the left-hand side. Dedicated pages like Agents and Queue are now supplemented with relevant details.

New breadcrumb trail

Revealing hidden features and creating transparency in navigation

With the new design, we’ve added a final breadcrumb element for better clarity and introduced a visible control for easier project tree navigation.

Page headers

Optimized headers for a clearer overview

The new header design enhances usability by providing a clearer visual hierarchy, making key information like build status, duration, and test results instantly accessible. Each widget’s interactive elements allow quicker actions, reducing the need for extra clicks.

Settings view

“I guide myself by going through the build steps that I created for the last project and see if I can apply them to the current project, so let’s get a second tab.”
– Michael Backmann, TeamCity user, Customer Journey map study provided by the Market Research and Analytics team

The new Settings view improves navigation and efficiency by allowing users to keep settings open while moving through the project tree. This makes it easier to compare configurations and make adjustments seamlessly.

The addition of a project sidebar enables fast switching between projects, while the tab layout on the build configuration keeps you focused and allows space for future designs (stay tuned!). To further enhance usability, project settings are now grouped into logical clusters, making it easier to find specific elements quickly.

This structured approach reduces search time, improves clarity, and ensures a smoother workflow. Together, these improvements streamline workflows, reduce friction, and provide a more intuitive editing experience in TeamCity.

More changes to come this summer

There are many more changes to come! We’re adding a visual pipeline editor to TeamCity. This means you’ll be able to configure your builds visually (think drag-and-drop).

There will also be a new creation flow that enables creating from used VCS roots, building configuration templates, and more. Stay tuned for more changes, and please share your feedback so we can shape the product together!

Let’s shape the future of TeamCity together

We’re excited for you to get your hands on the new TeamCity and can’t wait to hear your thoughts. Please feel free to share them here in the comments, and don’t hesitate to contact our Support team if you have any questions. We’re always here to help!

June 18, 2025

May 27, 2025

1 May 8, 2025

2 May 8, 2025

May 2, 2025

April 17, 2025

April 3, 2025

Back