Do you want to minimize the potential damage to your organization from a compromised account? Administrators can now enforce two-factor authentication for the following organization-wide roles:
Navigate to the Administration tab on the left-hand panel, click on Roles, select the desired role, and then toggle Require two-factor authentication. Each user within the selected roles will be required to set 2FA on their next login in order to access the organization, and will receive an email reminder to do so.
To add even more flexibility in setting up access protocols, you can create a Custom role and manually assign teams or individual users to it. As an admin, you will always be able to see which user hasn’t set up 2FA yet.
We've just added Space Automation alerts to subscriptions, which are a flexible way to manage notifications in Space!
You can now receive notifications about finished and failed Automation jobs in a single feed, along with your other Space notifications, and customize them to match your workflow.
Space subscriptions allow you to get notifications about different events and create personal or group feeds with custom alerts. Read this post to learn more about them.
With this update, you can choose whether you want to receive alerts about all finished Automation jobs, only those that failed, jobs run by you, or those containing your commits.
By default, your job notifications will automatically be sent to your #Spacebox channel. You can customize the events for different jobs in the settings.
You can also subscribe to notifications centrally instead of going to a specific job to set up custom alerts. Subscribe to a specific project repository and get notified about all jobs, sets of jobs, or a specific job. You are also free to choose which events you want to be notified of.
The custom Automation subscriptions are useful if you want to be aware of all failed jobs on a specific project instead of monitoring the status of each job individually.
Introducing a new Schedule view for your calendar in Space!
You can now get a different perspective on your monthly schedule with an ordered, day-by-day list of events. The Schedule view is more convenient than the regular view if you want to see a full overview of what's coming up, in order.
Want to see the busy days only? Hide the days when you have no meetings or plans in your calendar by clicking on the gear icon and unchecking the Show days with open schedules option.
Have you been looking for a private Dart package storage solution? Space Packages now lets you create your own Dart repositories. Use them to store and share Dart packages for your mobile, console, or Flutter projects.
To create a Dart repository, go to <your project> | Packages, click on New repository, and select Dart repository. Read this article to learn about how to publish and manage Dart packages.
You can now archive and delete both personal and project documents in Space.
By default, only project administrators have the permissions to delete and archive project documents; however, they can provide this permission to other roles in your organization.
Developing applications for Space is getting easier! The Authorization Playground is an interactive way to learn how app authorization works, and you can experiment with different authorization flows for your apps right in the Space UI.
Space supports app authorization with a permanent token and OAuth 2.0 flows. The playground allows you to check authorization requests and permissions granted, and you can also quickly generate code snippets that allow you to authorize your application.
To access the playground, go to Extensions > Authorization Playground. Read this article to learn more about authorizing apps in Space.
The Space plugin is now bundled with WebStorm, Rider, GoLand, CLion, and RubyMine, in addition to IntelliJ IDEA, PyCharm, and PhpStorm.
With first-class integration, you can browse Space projects and clone repositories, then start working on them directly. When your changes are ready, you can create a merge request and perform a code review from within the IDE.
Read this blog post to learn more about how to review code with Space.
Introducing a new way to customize Space to meet your team's needs!
Today we're releasing Space Marketplace Beta, where you can download applications for Space, create your own apps, and share them with other people.
You can get started by downloading apps created by JetBrains that allow you to:
Read this blog post to learn more about Space applications, find out how to create your own apps, and get an overview of the apps that are available.
You can now manage your Space dev environments for remote development directly within IntelliJ IDEA 2022.2 or the JetBrains Gateway UI.
When your IDE is connected to your Space organization, all of your existing dev environments are synchronized. You can create a new dev environment for a repository and branch, and start coding right away with JetBrains Client. You can hibernate a dev environment to reduce resource consumption or simply delete it when your work is finished.
Read this blog post to learn more about managing dev environments from IDEA 2022.2.
You can now customize the way your issue cards are displayed on issue boards. Select the attributes you want to see on each card, such as issue ID, due date, status, attachment preview, or other issue fields.
To customize the card preview, go to Your Project > Issue Boards > Settings > Cards. This feature is available in the Team plan and higher and requires board admin permissions to edit the view.
You now can add swimlanes to your issue boards to speed up your workflow and differentiate tasks. Use swimlanes to:
Open the Swimlanes tab in the board’s settings and set any issue field, including custom fields, as a swimlane label. You need board admin permissions to set up swimlanes.
Are you working on a fast-paced project on a growing team? You can now add an extra layer of protection to the main branch to ensure that a merge commit doesn't result in failed builds. With Safe Merge, you can run integration checks on the requested merge without actually merging potentially harmful changes into the main branch.
How does it work? Safe Merge creates a temporary merge commit combining the most recent main and feature branch revisions, runs predefined automation jobs or TeamCity checks, and lets you finalize the merge.
If you’d like to check your potential merge but don’t intend to finalize it just yet, there’s a new Dry Run option. Dry Run won't prompt you to complete the merge even if it passes all the checks.
How do you enable Safe Merge and Dry Run? Navigate to Your Project | Repositories | *your repository* | Settings | Protected Branches | Edit “main” branch. From there enable the Safe Merge option at the bottom, and then create a safe-merge.json configuration file. You will be automatically taken to the Quick Start Guide on how to set everything up.
Read this article to learn more about Safe Merge and Dry Run.
Do you want complete control over your data? We’re happy to announce the release of Space On-Premises Beta. You can now manage, maintain, and upgrade Space fully on your side.
Enroll in the Beta program and use the installation option that suits you best – Space On-Premises for Docker Compose for quick trial runs or Space On-Premises for Kubernetes for bigger installations that scale.
The Beta version is available for free and includes all the Organization plan features. You can use it for up to 1,000 users and 50 concurrent Automation workers.
Want to learn more? Read this blog post to learn more about the benefits of Space On-Premises, its installation options, and future pricing plans.
Want to give it a try? Follow these instructions to download and set up Space On-Premises.
We're introducing a batch of updates to improve your experience in Space Chats and help you communicate faster.
You can find all your mentions on a dedicated page by clicking on the
at the top of the left menu. You can quickly see the context you've been mentioned in, react
to messages right away, add them to your to-do list, create issues, and navigate to the
Working with many tabs can be troublesome, especially if you have a lot to do. With the new favicons, you can now distinguish between Space browser tabs more easily, as Chat, Issue, Code Review, Document, and Profile tabs all have different favicons. Review code, work on issues, chat, and edit documents at the same time without mixing up your tabs.
Looking for particular code snippets in Chats? Find them more easily with the improved search feature in Space, accessed by pressing Ctrl+Shift+F. It allows you to find snippets even if you don't remember all the parts of a class or a function name.
Want to keep a discussion amongst the participants? You can now make public channels private. To change your channel’s privacy level, click on the three dots in the top right-hand corner of the channel and select Make private. This setting is available to channel admins only.
Today we’ve got an important milestone in Space Automation development to share with you: We’re releasing support for deployments in Space.
Deployments let you track the delivery of source code changes to a deployment environment. Examples include delivering a web app to a production server, publishing a mobile app in a store, uploading a distribution to an FTP server, and so on.
Read this article to learn how deployments can be helpful to you and how to get started with them.
You can now choose between two line lengths in your chats – comfortable or full width. The comfortable reading setting always frames your main chat text regardless of whether you have a thread open or not. Full width lines, on the other hand, are bound only by the window size or the active thread.
Go to Chats | Settings | Advanced and pick your preferred mode under the Line length section.
Following the release of personal dashboard customization, you can now adjust your Project dashboard as well.
This dashboard provides quick access to the items most relevant to your Project – Description, Members, Favorite Repositories and Documents, Issues, and Code Reviews. Shuffle or disable any of the widgets by clicking the Customize dashboard button in the top right-hand corner of the project overview.
We're happy to introduce redesigned Code Reviews in Space. Our goal for this revamp was to make the interface simpler and the code review process easier.
You can now access an overview of your code review on a panel on the right-hand side of your screen. There you will find information about quality gates, conflicts, reviewers, dev environments, and linked issues.
The quality gates section has been completely reworked. You can now track the number of required approvals and their statuses without any extra clicks. This is especially useful when you have complex quality gate rules.
Commits and files are now located on the panel on the left-hand side of the screen. Also, the commit view now presents more information on the screen, so you don't have to hover over a title to see the full commit message.
You can now create code reviews and merge requests in just a few clicks! Press + on the left menu no matter where you are in Space and select what you want to create – Code Review or Merge Request.
Space will automatically suggest the repositories and branches that you've recently pushed changes to.
You can now create and export Matrix reports for issues in Space. This report allows you to display issues for two customizable attribute values, and view them as a matrix or a chart.
To create a report, go to Project | Issues, click on “Reports” in the top right-hand corner, and select "Matrix". By default, you will see how many issues are assigned to different users for each issue status.
You can customize your report by choosing issue attributes for the X and Y axes between Assignee, Created by, Status, and Tag.
Sort the data by clicking on the arrows next to the attributes. To access the list of respective issues, simply click on a number in the table.
Visualize your report as either a matrix or a chart by changing the report view.
You can now access all your favorite Space projects right from the JetBrains Toolbox App.
Read this blog post to learn more about the integration.
You can now log and track time spent working on issues in Space. This update allows you and your colleagues to keep track of time spent on tasks and report the results to a manager or a client with downloadable .csv files.
To log time spent on an issue, go to the issue and click on 'Spent time ➕'. Then, add Duration, Start day, and Description, @mention someone, or change the Assignee.
Adding time to sub-issues can be done in exactly the same way as issues. When logging time spent on a sub-issue, the overall issue time will be increased automatically.
To download a report in .csv format, go to the issue and click on 'Time tracking report' in the top right-hand corner.
To view and log time spent on issues, you need the appropriate permissions. You can grant them to your colleagues as a project administrator, or request them from your admin as a user. Time tracking functionality is available in the Team plan and above, but not in the Free plan.
Do your builds require workflows that are not possible with containers? Do they require specific hardware or access to internal network resources?
We're introducing Space Automation workers – a new way to run your Automation jobs on your own hardware or on virtual machines in the Space Cloud. Automation workers let you perform CI/CD workflows that are not possible with containers.
What is an Automation worker? It's a lightweight Java application that runs on Linux, Windows, or macOS. A worker connects to Automation via the Space HTTP API, gets jobs and source code from Space, runs the jobs, and reports the results back to Space.
Using Space self-hosted workers, you can run any build script on your own hardware on Linux, Windows, and macOS. Build full .NET Framework apps on Windows and run builds on specific hardware, for example to build iOS and macOS apps, run ML tasks on GPUs, and more.
Read this article to learn more about self-hosted workers and how to use them.
With Space Cloud workers, you can run build scripts on virtual machines hosted on the Space Cloud infrastructure. This means you can use them for CI/CD tasks that require full access to the system, which is not possible in Docker containers.
Check out this article to learn more about Space Cloud workers and how to use them.
You can now use Space dev environments to develop .NET projects with JetBrains Rider.
To launch Rider remotely, make sure you have the JetBrains Gateway app. From any Git repository, click on the Open in IDE button to start a dev environment. Pick the machine size, select Rider as your IDE, specify the path to your .sln file, and Create your dev environment.
Read this article to learn more about how to get started with Rider using dev environments.
Once pre-configured, Space dev environments allow you and your team to code remotely without having to prepare local machines. Using a devfile, you can now configure dev environments for your teammates, including such aspects as a docker image, environment variables, a default IDE, and CPU/memory resources.
What is a devfile?
Devfile is an open-source specification that uses YAML
formatting for configuring and running dev environments. To get started, create
devfile.yaml in the
.space folder of your project.
You can edit it by copy-pasting config examples from the snippets panel.
Read this article to learn more about how to configure your dev environment using devfiles.
You can now change the IDE version that you use for an already existing environment. To do so, go to the list of your Dev Environments using the personal navigation sidebar, select a dev environment, and click on the IDE version on the top. Your dev environment will be restarted using the new IDE version, with your uncommitted data saved.
A new type of Space Package repository is now available for automated storage and sharing of project-related files – File Repository.
Use command-line tools, like cURL and Powershell, to remotely manage the repository or handle files and folders from within the UI. Thanks to file content immutability enabled by default, you can ensure reproducibility for your CI/CD pipelines.
To create a File Repository, go to your Project | Packages, click on 'New repository', and select 'File Repository'. Read the documentation for more information.
Looking for ways to master time management? With this update, you can now manage your Space work schedule and personal plans from your favorite calendar app.
We've implemented CalDAV support in Space, allowing you to view and edit your Space calendar from calendars and mail applications that support CalDAV, such as Mac and iPhone Calendars, Thunderbird, and others.
What is CalDAV? CalDAV is a protocol that allows you to display and manage your calendar on any device using any compatible application.
Read these guidelines to find out how to view and edit your Space calendar from your other calendars, and to learn about supported clients.
When reviewing code changes in the IDE, you can now choose when to post a code review comment:
To learn more about Space code reviews in IntelliJ IDEA check out this blog post.
We have improved the code review user interface and show applicable keyboard shortcuts. When posting a code review comment, you can use Enter to add a new line. Ctrl+Enter will save or post the comment.
You can now rearrange the widgets on your personal dashboard or hide those you don’t need. The default dashboard provides an overview of useful day-to-day information, with widgets like the Calendar, Favorite Projects, Code Reviews, Followed Teams, and Recent Blog Posts.
To configure your personal dashboard, click on the 'Customize dashboard' button in the top right corner of your profile. You can adjust the widgets any way you like, and if you ever want to revert them back to the default view, you can simply click 'Reset to default'.
With this update of Space Documents, managing files has never been easier.
Learn the details of the new Documents and discover more about the update in this blog post.
When reviewing a merge request from your teammate, you can now make quick edits to the code and post them as suggestions instead of just leaving comments.
To suggest edits, select a line or a fragment of code, click 'Suggest changes', and edit it. Comment your edits as well if you'd like to explain the reasoning behind them. When your teammate sees your edits, they can accept and commit them right away with just a couple clicks.
Space Packages now lets you create your own Composer repositories. Use them to store and share packages in your PHP projects. To create a Composer repository, go to your Project | Packages, click on 'New repository', and select 'Composer repository'.
Read this article to learn more about how to create a Composer repository and publish Composer packages.
We're introducing mirroring for Space Packages! With this update, you can now:
Read this article to learn how to use mirror remote repositories step by step.
Space Automation now supports HashiCorp Vault storage, allowing you to use secrets stored in a Vault server in your Automation jobs. Simply add a connection to the Vault server, create a parameter, and use it as if it were an ordinary parameter stored in Space.
Read this article to learn more about the update, and discover how to use Vault secrets in Space Automation.
Thanks to the new application authorization options, you can now allow your Space applications to access private channels in Space chats. We’ve also added an option to specify what your application can do within a particular private or public channel. For example, you can allow an application to view and post messages, update channel info, add new members, and more. This level of granularity in the permissions helps you keep your communication private by ensuring that the application can only access the information you allow it to.
To set chat channel permissions, head over to your application’s Authorization page | In-context Authorization, select the chat channel where you want to authorize your application, and choose the permissions you want to grant to it. You can also authorize the application from the chat channel by going to Channel info | Applications.
Please note that only channel administrators can grant chat channel permissions. Other users can request permissions from the channel administrators. Currently, applications don’t need authorization to access public chat channels, but we will introduce this requirement in one of the upcoming Space updates.
Take a look at this article to learn how to grant permissions to your application.
We’re introducing a few updates that will make working with issues easier and more transparent.
You can now add sub-items to Space issues. They allow you to break complex issues down into smaller tasks, or list requirements, DoDs, and other relevant information. Just like checklists, sub-items can have a nested structure, and you can check them off upon completion.
You’ll find the new Sub-items section under the issue description. To add a sub-item, click Add item and start typing. You can then leave the sub-item as a simple line of text, which can be formatted with Markdown, or you can convert it into an issue and assign it to any team member right away. You can also add an existing issue as a sub-item by clicking on the ✳ icon.
Check out this article to learn more about how to use sub-items in issues.
To make sure that you don't miss anything important, we’ve made it easier to track any mentions and discussions related to your tasks in Space.
Whenever somebody mentions an issue by its ID or link in a Space chat channel, code review comment, or another issue, the mention is automatically reflected in the issue’s history. This way, you can be sure no important discussions go missing and you always have the full context.
Here's an example. A chat message that contains an issue ID is copied to the mentioned issue:
The following rules ensure that private messages don't end up being made public. Space will NOT post mentions originating from:
Code review comments from a public project will be posted, but details will be only visible to project members who have access to the project repository. Read this article to learn how to comment on issues.
You can now search for issues even faster – use the new Board filter on a project’s issues list to filter by board and sprint. Head to this article to learn how to use issue boards.
Want to code on your favorite JetBrains IDE remotely? Aside from IntelliJ IDEA and Fleet, Space dev environments now support more IntelliJ-based IDEs. You can launch GoLand, PhpStorm, PyCharm, RubyMine, WebStorm, and CLion (starting with the 2021.3 version) remotely using Space dev environments via JetBrains Gateway.
Read this blog post to see Space dev environments in action and learn how to launch your IDE remotely.
We’ve changed the underlying engine that runs Automation jobs, allowing you to enjoy faster build times with Space Automation. Start-up times for jobs have been dramatically reduced, and jobs consisting of multiple steps have received a significant boost, as well.
Let's suppose you have to run a script that contains two jobs – one job with only one 'hello-world' container step inside, and another one with three such steps. With the new engine, the one-step job runs up to 10 times as fast, and the three-step job runs up to 5 times as fast.
Space Automation now uses the new engine as the default option, so you don't have to adjust any settings for your build times to be faster. If long build times were the main issue preventing you from using Space Automation, now is a great time to give it another try.
We discovered that the new backend fixed a bug affecting container resource allocation. More specifically, the old backend ignored the CPU and RAM container configuration and gave the container access to all the resources available on the host where it was started.
While the new backend fixes this bug, you might experience a slowdown of your jobs with low CPU or memory limits configured, since they will now get the correct amount of resources.
Space now supports the Docker daemon inside the dev environment container. To run a container in a dev environment, just open the terminal in your IDE and run Docker or Docker Compose commands the same as you would on your local machine.
Check out this article to learn how to develop in a dev environment.