The YouTrack Blog

YouTrack 2020.5 is now available! This is a specific update devoted to the discontinuation of legacy workflows and enhancing the overall workflows experience. If your team relies on YouTrack workflows written in 2018 or earlier, please show this post to your system administrators and project adminis…

Some time ago we wrote that support for legacy workflows would cease in YouTrack 2019.1. By "legacy" workflows we mean those written in the old Workflow Editor, which was an external application discontinued in version 2018.3. We see that some of our customers are still using these legacy workflow…

Over the last month, we have investigated various aspects of the issue lifecycle. We described how to set up granular read and write access for existing issues, how to streamline issue creation, and even how to generate issues automatically. If you missed any of our previous installments, you can fi…

Last week, we shared a few tips for streamlining issue reporting. The goal was to improve the simplicity and accuracy of issue creation for your team and for your customers. In this article, we take it one step further. Imagine what happens when you need to create a standard set of issues on a regu…

In previous installments, we discussed how to restrict issue visibility and prevent unwanted updates. We still haven’t covered what is possibly the most important aspect of the issue life cycle — its birth. In this article, we describe how you, your team, and your customers can create issues that co…

The previous article in our Make it Workflow series showed you how to set up complex visibility restrictions for issues. We limited the ability to read issues to specific groups of people and restricted read access for different sets of users for issues in a single project. In this post, we descr…

With this article, we begin a series of blog posts that demonstrate how to support specific processes in YouTrack with the help of workflows. This post is devoted to visibility restrictions. Specifically, we’ll show you how to restrict visibility so that each issue can be read by a very limited set …