Features

Code review like no other development practice relies on humans being efficient. And for most of us to achieve that, it's important to have our tasks well organized and our time well planned. Upsource takes care of a lot of things for you without any need to configure anything. For example, if you have a branch review, it'll automatically add new revisions to it. It'll promptly notify you about things that require your attention. It keeps track of which changes you have seen, and which you haven't so that you only need to review those you haven't seen. With some configuration required

If you're using JIRA workflows and have code review as a part of it, you'll be pleased to find out that Upsource 2017.2 can apply issue transitions automatically. Let's say you have a JIRA workflow set up that looks something like this. We won't go into detail on how to configure a JIRA workflow - please refer to JIRA documentation. Now, if we look at the text version of it, we'll see which transitions we should let Upsource know about: We, of course, assume that you already have JIRA integration enabled and configured in Upsource. If not, check out this post. Now, in Upso

In the latest Upsource release we have further extended the reach of JavaScript code intelligence by introducing support for npm and yarn package managers. Upsource will look into your package.json file(s) and install the required dependencies so that you can get more out of Go to declaration and Find usages actions. The downloaded dependencies are intelligently cached. Here's how you can enable JavaScript support in your project: Make sure Node.js, npm and/or Yarn are installed on the Upsource server. Remember: it's better to have package-lock.json (for npm) and yarn.lock (

The latest Upsource release brings Python code insight functionality to help developers understand new changes in a familiar manner and be more efficient when reviewing them. The code insight features in Upsource include server-side static code analysis and code-aware navigation. These features allow you to understand code better when browsing through it and perform code reviews more efficiently. Let's take a look at them. Navigation It might seem like a trivial thing, but the ability to navigate through the code is something we simply take for granted when using an IDE. Yet these feature

Let's say you've just fixed a typo in a branch that is undergoing a code review or committed some other minor change. Now, you've become one of the authors in this branch review, even though you probably don't want to follow the review progress. Unlike watchers and reviewers, authors cannot simply remove themselves from a code review, but in Upsource 2017.2 it is possible to mute it. If you mute yourself in a code review like that, you will stop receiving updates in your news feed as well as email and browser notifications. Your userpic will reflect that you've muted a review, h

As you know, Upsource has IntelliJ IDEA at its core which brings IDE-level code insight right into your browser. This helps teams that code in Java, PHP, Python, Kotlin, and JavaScript perform code review in a more efficient manner. This, however, doesn't mean that projects written in other languages cannot use Upsource as a code review tool. In fact, all of the smart code review functionality such as progress tracking, workflow automation, and intelligent suggestion of reviewers and revisions is language-independent. The only teams that cannot use Upsource are the ones using exotic versio

In the recent release, Upsource 3.5, we have significantly improved PHP code intelligence features announced in the previous release. We've added support for composer dependency manager and made it possible to explicitly specify external dependencies. In Upsource 3.5 you can now set the PHP language level, and fully enjoy smart code review features. In the following video Gary Hockin, a Developer Advocate for PhpStorm at JetBrains, explores Upsource and its PHP code insight. Check it out! https://youtu.be/KaRhE3I9YCs

We are delighted to announce that with the latest release Upsource has reached an entirely new level of scalability. In the last few months, we have revised and reworked Upsource's architecture. As a result of this work, we are now able to provide a distributed cluster installation that is highly scalable, fault-tolerant and available 24/7. This new multi-node cluster installation allows you to scale and distribute Upsource services to different nodes and machines providing more control and resources demanded by large projects and thousands of users. The setup procedure is not as sim

Code review workflows are as diverse as teams that use them. Some teams are flexible and review only certain commits as they see fit, others have more formal criteria of what should be reviewed, by whom, and how the outcome of the code review should affect the development process. For example, there are teams that want to make sure all commits are reviewed by at least three team members. Some teams may have dedicated team members whose approval is crucial – changes won't get merged into main branch until approved by all. Upsource lets you make your code reviews more efficient by allowing y

In the previous post we have talked about the Analytics reports representing contribution and code review activity. Today we’d like to cover the two remaining reports, Project Treemap and File History Chart. They both focus more on exploring the project structure rather than its history. Project Treemap As a developer, once you start getting familiar with a repository that you have never seen before, it usually takes a while to build the understanding of the codebase structure: where most of code is located, what are the key elements of the codebase, which parts of it are changed more fr

At JetBrains, we make a lot of effort to help reduce the amount of boilerplate work that our users have to deal with. Even though code review is a process requiring human's attention, there's still room for automation. A brand new feature in the latest major release is aimed to take responsibility for routine tasks, which a code review process involves, and it’s called “Custom Workflows”. Basically, a custom workflow is a list of triggers related to a specific action. Each trigger consists of criteria and properties. When the criteria are met, the action with the corresponding properties is