YouTrack Demo Overview and Features

Hello, hello, good morning. It's morning in the sunny Amsterdam today. I'm happy to see you all joining our event. I'm Yelena, the Utrecht product marketing lead, and I'm happy to introduce Anastasia, our Utrecht technical support lead. And today in our session, we will show you a live demo of Utrecht. And as you probably know already, Utrecht is an agile and flexible project management tool. There you can also track your tasks. And it is currently trusted by 85,000 teams in more than 200 countries. and they all are using YouTrack to plan, track and manage their projects. Half of our customers are from the IT, software and gaming development world, and the other half is from many different industries and they are building everything from FinTech solutions to creative video ads with YouTrack today. So we are here now to show you how they manage their team projects and how they manage their knowledge base daily. And you know each team has their own ways to work on their projects. Your track is used by various teams in software development, quality assurance, data insights, marketing, design, web development, product management, and even in human resources or by administrative teams and management board members and even by chief executive officers. So every team needs a tool to adjust to their business process and hopefully not vice versa. That's why we actually designed Utrecht for enterprise companies, but it's also loved by small teams that get Utrecht for free. And the free version is fully functional and it is available for teams up to 10 members and you're free to choose cloud or server. And for today's demo, we've chosen the basic scenario and actually some non-technical roles in the team, so you could see what U-Track consists of and how you could adjust it in your case. We hope to get to the bottom line idea of how project and task management works in U-Track, how you can build in your knowledge base, what can you do with interactive Gantt charts, how to create agile boards, and how to use time tracking and reporting. reports and multiple dashboards in your business flow. And also, we'll try to give you a glimpse of how the HL process management is supposed to work in Utrecht, if a workflow constructor and JavaScript workflows. So we hope that you'll get a helicopter view of projects and task management in Utrecht. And be sure, if you at some point decide to try Utrecht, it's... easily integrates into your environment. Hopefully you see here on screen some of your favorite products and solutions and we'll also show you today how some of these integrations work. But better to see something once, so let's get started with the demo. Anastasia, yeah the floor is yours. Yeah, thank you, Lena. Hi all, it's Anastasia here and let's do the demo. So today we'll show you a demo of U-track. project management tool and we'll see how various teams across the world both technical and non-technical use YouTrack in their daily processes. So to demonstrate that we try to imagine how your working day may look like if for example you need to launch a website for an upcoming conference. So today we'll imagine that I'm a member of the web development team and together with my teammates from the design team, Lena will play a role the design team today, and from the marketing team we'll try to launch this website. Okay, so let's go, let's see how various teams use YouTrack to organize collaborative work of multiple teams even without personal meetings and how they use it to achieve their results in time. So what you see here What you see here is a page of a list of projects. In U-Track you can create projects for almost any organization that you find suitable. You can create a project for a team, or for a department, or even for the whole company. Or you can, for example, organize your projects if you have some separate initiatives. organizing a conference in our company uh we we create projects for uh for teams so that each separate team has their own project so what you see here is a project page and well it's team and also their backlog also on right sidebar you can see a list of project settings and project administrators can serve through the settings to configure the project like integration functions, automation, set of fields, level of access for the team. We'll check what the project can contain later. But now what I want to say is that each project has two main parts. The first one is the knowledge base. We truly believe that documentation is everything. That is why we implemented the knowledge base so that you can store your data next to your issues. Well, the knowledge base is basically a set of articles, you can see them here. So you see a list of projects and each project has its own hierarchy of articles. An article may represent maybe just a plain text or a link or a table or an embedded video. You can also use Google documents and checklists, whatever you find suitable to express your idea. How you can use the knowledge base? So the first scenario is organizing a public space for your external users. For example, you can publish your external announcements here, or you can organize an FAQ section so that your external users can get replies to their questions even without pinging your support team. The second scenario is organizing an internal space for your team or for your company so that you can store there your vacation policies or an internal roadmap or store meeting minutes and this is exactly what we do so when we are about to um to organize something big like i don't know a conference we house the call and we invite their all all involved parties all teams and we discuss the main points of what we are going to do. So we discuss the deadline, the scope, what features do we need and what teams do we need and we write down everything that we discussed to the article so that even those who missed the call they can just open this article and stay up to date. Of course it's possible to start a discussion in comments and you can easily mention your teammates to let them know your opinion and they will be notified about new comments. Or it is possible just to start an article, to add it to favorites and to receive notifications about any new update. If we think that this initiative is not public yet, so we don't want other teams to know about it, we can just restrict its visibility to... any team we want to a group of users and no one will know about it until it's time yeah and of course it's easy to get lost in this infinite list of articles that is why there is a search that allows you to to easily find what you need right now using a keyword yeah so when we have everything written down it's now time to proceed to our tasks and we are now moving to the Second important part of what each project has issues. An issue may represent some minor task like fixing a typo on a website or something really big like preparing a conference. You can also manage business trips or salaries or hiring process or approval process using issues. And we'll now see how it can be done. Yeah, so issue always belongs to your project. You see there are issues from. multiple projects here so it's kind of our backlog and issue always inherits its project settings its integrations automations uh a set of fields and you see there are assignees my teammates who already work on these issues and i see that lena is um is assigned to this design issue so let's ask lena to show us how her working day is going and um and how she solves her tasks. Lena, the floor is yours. Yeah, thank you. I'll be happy to show you my side of things. You now see my screen and my U-track. So imagine, again, I'm a design team lead and our team is responsible now for providing the web development team with everything they need to launch the website. But first things first, I would like to change the theme here to the darker one. Yeah, now I like it better. Actually, I can start my day. Usually, I do it by checking the notification center and seeing if there is anything new for myself, if there are some new tasks available, and checking what I actually need to do with them. So, as you can see, I can check out the task right away and... easily proceed to the task right from the notification center. But for example, some of other teams not only interact with internal tasks, but they also have a mailbox integration set up, and they actually have the incoming emails fetched as issues or tasks to their dedicated project. So here is my urgent task for today. Let me check how it works. Yeah, so I can go to the tasks right from the notification center. And yeah, what I see here is here is the details, the design department team actually would like to know about the tasks. So we set it up so we see the priority and you see it's critical now. You see there are types of the materials we need and yeah, and for example, its banners and if you have animations here you see that we would like to specify the video format for the animations and so on. And this is how the design task look like and let me first of all set the state here to in progress so everyone is notified that I'm working on the tasks this is critical and no one is pinning me with some questions for some updates while I'm I'm busy with the task. But for example, if I switch to one of my recent tasks and check how the task in the HR project looks like, you see that my colleagues there, they set it up to look completely differently. So they need an employee ID, for example, there, and they've got a type of the task, for example, annual review. And if we set it to the annual review, they are they can have some specific fields need to be filled in. And if I edit the task, so they, for example, require the annual goals and the annual review results to be posted in the task, and the layout of the task looks completely differently. So this is the way how they like to do it. But let me get back to the banners. I'm working on. Since the task is critical, let's say I'm already done with doing the job, so I can pin Anastasia here and say, like, please have a look at this. And yeah, I can, for sure, I can add the button here to the, yeah, and it's positive. Let's say I'm a design team and we are working on the team member and we are working on the banners for the website. So I would like the team to preview how the banners will look like on the website so I can post the Figma link right here. I've got some Figma link in my backlog So I am embedding the link and you see that I add the comment everyone who is logged into Figma can not only see the banner itself, but also can have a look and interact with it from the U-track interface and see how it works on the actual page draft. And can do something right from the U-track interface without even leaving the U-track. So yeah, with that all said, let me say that the stage for the task is waiting for review. and I will be waiting actually for nice, for Anastasia to have a look at what I've done. And meanwhile, I can. work with some of my other tasks. You see, here is my list. I can set it up to look like more more like a simple to-do list with no details or I can add the fields, the details that I would like to see. For example, I need to know the SIE, I need to know the due date of the tasks and I would like to the due date to be the first thing I see about the task and everything. What can I do else? I can, for example, sort, of course, by some of the details here, or I can filter the tasks, so I can see the design department tasks only. Also, I can use some more powerful filters. For example, I can do a search for unresolved tasks or some more you see there are there are a list of unresolved tasks or i can do some more complicated for example relative date search so i can choose to filter the tasks created for example last month let's see so let me uh and you see your track is actually helping me to uh to perform the this search the way i need it with some with some tips here. So yeah, this way I'm filtering the tasks that were created last month. And it's a relative search. So that every time if I save it, for example, let's say I name it last month and save the search. And each time when I have it, yeah, I have it here in my saved searches. I can share it with my team or use it in some reports later. And each time then I open this search results, I will see the relative search. So it's actually gonna be the last month, regardless of what date is it today. Yeah, this is how my backlog looks like for the team. You can see there are no tasks assigned for me. So let me check the notification center once again and see if... if there are any news for me and there are some news actually you see that Anastasia not only approved but also she likes the banner so what I can do I can do the change of state of the task so now it's fixed and why I'm smiling because it was the last my last task for the for the day and for the week because actually I'm going on vacation And let me use this example to see how YouTube workflows can help me with this. Since I'm a team lead, I wouldn't be leaving the work without actually making sure that someone is taking care of the tasks ahead. So I would like to set some workflow. to the rule that will check the tasks during my absence and that actually will reassign the tasks to one of my teammates. So let me name the role learning location, let me choose the design department project and in my visual workflow constructor I can actually filter some conditions and actions for the role. So I'm going to to check the issues that were created for during my absence and my vacation starts starting today and yeah and I will be there before yeah it's starting today and I will be yeah and I will be there until the end of November yeah here's the the period and also I would like to check if these created tasks... I would like to check the field. So if those created tasks are assigned to me, so I'm checking for the assign field and if it's set to myself... Then I'm going to change it and then I'm going to update it. I'm going to use the SAE field to be set again to one of my colleagues. And yeah, I agree with Carrie that she will be taking care of that. And I wouldn't be... I wouldn't like to do it in silence, so I would like the comment to be... To be added, so I choose also a comment. I will say to everyone that I am resigning the task during my absence. And I would like everyone to see that it's me who is posting this comment. So, yeah, I'm selecting again myself. So, yeah. This way I'm all set. You see the conditions, directions. I'm saving the rule and I'm good to go off to my location. For sure, I wouldn't be left without any information. I can reuse integration with Slack and Telegram for Utrecht to get some notifications on the updates in the projects and tasks I follow. And also, for sure, I've got a mobile app. And in this mobile app, I'll see a lot of states and notifications and the jailboards for the tasks I'm working on. But hopefully, I wouldn't be seeing any surprises there. So I hope you'll manage just perfectly without me. Nesta, how do you think? Is it possible? Yeah, I'm sure it is. Because, well... we know that the design team is pretty strong so that i think i'm sure they will manage all critical tasks while you are away uh okay so um of course of course let's check that this workflow works uh fortunately or unfortunately i'm having a critical design tasks task that um that should be done until tomorrow and let's see if lena Liana, could you please, please, please fix it today while you're still in the office? No, you can't. Okay, so Liana, you see that this issue was automatically reassigned to Carrie, and there was a comment added automatically on behalf of Liana that she's already out of the office, so she will not be able to take care of this issue. But you see that it was not left unattended, it was reassigned, so our teammate will take care of it. care of this issue and we will not miss anything important. Of course there was like the simplest scenario where you can use this workflows. Workflows is a very powerful feature of Vue track and you can use it to react on some events like updating a field and the workflow can update fields for you or add comments or check commits or pull requests, it can modify description. it can create subtasks, new issues and also it can react on schedule, run on schedule. For example, it can create reporting issues for you each Monday. Let me show you one more example of how it can work. So we in our company, we have a release process and each time we are about to release something, we need to create a meta issue about this release. So the release is a process, so you need to follow it to do everything properly. So in our company we have a specific process to follow and we decided to automate it because release is something you do quite often and it's a set of repetitive tasks, so that's a perfect case to be automated. So each time when I switch... um switch to the release type a workflow automatically substitutes this description for me so that I don't forget to specify the release name the version number and description let it be you track release yep and the version also the workflow makes sure that I'm not allowed to create a release issue without setting a due date yeah so let it be like one week from here that's a tight planning but whatever yeah and now i'm all set and i can create this release issue and you see um that in our company the release breaks down into a set of steps and the workflow automatically creates this set of steps for me so this meta issue is now a sequence of these um of these steps so we need to prepare a blog site, to localize the materials, to enable new features, to publish them, etc. And now I don't need to create these steps manually because it's very time consuming and I can miss something important. It was all created for me, now all I have to do is to follow these steps. What we use workflows for is to automate some routing processes for us so that we don't forget about them, so that we don't miss anything important and so that we can spend our time doing really important things. And more about workflows, how you can build them. Learn the show does. the workflow constructor where you can build your workflows by dragging and dropping blocks so you don't need any programming skills for that and if you need more advanced and more advanced workflows for example if you need to interact with third-party tools if you want to send http requests or something else you can switch to the javascript editor and create even more powerful automations there Okay, so yeah, that's it with the workflows. And yeah, we saw the list of issues we are about to do to launch our website. But of course, it's not enough just to have this set of issues and the deadline in front of you to finish it in time. There is one more very important stage that you need to follow. And I'm talking about planning here. To organize the planning stage correctly we use the Gantt chart. Okay, so this is the Gantt chart in front of you and the Gantt chart considers dependencies between issues and their start dates and their durations and builds the planning activity for you. The Gantt chart predicts the end date of your process so you can see if you are in time or if you need to descope something or schedule something and it's pretty easy to add new issues to this chart you see that yeah you can create a brand new issue or you can add something from existing ones for example if we want to see all critical tasks that we have yeah i can add them one by one or i can add all 17 issues to the chart yeah you can see here you can see issues that take parts in the chart now you see there are issues from multiple projects so you are not limited to use only one project and you can um you can add the whole activity that you are now planning to this chart to see the whole picture in front of your eyes um the chart is interactive meaning that you can drag and drop these issues you can for example update their duration or alter their start date you see they are updated here immediately Yeah, and one more important point is that the chart immediately highlights if any area of your project requires immediate attention. So imagine you've planned all the activity and now you're working on it. But let's see, we estimated this issue to take one day and we've already spent five hours doing it. But let's imagine I spent one more day. doing this issue so it's like more than day and a half in totals it's more than we estimated and the chart immediately highlights this issue in red meaning something went wrong here and probably we need to pay attention you see that the parent issue is still blue because we still have chance to finish it in time if we are faster with these two subtasks okay uh so when we planned the whole activity it's now time to do the issues themselves and we find it very important to to still keep all issues that are in progress now in front of our eyes so that we don't need to go to each team separately and ping them and ask them what's the progress so we use the agile board page to to keep all issues in one place on one page you can use the agile board even if you don't follow any agile process you can use it just as a table so you can see that's basically a table and um uh yeah and uh it has its columns and rows and of course you can define these columns and rows and it can be done like really easily let's take a look First of all, let me tell you how I think it's obvious, but nevertheless, now you see that each cell contains issues that are in a particular state and belong to a particular assignee. Yeah, so that's pretty easy to see the workload of each assignee now and to understand the state of each issue by just looking at the board. Now let's try to modify it. So you see, these are my states that are currently used for defining the table columns. And of course, they are not hardcoded at all. So you can customize it up to your needs. You see, there is a drop down where you can add. new state and if you yeah it immediately appears here but if you feel that the new state doesn't deserve a separate column you can easily merge it with for example open so you see now we have opening new issues combining this column and this column already combines three states and of course we can easily modify that yep Right, now we are going to swim lanes, rows or swim lanes, how we call them. So right now they are defined by assignees, but there is a plan of choice for me here. For example, if I want to define rows by priorities, you see, now I have all critical issues collected on the top of the board, right? Or I can, for example, choose project. to define uh to define swimlands so now i have uh issues divided by their group by their projects so this is what our marketing department have related to to launching our website and this is the design department workload well they have no the web development is a champion right yeah and also it is possible to use issues themselves to define to define swim lanes. So this is how you can build your issues hierarchy there. So if you have epics or user stories, you can make them swim lanes so that each user story will have their own swim lane and cards, their subtasks will be well cards. But let's get back to our configuration. So we have assainese yeah yeah we have assainese and states and let's see this is lena's issue that she just fixed in front of our eyes and i'm working on my development issue here uh you see that it's in progress so that anyone who opens it knows what what is going on there and besides besides reflecting states um and descriptions in issue we also prefer to keep all development stages of the issues lifecycle in on the issue page. I'm talking about VCS changes now. So let me show you how it works. So imagine I'm working on some code, right? And when it is read, oh no, that's not commit yet. I will tell you more about the plugin. So we have a dedicated IDE plugin and Thanks to this plugin, you can see notifications from your U-track right in your IDE, and you can update your issues right from your IDE without leaving it. So you don't need to switch between two tools, and you can do all the stuff related to issues right in your IDE. So when you are done with your code changes and you are ready to commit, all you have to do is to mention the... yeah you have all you have to do is to mention the issue id in the commit message and push your changes yep push it push it okay now it's pushing yeah it's done and uh we'll now see how it looks in you should be updated yeah you are so you see your track automatically fetched they can meet based on the issue ID that was mentioned in the commit message. And now anyone who opens this issue page, they will see this commit. They know that it's a work in progress. They will probably know what is going on judging by the comments. But if they need any more details, they can easily navigate to the code changes to the version control system itself. We use space for that. And they can see the changes or view them, whatever they need. One more important part here is time tracking. So first of all, the IDE plugin allows you to track time automatically. You see, I have the timer that is that is in the process now and I can post time right to my YouTrack without leaving IDE. Thanks to that I don't need to remember how much time I spent developing my issue and I will not forget to post it to the tracker. But I will show you how it works manually. We also have a dedicated button here. So you see, let's imagine I spend three hours doing it was development and of course these work types they are not um hard-coded at all so you can add your own or you can modify the existing ones and you can also add a set of additional fields if for example you need to tell billable work from non-billable or if you want your teammates to specify your contractors to specify the currency or the price of work i don't know So let's imagine I was in Los Angeles and at spend time. Yeah, it is added here and you see that issues, overall issues spend time is reflected here in the issue. And it will calculate the overall amount of all work time records that I've added. When I'm done, I can just easily move the issue to the Fix It column, and now everyone will see that it is done and probably can be tested. Speaking about time tracking, of course, it's not very convenient to surf through each issue to see how much time I spent, especially if I'm a team manager and I need to collect the workload of my team. I cannot imagine I go through each issue. issue of the project to see the workload of my teammates. So this is what the timesheet page is for. First of all, you can see a personal workload here. So you see this is my calendar where all my workload is collected. I can add new records right from here. This is a list of issues I can select from. And also, I can edit existing. existing entities here, entries here. Yeah, also I can check the calendars of my teammates if I want and if I want to see a collective workload of the team I can switch to a work group tab and build a timesheet report that contains time entries from teammates I'm interested in. So yeah, you see this is a collective workload. And I can use this report for billing purposes or just to collect time statistics. And speaking about reports, we also use a set of U-Tracks default reports. There is a bunch of them. Let me show you some examples. So, for example, there are issue distribution reports. So you can, for example, check how many issues each assignee has. or you can see issues divided by their priorities. You can also build different tables or matrices. Of course, you can track your progress using the burndown chart or various flows. And you can also track various metrics like manage your SLA, service level agreements. or to check how much time does it take in your team to fix an issue in average or how many re-opened issues you have. Of course, there is also a classic time report that allows you to compare the spend time, the estimated time and the actual time. So you can choose the reports you are interested in and just use it in your processes. And of course, you may wonder if there is a page to combine all these metrics on one page. And yes, there is. There is a dashboard page for that. A dashboard page consists of widgets, and each widget may represent a report, an issue list, some calendar, team activity. And depending on the purpose of your dashboard, you can pick different widgets. So how you can use dashboard? For example, you can create a helicopter view for the executive members of the team. So in this case, they will probably need a calendar with upcoming deadlines and probably a chart that shows how many overdue issues you have and a backlog of your high priority tasks. And probably they will need to see the team activity. Oh, I'm so active. yeah activity of the team and yeah maybe some workload too the second scenario you can use is organize a guest dashboard so that your external users land on this page when they open your utrap and they can check your team or your public roadmap or your backlog or some announcements And yeah, in this case, you can use also initial list widget and some notes widget. And one more scenario is to create a personal dashboard. And in this case, your teammates, they can build their personal space and they can keep their personal notes or their personal activity or backlogs. And also they can look forward to their vacation. here. Yeah, so you see, we are pretty sure that everyone can organize their personal space in U-Track to have their personal board with their current work or their personal dashboards to see an overall state. And of course, each team can have their own personal space to track the activities, to collaborate and to... to deliver results together and what is more important we truly believe that you don't need to adjust your team process to uh to so that it fits you track because you track fits any process it can be customized customized uh in almost any way um yeah so yeah we hope that each team can find can benefit from from using utrac in their daily processes That was pretty it from my side and we went through almost all essential features of Vue Track. Of course that's not it and you can find much much much more if you dive deeper. Yeah and one more one more thing I wanted to say is that when we finish launching this website and I'm sure we will, we'll have external users who have their questions and feature requests and we need to handle them somehow so to address that we at JetBrains in Utrecht team we are actively working on extending our help desk functionality and yeah Lena will now show us a secret preview of what we currently have Lena up to you I'll be happy to thank you nice yeah yeah you Yeah, I will share a couple of more moments here and while we still have time to look for your questions and we hopefully will take them online right after these couple of points. So in the end we are currently focused on expanding the support for the helpdesk scenario in Utrecht and then the very dedicated type of helpdesk project. You are going to be able to have almost unlimited reporters and also have support agents in such projects. And we are thinking of paid per user price for the support agents only. And they are going to be customizable, embeddable form so that you can build it into your website or internal portal, for example, and get the support tickets directly to you, Tarek. And also we'll streamline the interface for the support agents to work on these tickets. For example, use templates and some internal comments that are visible only to team members or publish answers to customers for visible to external customers. And plus Helpdesk will come with editable service level agreements schemes to manage your tickets work for us. And then you will be able to easily set up some escalation rules and some business hours and other other workflows that are helpful for the working with external or internal tickets. It's all coming in the beginning of next year, 2023, and as you can see we are intensively developing new track and planning to add a little bit more. In the future, we are also working on the apps and plugins to be available in Utrecht, to go deeper into the resource planning and management functionality. And this is the plans for the upcoming year 2023. And also, of course, we are going to polish and deep dive into the better experience with what we already have in Utrecht. And today we've shown you U-Track in English interface, but we've got several languages available for the settings to be set as a main language for the whole U-Track, or also available on a per-user basis, so if you have a team that works globally and works in multiple languages, each user can set up one of the languages for their own to see the interface. in the convenient way. What else I would like to mention? We usually ask our customers, why did you choose U-Track? And one of the popular answers, of course, more than half of the respondents are usually saying pricing. And U-Track is available both in cloud and server versions. For the server version, it's also starts with a free plan for 10 users and you can have a granular user packs starting with 15, 25, 50, 100 and so on users. And for the cloud it's a price per user model so if you at some point need more than 10 users it starts with a starting price. It starts with a price of $4.40 per user and the price decreases with the growing of the number of users in your team. One more answer that we usually get is that it was the functionality. So it's either the team or one of the leaders or the project manager in the team decides that the functionality suits the most. And this is the interesting part of it. of how we try to develop it, right? Because we're thinking of enterprise teams with multiple functions in the teams, but it also fits for small teams as well. And yeah, this is one of the parts of the answer here. It's because of the free version for small teams, the free version is fully functional. We have no limitations to it. almost there and it's free for as long as your team is not bigger than 10 members. If you ask about some easy ways to start a new track and to see in action what we have shown you today, we recommend usually to start with the cloud version. You can get it up and running in two minutes. and use it free forever, like I said, for 10 users. And there are also import functionality for you to migrate tasks from some of the popular trackers. Then if at some point you would like to test the system with the extended team, there are trial versions for you to test it for two weeks in cloud for free. for 100 users and for two months in on server for several thousand of users. This is also going to be a great point for you to create some custom workflows to see if it works for your business processes. And then if at some point you decide to migrate to a paid version or to add some users into your growing team, then all the data from the trial or from your free training free your track, it will be easily and smoothly migrated to the paid subscription. And here is the thing you might... What I want to know is that the 25% competitive discounts for migrating from any of the competitors to competitive tools is also there for you. So please reach out to us to get it. And for some help along the way, you've got a list of partners, technically certified solution engineers in several companies in various regions in the globe. And also you direct sales engineer in our... brilliant support team are available to help you with a lot of questions you might have along the way. Yeah, that's it for the part that we prepared for you today. Thank you for watching. You can see the contacts on the screen, so please feel free to reach out to us if you think of any questions after the webinar. And now we can start with some of them that we already have in chart. So, thank you for the feedback. Thank you for sharing how you love GitRec and you migrated from another solution. And now to the first question. I can start and then moderate if you want me to. The first question is, when can we get inline comments in the Knowledge Base? Yeah, this is the popular thing. We've got a... popular uh quite popular feature request you know public uh uh uh tracker on utracjetbrains.com if you haven't heard of that uh we uh use the uh the opportunity to uh to to get feedback from from you from our uh customers in on utracjetbrains.com you can buy pretty much projects for every of pretty much for every of the JetBrains products there and also we of course we follow all the all the requests for for uTorque there are some roles for these and many other updates to knowledge base it's now planned we are planning for the next year for the update for the whole experience for knowledge base not only regarding the e-line comments but some other things that we are still prioritizing for We are still prioritizing among them, but yeah, this is the plan. The next one is probably for you, Anastasia. Yeah, so the question is how to prioritize the backlog. So if you can debug the issues and prioritize them in backlog. Yeah, sure. I'd like to share my screen now just to show it. Yeah, here it is. Nice. Okay, so speaking about the whole Agile story, the Agile board, of course, it's not just a table. That's where it started from, but it provides the fully functional Scrum and Kanban functionality. And of course, you can manage your backlog here. Your backlog sprints your progress, burn down charts, and the backlog can be opened right on the board. and you can prioritize your issues by dragging and dropping them here. And you can add them to the board. And you can select the saved filter that is used for the backlog, like a list of issues that is your backlog. You can edit them, and you can also add it in a separate tab. So yeah, the backlog also supports the tree view and the list view. so if you don't want the hierarchy you can just switch to plain plain view and here it is uh so yeah this is uh this is how you can manage your backlog right on the board um and i hope i answered the question yeah it seems to me too so the next question is um You mentioned automatic issue creation directly from incoming external email. Which program automation do you use there? Yeah, my screen disappeared. Can I get it back? Thank you. Yeah, so there is a mailbox integration, and its main purpose is to fetch emails from a mail server and convert them into issues in U-Track. It can be configured in literally one minute because uTrac Cloud provides a default mailbox configuration for you. So I'm now on the mailbox integration page and all I need to do is to add new server you see this is a default one but i can configure my own if if i want to the default one is the easiest one you see you are provided with the default mailbox address and um uh yeah i'm now adding the server and now i just need to configure the rule the rule is where i map this integration to project in my u track so all is all emails sent to this address should be converted into issues in my do i have yeah i do in my help desk project and i will be the maintainer and there is also a set of filters i can use for example i can if i don't want all emails to be converted into issues i can filter them for example by recipient recipient address uh or by patterns also i can specify who will be said as a reporter of an issue. So you see the default option is that if such user exists in U-Track, it will be set as a reporter. Otherwise, I will be set as a reporter. And also, it is possible to apply some actions to create issues. For example, if you want to all issues created from emails to be automatically tagged with, I don't know, tag helpdesk. like that yeah so all issues will be automatically tagged and yeah that's pretty it uh your mailbox integration is configured um yeah so this is how you convert your external emails into issues that's thank you looks great then to the next question maybe uh yeah i can i can probably answer What are the differences between the integration of Slack versus using JetBrains Space, needed as a messenger for the team and for notifications? Well, actually, we think that JetBrains Space is way more than just a messenger. It's actually a complete development team environment for software development teams that includes code hosting and package repositories and the... CI, CD facilities and also automations and much more. That said, for U-Track we built the integration with space around the source code and VCS commits. Of course, we showed the statuses as you see in the demo. We showed the statuses in the issues in U-Track. So you can use them of course in parallel. But well, for For the Slack integration in Utrecht, the same as with Telegram, it's mostly focused on delivering notifications to the team. So for notification purposes, there are integrations with Slack, Telegram. Of course, you can get your notifications in mailbox or in mobile app and also in the building notification center. And space is something that you use as a development environment for the team as an alternative to multiple products. in a portfolio. I hope that covers it a little bit. And yeah, maybe to the next question then. The next one is about renaming fields. I guess the question is that if you have mandatory fields that are required to be filled when creating an issue, and if you rename them, how it's possible not to ruin your automations and workflows. Yeah, so the answer is that it is possible when you create a workflow in a JavaScript editor, you specify the requirements of this rule. That means that this rule will run only if all requirements are met. For example, you define that this project, like your project, should have the due date field. And if you have a specific time period, And if there is any mismatch, for example, you rename the field and now there is no due date field in the project, the workflow will say you like something is wrong. You don't have such a field, please rename it or update the rule. So it will be like quite transparent for you. You will be able to, you will know that your workflows are now affected and you need to edit them. So yeah, if the question is that you need to rename fields that take part in workflows, specifying the requirements in your rules is the way to go, just to know that the rule is affected. Okay, yeah, I think I think you're covered here. Yeah So maybe yeah next one is a little bit easier Do you have plans for integration? Microsoft into Microsoft teams. Well, you've got some demand actually they've got a feature request. There are some roles for it But but honestly I cannot share at the moment some estimated delivery time for this, so we are in process of prioritizing it. So please, I will post the feature request details in the comments after the webinar, so you can follow the request and see and follow the updates there. Actually, by voting for the request and by starting it for yourself using the star thing there, you can subscribe to the notifications and if something changes to the feature request you will know about that. Nastya, do you have your next one? Yes, I do. The next question is... By the way, can I have my screen back please? Thank you. In your example you're using projects by unit names and the creation of the website is... cross-unit functionality so the website creation tasks are part of different programs so how they are linked so yeah um it is possible to link issues from multiple from different projects i will show you how it looks um yeah this was lena's task and you see that it is linked with the web development project issue this is design issue and this is web development so they are basically from different different projects. So there is no limitation in linked issues from different projects. You can connect your initiative's issues from different projects using these links. And we have a set of default links, link types that you can use. And of course you can add your custom links. For example, if you don't like the relate to, you can use your own name. is more suitable yeah and you see that i can enter i can enter like any uh let it be i don't know uh marketing issue yeah this one yeah it is linked now so no limitation at all uh this is this is the case if you have uh if you have a project for each team so when you need um a combined input, a combined effort of these multiple teams, you can link issues from different projects. But there is also another way you can create a project from scratch that will be devoted to this initiative, like launching a website. So you have a project, launch a website, and you have all issues related to this initiative in this project, if it's easier for you or if it's more suitable. So it's just It's just about the process you follow. You can choose the one that suits you best and any option is possible here. Yeah, we can move to the next question. Do you have your next one or do you want to meet? Next one? Yeah, I can. The question is, does the automatic fetch work if you enable... the CI CD and define a job. In our examples after you create or enable CI CD it stops automatic fetching and you have to recreate the connection. By design automatic fetch automated fetching should work until it disabled explicitly so the behavior you described is not normal And we'll be happy to assist you if you reach out to our support. You can submit a support request, describe the situation, and we'll help to configure it properly so it works without any interruptions. Sounds great. And the next question. Yeah, go on. Yeah, maybe... Maybe about the guest dashboard. So the question is how to configure external access to guest dashboard, guest issues list, et cetera. Do guests need JetBrains licenses for access? Yeah, so yeah, since my screen is enabled, I will show you how it can work. So the guest access in U-Track is controlled by a special guest account. If it is blocked, then external users cannot access your U-Track at all. So you see it's blocked here, but I can unblock it. And then... Everyone who knows my U-Track address, they will be able to access it according to guest user permissions. So, yeah, my guest account has some permissions. And now let's load out and see what I see when accessing U-Track anonymously. So you see, I'm not... I am. Let me open an anonymous tab. Yeah, so depending on what permissions you define for the guest user, the guest user will be able to access your U-Track, like your dashboards or your knowledge base or even your issues, if you find it reasonable. Actually, this is how you provide this external space. So you see this is dashboards. I'm not logged in. And this dashboard can be used as a landing page for my users. And now I'm going to the knowledge base. It's also open to anonymous access. So I see lots of information. Probably that's not what you should open externally. But. As I said, it all depends on the permissions granted to the guest user. Yeah, so this is how your external users can access your knowledge base, your public knowledge base. Let me see if we have our announcement. Yeah, public knowledge base. Yeah, you see. So this is kind of a public knowledge base that external users can access and get their... the answers even without logging in. Speaking about licenses, the guest account consumes one license slot but each user can use this guest account to see this information. So if the guest account is unblocked then it takes only one license slot from you and anyone can access the information. If you want users to, if you want to, well, you will, in this case, you will not be able to identify your users because they all access your U-Track via guest account. If you want to identify them, then each of users should have their own account and consumer license swap. Yeah. And we can go to, there is also a question about exporting timesheet. Okay. Yeah, I'll take it. Is it possible to export timesheet via REST API? This endpoint is not public, maybe yet, so it's not documented, but it is possible to export timesheet reports into a CSV file and then you can proceed with it further and log in. Now we need to log in. Yeah, so I think that's the answer. Most of our reports have an option to be exported into CSV or I should have some, yeah I do. Most of our reports have an option to be exported as CSV file or excel file. So you can use it to export reports and to process the data further. And we can move to the next question. Great, yeah, we've got one about the SonarQube. Are we having any integration with it for the static, the tool for the static code analysis? To be honest, this is not something that's on table right now. And that's why I'm actually... we would appreciate if you could stop by our public task tracking that I mentioned, utrack.jetbrains.com and just file a post for us, a feature request, so we could better understand what is expected from the integration. And just by the way, You probably didn't know about that, but JetBrains is quite recently started to work on the code quality platform for one of your favorite CIs. It's called Kadana. You can check it out on the JetBrains.com slash Kadana. I will post the link here in comments. And yeah, it's actually... works the way that it's evaluating the integrity of the code that you have and enrich your CI-CD pipelines with some of the popular features that many teams need. Yeah, that's about the integration of SolowQ. Yeah, the next question was about the help desk. If we have a plan on... keeping in mind solution companies with multiple partners and multiple SLE levels when designing this feature. Do you want to answer or should I take it? Yeah, I can actually. The short answer is yes, they do. This is actually the scenario we are working on and try to cover. For now, actually the timesheets also is part of this process because we are having in mind teams that are working with multiple partners and do some external services to various counterparts in their work and the same thing with Helpdesk. We will cover the multiple levels for you to be able to support. several flows of incoming requests. So you can have several helpdesk projects and you can configure each project separately on the project level with all the possible configurations available separately for your various helpdesk scenarios. Yeah. Thank you. The next one is will you join the tables with you? For example, when clicking on issues so you can have the light version view in the pro version. We actually we are working to bring these two interfaces together. Yeah, so we're trying to track your request too to make sure that as a result will bring the best. possible experience for our users and take like the best from both versions. The next one is how to add a tag to issue while subtask was added. That's actually a perfect use case for workflows. So yeah, I think I'm not sure I will let's try i'm not sure it can be created with a workflow constructor but let's see uh so our use case is that if um if a subtask was added we need to tag an issue well i'm not sure we'll be able to to check the subtasks but i will show you um a simpler use case um that covers when just an issue was created uh if you created, you should create it, new, yeah, new issue created. Yeah, when I say that it's not possible to do with the workflow constructor, it only means that it is possible to do with the JavaScript editor. So the total use case is totally, the use case is totally possible, and you can create it. But right now, for the sake of the simplicity, I will show you a simpler case. When a new issue is added, we will tag it. with, let's use the tag mailbox, yeah, and that would be the marketing project and the name tag an issue. Okay, I hope I have this tag. Let's see how it works. A new issue and I need marketing project. Check the tag and create this issue. and you see the mailbox tag is added right away. So it was like the simplest automation that can be created like in one minute and of course you can enhance and expand it if you need. So for example you can assign it automatically to someone or you can check the linked issues like a subtask that was the initial use case and tag issues that have subtasks. Yeah, now we're going to the next question. Yeah, maybe the next one is... Yeah, I will have a couple of next ones because they are relatively easy. About the Gantt chart, the question is to support, to change the coloring of the issues on the Gantt chart based on the SIE, for example. Actually, for now, the Gantt chart color scheme is based on the time estimation, so you visually see the difference between... the overdue tasks and tasks that are still good to go and still run as planned. So yeah, this is a perfect case for the feature request again on our public tracker utrack.jetbrains.com. So if you see how it could be helpful for your team, please describe us, trust your scenario so we can see if it's something worth to explore. Thank you. One more of the same kind, but with a little bit different answer. So the question is, will Utrecht Lite ever support Commons? Yeah, like Anastasia said, we are working on bringing these two experiences of Utrecht Lite and Classic more closer together. So the Utrecht Lite will support Commons. We are actually working on it and planning to release it early in 2023, I hope. And yeah, and one more. I can start it if you have anything to add, please, please, please help me. So the question is how to use custom queries for swim lanes. The answer is also short. It's not possible yet, but there is a feature request. So we actually would like to know the demand for it. So please vote for it. We'll post the link in the comments. Please follow it. Yeah, I have a small addition here, if you don't mind, that it is possible to define swim lanes by tags and that provides you a more agile approach because you can mark any issue with a tag and then swim lanes defined by tags will contain issues marked with this tag. So it's not custom queries of course, where it's something because you can You can configure your processes or automations so that issues that don't have something in common can be defined by a field. They will be united by a tag and you will display them on the board using this tag division. That's it. Oh, yeah. And the next question is... Next? Yeah, go on. Go ahead, please. About the user management. Oh, yeah. We also have a question. Yeah. For the on-premise installation of U-Track, is there a possibility to integrate a third-party user management? For example, firing off identity management. Yes, it is. Generally, it is possible. Can I please have my screen back? I will show you what we have here. So currently you can configure authentication via several providers and this is the full list that you can see. So for example if you use Active Directory you can configure your YouTrack so that your users can log in to YouTrack using their Active Directory credentials. The same goes to Google, Azure AD, I don't know, GitHub, Bitbucket. Yeah. And yeah, we support all 2.0 and XAML and other protocols. Yeah. And there was also a question that it would be nice to have a top of column and bottom of column function on the Kanban board in order to prevent long drag and drops. Yeah, that's actually a nice feature request. Thank you. We'll share it with the design team, with our UX team to consider. Sure. The next one is, yep, I can answer also. Do you have an integration with Terola? Yep. The answer is also short, not at the moment. And actually, we're working on the flexibility for agile wars in utrecht to add even more flexibility there uh so um yeah for for the travel we are only considering um to uh to add more automation to import from there and there is a feature request and we will be working on that for sure yeah i promised it could it would be short the next one is the texture yeah next one is the Utrecht Sharp library for integration with Utrecht from C-sharp actively developed and supported? Well, we consider this library more or less feature complete, so we can't say it's actively developed, but we for sure we provide all maintenance and support that is needed for it. So if you have any questions, please feel free to contact us. The next question is, let's say you have two epics having a few issues. For the backlog, the top will be a mix from these two epics. How can I see backlog respecting the order and still see what epic each issue is part of? Well, that's a tough one. Well, I guess having a tree view in backlog will not happen. how because it will not maintain the custom order rate i guess that the solution well it may not be the the the beautiful one but you can mark issues with a tag and this stack will uh relate to the epic to the parent topic of this issue so when you will have a list uh about your backlog which is ordered each issue will have a tag that says what etiquette relates to. Well, that's kind of a solution, I think, because I cannot come up with it. Sorry? Yeah, I mean, it's a resolution. And I also wanted to add that this is exactly one of the type of the questions when I mentioned that we are going to work on expanding the planning and support for planning boards and planning and resource management functionality. It's kind of related in terms of how we see the implementation. Yeah, but we're going to explore those scenarios and thank you for the example. We probably can cover it in the future of MAP. Yeah, thank you. The next question is how can you separate tasks, internal only access and external access? And give access to external users who are outside of company only to those set for external access? I assume group access. Yeah, so the question is that you want to open several issues of your project for external access, but you don't want the external users to see all issues of your project. Well, generally, you can configure the project settings. Yeah, so first of all, there are several parts of my answer. First of all, there is a setting that controls the default visibility of issues in your project. So by default, issues are visible to everyone who has permissions to see issues in that project. But you can narrow it down to, for example, your team. Let it be, I don't know. marketing team. Yeah, right. That's not very smart since it's a web development project. I'm sorry, I'll change it. Yeah, now it is smart. So now issues in the web development project will be restricted to the web development team. And what we can do next is... Let me show you how it works. So it's web development... um let it be external issue right um Okay, it doesn't work for some reason. Okay, let it let do it manually. So if we if we limit the visibility of an issue to to the team now External users will not be able to access it even if they have permissions to view issues in this project So this is the approach you can follow you can limit the visibility of issues in your project to your team or for example to your company and then you can manually add separate users like external users or the guest user to this issue to open it to external access. And also once we have the extended help desk functionality there will be like more distinguished support for internal and public visible projects and issues so I think it will it will become more transparent in the nearest future. Yes, hopefully. And there are a lot of good words from you folks. Thank you for watching, thank you for those thank yous. There's always this part of the questions as well, and the feedback is also very much important for us, and this is the part that I appreciate the most actually. And thank you on behalf of the whole team for watching and for... for using them for helping us develop the product with all your feature requests and feedback and everything. Yeah, that is greatly appreciated. We actually feel your support. Thank you. Yeah, thank you very much for your kind words. Yeah, and also there is a question, when do we expect the next update of uTrack? Well, since we provided a major release like one week ago, I'm not sure if you checked it yet, but please feel free to check. There is a plenty of new features released and I think the next one can be the next major release can be expected in Q1 of the next year, right? We hope for it. Yes. Yeah. But we also try to, you know, to release minor updates like once in a couple of weeks so that you don't have to wait for for small updates for too long. Oh yeah, one more question. Can someone without access to a project, not a guest, create issues for another project? Yeah, sure. Actually, the create issue permission works on a per project basis. So you can say that, for example, this user can create issues in project X but cannot create issues in project Y. Yeah, so project A, project B. Yeah, sorry, I'm lost with the letters. So yeah, I can show you a basic overview of how permissions work. So basically how access management works in YouTrack. We have a long list of permissions, they are very granular. and they define what a user can do. So, for example, this permissions control, the user can read article or create group or read issue or update issue, and you can combine these permissions into sets, and we call this sets roles. So you can create custom roles. Of course, we provide a set of default ones. And you can create your custom roles to define the level of access that you need. And then you can grant these roles to users or groups, either per project or globally. If you grant a role per project, then permissions that work on a per project basis, they will grant this level of access only in the project where this role was granted. And if you grant a role globally, then a user will be able to do all this stuff like in all projects. So yes, it is possible to allow a user to read issues only in one project or only in two projects or create issues in one project but read issues in a second project. Yeah, that's it. Exactly, exactly. And right in time. So yeah, we've done with all the questions. That's not it. If you ever have some more questions for us, please feel free to post them in the comments or reach out to us in the support ticket or via email we've shown you today on the slide and we will add it in the comments to this video. Again, thank you for watching. Have a nice experience with Utrecht. Great amount of success with your projects. Yeah, have a nice day and thank you for joining us today.

Hello, hello, good morning. It's morning in the sunny Amsterdam today. I'm happy to see you all joining our event.

I'm Yelena, the Utrecht product marketing lead, and I'm happy to introduce Anastasia, our Utrecht technical support lead. And today in our session, we will show you a live demo of Utrecht. And as you probably know already, Utrecht is an agile and flexible project management tool.

There you can also track your tasks. And it is currently trusted by 85,000 teams in more than 200 countries. and they all are using YouTrack to plan, track and manage their projects.

Half of our customers are from the IT, software and gaming development world, and the other half is from many different industries and they are building everything from FinTech solutions to creative video ads with YouTrack today. So we are here now to show you how they manage their team projects and how they manage their knowledge base daily. And you know each team has their own ways to work on their projects.

Your track is used by various teams in software development, quality assurance, data insights, marketing, design, web development, product management, and even in human resources or by administrative teams and management board members and even by chief executive officers. So every team needs a tool to adjust to their business process and hopefully not vice versa. That's why we actually designed Utrecht for enterprise companies, but it's also loved by small teams that get Utrecht for free.

And the free version is fully functional and it is available for teams up to 10 members and you're free to choose cloud or server. And for today's demo, we've chosen the basic scenario and actually some non-technical roles in the team, so you could see what U-Track consists of and how you could adjust it in your case. We hope to get to the bottom line idea of how project and task management works in U-Track, how you can build in your knowledge base, what can you do with interactive Gantt charts, how to create agile boards, and how to use time tracking and reporting. reports and multiple dashboards in your business flow. And also, we'll try to give you a glimpse of how the HL process management is supposed to work in Utrecht, if a workflow constructor and JavaScript workflows.

So we hope that you'll get a helicopter view of projects and task management in Utrecht. And be sure, if you at some point decide to try Utrecht, it's... easily integrates into your environment.

Hopefully you see here on screen some of your favorite products and solutions and we'll also show you today how some of these integrations work. But better to see something once, so let's get started with the demo. Anastasia, yeah the floor is yours. Yeah, thank you, Lena. Hi all, it's Anastasia here and let's do the demo.

So today we'll show you a demo of U-track. project management tool and we'll see how various teams across the world both technical and non-technical use YouTrack in their daily processes. So to demonstrate that we try to imagine how your working day may look like if for example you need to launch a website for an upcoming conference.

So today we'll imagine that I'm a member of the web development team and together with my teammates from the design team, Lena will play a role the design team today, and from the marketing team we'll try to launch this website. Okay, so let's go, let's see how various teams use YouTrack to organize collaborative work of multiple teams even without personal meetings and how they use it to achieve their results in time. So what you see here What you see here is a page of a list of projects.

In U-Track you can create projects for almost any organization that you find suitable. You can create a project for a team, or for a department, or even for the whole company. Or you can, for example, organize your projects if you have some separate initiatives.

organizing a conference in our company uh we we create projects for uh for teams so that each separate team has their own project so what you see here is a project page and well it's team and also their backlog also on right sidebar you can see a list of project settings and project administrators can serve through the settings to configure the project like integration functions, automation, set of fields, level of access for the team. We'll check what the project can contain later. But now what I want to say is that each project has two main parts. The first one is the knowledge base. We truly believe that documentation is everything.

That is why we implemented the knowledge base so that you can store your data next to your issues. Well, the knowledge base is basically a set of articles, you can see them here. So you see a list of projects and each project has its own hierarchy of articles.

An article may represent maybe just a plain text or a link or a table or an embedded video. You can also use Google documents and checklists, whatever you find suitable to express your idea. How you can use the knowledge base?

So the first scenario is organizing a public space for your external users. For example, you can publish your external announcements here, or you can organize an FAQ section so that your external users can get replies to their questions even without pinging your support team. The second scenario is organizing an internal space for your team or for your company so that you can store there your vacation policies or an internal roadmap or store meeting minutes and this is exactly what we do so when we are about to um to organize something big like i don't know a conference we house the call and we invite their all all involved parties all teams and we discuss the main points of what we are going to do.

So we discuss the deadline, the scope, what features do we need and what teams do we need and we write down everything that we discussed to the article so that even those who missed the call they can just open this article and stay up to date. Of course it's possible to start a discussion in comments and you can easily mention your teammates to let them know your opinion and they will be notified about new comments. Or it is possible just to start an article, to add it to favorites and to receive notifications about any new update.

If we think that this initiative is not public yet, so we don't want other teams to know about it, we can just restrict its visibility to... any team we want to a group of users and no one will know about it until it's time yeah and of course it's easy to get lost in this infinite list of articles that is why there is a search that allows you to to easily find what you need right now using a keyword yeah so when we have everything written down it's now time to proceed to our tasks and we are now moving to the Second important part of what each project has issues. An issue may represent some minor task like fixing a typo on a website or something really big like preparing a conference. You can also manage business trips or salaries or hiring process or approval process using issues.

And we'll now see how it can be done. Yeah, so issue always belongs to your project. You see there are issues from.

multiple projects here so it's kind of our backlog and issue always inherits its project settings its integrations automations uh a set of fields and you see there are assignees my teammates who already work on these issues and i see that lena is um is assigned to this design issue so let's ask lena to show us how her working day is going and um and how she solves her tasks. Lena, the floor is yours. Yeah, thank you. I'll be happy to show you my side of things.

You now see my screen and my U-track. So imagine, again, I'm a design team lead and our team is responsible now for providing the web development team with everything they need to launch the website. But first things first, I would like to change the theme here to the darker one. Yeah, now I like it better.

Actually, I can start my day. Usually, I do it by checking the notification center and seeing if there is anything new for myself, if there are some new tasks available, and checking what I actually need to do with them. So, as you can see, I can check out the task right away and...

easily proceed to the task right from the notification center. But for example, some of other teams not only interact with internal tasks, but they also have a mailbox integration set up, and they actually have the incoming emails fetched as issues or tasks to their dedicated project. So here is my urgent task for today. Let me check how it works.

Yeah, so I can go to the tasks right from the notification center. And yeah, what I see here is here is the details, the design department team actually would like to know about the tasks. So we set it up so we see the priority and you see it's critical now.

You see there are types of the materials we need and yeah, and for example, its banners and if you have animations here you see that we would like to specify the video format for the animations and so on. And this is how the design task look like and let me first of all set the state here to in progress so everyone is notified that I'm working on the tasks this is critical and no one is pinning me with some questions for some updates while I'm I'm busy with the task. But for example, if I switch to one of my recent tasks and check how the task in the HR project looks like, you see that my colleagues there, they set it up to look completely differently.

So they need an employee ID, for example, there, and they've got a type of the task, for example, annual review. And if we set it to the annual review, they are they can have some specific fields need to be filled in. And if I edit the task, so they, for example, require the annual goals and the annual review results to be posted in the task, and the layout of the task looks completely differently.

So this is the way how they like to do it. But let me get back to the banners. I'm working on. Since the task is critical, let's say I'm already done with doing the job, so I can pin Anastasia here and say, like, please have a look at this.

And yeah, I can, for sure, I can add the button here to the, yeah, and it's positive. Let's say I'm a design team and we are working on the team member and we are working on the banners for the website. So I would like the team to preview how the banners will look like on the website so I can post the Figma link right here.

I've got some Figma link in my backlog So I am embedding the link and you see that I add the comment everyone who is logged into Figma can not only see the banner itself, but also can have a look and interact with it from the U-track interface and see how it works on the actual page draft. And can do something right from the U-track interface without even leaving the U-track. So yeah, with that all said, let me say that the stage for the task is waiting for review.

and I will be waiting actually for nice, for Anastasia to have a look at what I've done. And meanwhile, I can. work with some of my other tasks. You see, here is my list.

I can set it up to look like more more like a simple to-do list with no details or I can add the fields, the details that I would like to see. For example, I need to know the SIE, I need to know the due date of the tasks and I would like to the due date to be the first thing I see about the task and everything. What can I do else? I can, for example, sort, of course, by some of the details here, or I can filter the tasks, so I can see the design department tasks only.

Also, I can use some more powerful filters. For example, I can do a search for unresolved tasks or some more you see there are there are a list of unresolved tasks or i can do some more complicated for example relative date search so i can choose to filter the tasks created for example last month let's see so let me uh and you see your track is actually helping me to uh to perform the this search the way i need it with some with some tips here. So yeah, this way I'm filtering the tasks that were created last month.

And it's a relative search. So that every time if I save it, for example, let's say I name it last month and save the search. And each time when I have it, yeah, I have it here in my saved searches. I can share it with my team or use it in some reports later. And each time then I open this search results, I will see the relative search.

So it's actually gonna be the last month, regardless of what date is it today. Yeah, this is how my backlog looks like for the team. You can see there are no tasks assigned for me. So let me check the notification center once again and see if... if there are any news for me and there are some news actually you see that Anastasia not only approved but also she likes the banner so what I can do I can do the change of state of the task so now it's fixed and why I'm smiling because it was the last my last task for the for the day and for the week because actually I'm going on vacation And let me use this example to see how YouTube workflows can help me with this.

Since I'm a team lead, I wouldn't be leaving the work without actually making sure that someone is taking care of the tasks ahead. So I would like to set some workflow. to the rule that will check the tasks during my absence and that actually will reassign the tasks to one of my teammates. So let me name the role learning location, let me choose the design department project and in my visual workflow constructor I can actually filter some conditions and actions for the role. So I'm going to to check the issues that were created for during my absence and my vacation starts starting today and yeah and I will be there before yeah it's starting today and I will be yeah and I will be there until the end of November yeah here's the the period and also I would like to check if these created tasks...

I would like to check the field. So if those created tasks are assigned to me, so I'm checking for the assign field and if it's set to myself... Then I'm going to change it and then I'm going to update it.

I'm going to use the SAE field to be set again to one of my colleagues. And yeah, I agree with Carrie that she will be taking care of that. And I wouldn't be...

I wouldn't like to do it in silence, so I would like the comment to be... To be added, so I choose also a comment. I will say to everyone that I am resigning the task during my absence. And I would like everyone to see that it's me who is posting this comment.

So, yeah, I'm selecting again myself. So, yeah. This way I'm all set. You see the conditions, directions.

I'm saving the rule and I'm good to go off to my location. For sure, I wouldn't be left without any information. I can reuse integration with Slack and Telegram for Utrecht to get some notifications on the updates in the projects and tasks I follow.

And also, for sure, I've got a mobile app. And in this mobile app, I'll see a lot of states and notifications and the jailboards for the tasks I'm working on. But hopefully, I wouldn't be seeing any surprises there.

So I hope you'll manage just perfectly without me. Nesta, how do you think? Is it possible? Yeah, I'm sure it is.

Because, well... we know that the design team is pretty strong so that i think i'm sure they will manage all critical tasks while you are away uh okay so um of course of course let's check that this workflow works uh fortunately or unfortunately i'm having a critical design tasks task that um that should be done until tomorrow and let's see if lena Liana, could you please, please, please fix it today while you're still in the office? No, you can't.

Okay, so Liana, you see that this issue was automatically reassigned to Carrie, and there was a comment added automatically on behalf of Liana that she's already out of the office, so she will not be able to take care of this issue. But you see that it was not left unattended, it was reassigned, so our teammate will take care of it. care of this issue and we will not miss anything important.

Of course there was like the simplest scenario where you can use this workflows. Workflows is a very powerful feature of Vue track and you can use it to react on some events like updating a field and the workflow can update fields for you or add comments or check commits or pull requests, it can modify description. it can create subtasks, new issues and also it can react on schedule, run on schedule.

For example, it can create reporting issues for you each Monday. Let me show you one more example of how it can work. So we in our company, we have a release process and each time we are about to release something, we need to create a meta issue about this release. So the release is a process, so you need to follow it to do everything properly.

So in our company we have a specific process to follow and we decided to automate it because release is something you do quite often and it's a set of repetitive tasks, so that's a perfect case to be automated. So each time when I switch... um switch to the release type a workflow automatically substitutes this description for me so that I don't forget to specify the release name the version number and description let it be you track release yep and the version also the workflow makes sure that I'm not allowed to create a release issue without setting a due date yeah so let it be like one week from here that's a tight planning but whatever yeah and now i'm all set and i can create this release issue and you see um that in our company the release breaks down into a set of steps and the workflow automatically creates this set of steps for me so this meta issue is now a sequence of these um of these steps so we need to prepare a blog site, to localize the materials, to enable new features, to publish them, etc.

And now I don't need to create these steps manually because it's very time consuming and I can miss something important. It was all created for me, now all I have to do is to follow these steps. What we use workflows for is to automate some routing processes for us so that we don't forget about them, so that we don't miss anything important and so that we can spend our time doing really important things.

And more about workflows, how you can build them. Learn the show does. the workflow constructor where you can build your workflows by dragging and dropping blocks so you don't need any programming skills for that and if you need more advanced and more advanced workflows for example if you need to interact with third-party tools if you want to send http requests or something else you can switch to the javascript editor and create even more powerful automations there Okay, so yeah, that's it with the workflows.

And yeah, we saw the list of issues we are about to do to launch our website. But of course, it's not enough just to have this set of issues and the deadline in front of you to finish it in time. There is one more very important stage that you need to follow. And I'm talking about planning here. To organize the planning stage correctly we use the Gantt chart.

Okay, so this is the Gantt chart in front of you and the Gantt chart considers dependencies between issues and their start dates and their durations and builds the planning activity for you. The Gantt chart predicts the end date of your process so you can see if you are in time or if you need to descope something or schedule something and it's pretty easy to add new issues to this chart you see that yeah you can create a brand new issue or you can add something from existing ones for example if we want to see all critical tasks that we have yeah i can add them one by one or i can add all 17 issues to the chart yeah you can see here you can see issues that take parts in the chart now you see there are issues from multiple projects so you are not limited to use only one project and you can um you can add the whole activity that you are now planning to this chart to see the whole picture in front of your eyes um the chart is interactive meaning that you can drag and drop these issues you can for example update their duration or alter their start date you see they are updated here immediately Yeah, and one more important point is that the chart immediately highlights if any area of your project requires immediate attention. So imagine you've planned all the activity and now you're working on it. But let's see, we estimated this issue to take one day and we've already spent five hours doing it. But let's imagine I spent one more day.

doing this issue so it's like more than day and a half in totals it's more than we estimated and the chart immediately highlights this issue in red meaning something went wrong here and probably we need to pay attention you see that the parent issue is still blue because we still have chance to finish it in time if we are faster with these two subtasks okay uh so when we planned the whole activity it's now time to do the issues themselves and we find it very important to to still keep all issues that are in progress now in front of our eyes so that we don't need to go to each team separately and ping them and ask them what's the progress so we use the agile board page to to keep all issues in one place on one page you can use the agile board even if you don't follow any agile process you can use it just as a table so you can see that's basically a table and um uh yeah and uh it has its columns and rows and of course you can define these columns and rows and it can be done like really easily let's take a look First of all, let me tell you how I think it's obvious, but nevertheless, now you see that each cell contains issues that are in a particular state and belong to a particular assignee. Yeah, so that's pretty easy to see the workload of each assignee now and to understand the state of each issue by just looking at the board. Now let's try to modify it.

So you see, these are my states that are currently used for defining the table columns. And of course, they are not hardcoded at all. So you can customize it up to your needs.

You see, there is a drop down where you can add. new state and if you yeah it immediately appears here but if you feel that the new state doesn't deserve a separate column you can easily merge it with for example open so you see now we have opening new issues combining this column and this column already combines three states and of course we can easily modify that yep Right, now we are going to swim lanes, rows or swim lanes, how we call them. So right now they are defined by assignees, but there is a plan of choice for me here. For example, if I want to define rows by priorities, you see, now I have all critical issues collected on the top of the board, right? Or I can, for example, choose project.

to define uh to define swimlands so now i have uh issues divided by their group by their projects so this is what our marketing department have related to to launching our website and this is the design department workload well they have no the web development is a champion right yeah and also it is possible to use issues themselves to define to define swim lanes. So this is how you can build your issues hierarchy there. So if you have epics or user stories, you can make them swim lanes so that each user story will have their own swim lane and cards, their subtasks will be well cards. But let's get back to our configuration. So we have assainese yeah yeah we have assainese and states and let's see this is lena's issue that she just fixed in front of our eyes and i'm working on my development issue here uh you see that it's in progress so that anyone who opens it knows what what is going on there and besides besides reflecting states um and descriptions in issue we also prefer to keep all development stages of the issues lifecycle in on the issue page.

I'm talking about VCS changes now. So let me show you how it works. So imagine I'm working on some code, right?

And when it is read, oh no, that's not commit yet. I will tell you more about the plugin. So we have a dedicated IDE plugin and Thanks to this plugin, you can see notifications from your U-track right in your IDE, and you can update your issues right from your IDE without leaving it.

So you don't need to switch between two tools, and you can do all the stuff related to issues right in your IDE. So when you are done with your code changes and you are ready to commit, all you have to do is to mention the... yeah you have all you have to do is to mention the issue id in the commit message and push your changes yep push it push it okay now it's pushing yeah it's done and uh we'll now see how it looks in you should be updated yeah you are so you see your track automatically fetched they can meet based on the issue ID that was mentioned in the commit message.

And now anyone who opens this issue page, they will see this commit. They know that it's a work in progress. They will probably know what is going on judging by the comments. But if they need any more details, they can easily navigate to the code changes to the version control system itself. We use space for that.

And they can see the changes or view them, whatever they need. One more important part here is time tracking. So first of all, the IDE plugin allows you to track time automatically.

You see, I have the timer that is that is in the process now and I can post time right to my YouTrack without leaving IDE. Thanks to that I don't need to remember how much time I spent developing my issue and I will not forget to post it to the tracker. But I will show you how it works manually.

We also have a dedicated button here. So you see, let's imagine I spend three hours doing it was development and of course these work types they are not um hard-coded at all so you can add your own or you can modify the existing ones and you can also add a set of additional fields if for example you need to tell billable work from non-billable or if you want your teammates to specify your contractors to specify the currency or the price of work i don't know So let's imagine I was in Los Angeles and at spend time. Yeah, it is added here and you see that issues, overall issues spend time is reflected here in the issue.

And it will calculate the overall amount of all work time records that I've added. When I'm done, I can just easily move the issue to the Fix It column, and now everyone will see that it is done and probably can be tested. Speaking about time tracking, of course, it's not very convenient to surf through each issue to see how much time I spent, especially if I'm a team manager and I need to collect the workload of my team.

I cannot imagine I go through each issue. issue of the project to see the workload of my teammates. So this is what the timesheet page is for.

First of all, you can see a personal workload here. So you see this is my calendar where all my workload is collected. I can add new records right from here. This is a list of issues I can select from.

And also, I can edit existing. existing entities here, entries here. Yeah, also I can check the calendars of my teammates if I want and if I want to see a collective workload of the team I can switch to a work group tab and build a timesheet report that contains time entries from teammates I'm interested in. So yeah, you see this is a collective workload. And I can use this report for billing purposes or just to collect time statistics.

And speaking about reports, we also use a set of U-Tracks default reports. There is a bunch of them. Let me show you some examples. So, for example, there are issue distribution reports.

So you can, for example, check how many issues each assignee has. or you can see issues divided by their priorities. You can also build different tables or matrices. Of course, you can track your progress using the burndown chart or various flows. And you can also track various metrics like manage your SLA, service level agreements.

or to check how much time does it take in your team to fix an issue in average or how many re-opened issues you have. Of course, there is also a classic time report that allows you to compare the spend time, the estimated time and the actual time. So you can choose the reports you are interested in and just use it in your processes.

And of course, you may wonder if there is a page to combine all these metrics on one page. And yes, there is. There is a dashboard page for that. A dashboard page consists of widgets, and each widget may represent a report, an issue list, some calendar, team activity. And depending on the purpose of your dashboard, you can pick different widgets.

So how you can use dashboard? For example, you can create a helicopter view for the executive members of the team. So in this case, they will probably need a calendar with upcoming deadlines and probably a chart that shows how many overdue issues you have and a backlog of your high priority tasks.

And probably they will need to see the team activity. Oh, I'm so active. yeah activity of the team and yeah maybe some workload too the second scenario you can use is organize a guest dashboard so that your external users land on this page when they open your utrap and they can check your team or your public roadmap or your backlog or some announcements And yeah, in this case, you can use also initial list widget and some notes widget.

And one more scenario is to create a personal dashboard. And in this case, your teammates, they can build their personal space and they can keep their personal notes or their personal activity or backlogs. And also they can look forward to their vacation.

here. Yeah, so you see, we are pretty sure that everyone can organize their personal space in U-Track to have their personal board with their current work or their personal dashboards to see an overall state. And of course, each team can have their own personal space to track the activities, to collaborate and to... to deliver results together and what is more important we truly believe that you don't need to adjust your team process to uh to so that it fits you track because you track fits any process it can be customized customized uh in almost any way um yeah so yeah we hope that each team can find can benefit from from using utrac in their daily processes That was pretty it from my side and we went through almost all essential features of Vue Track.

Of course that's not it and you can find much much much more if you dive deeper. Yeah and one more one more thing I wanted to say is that when we finish launching this website and I'm sure we will, we'll have external users who have their questions and feature requests and we need to handle them somehow so to address that we at JetBrains in Utrecht team we are actively working on extending our help desk functionality and yeah Lena will now show us a secret preview of what we currently have Lena up to you I'll be happy to thank you nice yeah yeah you Yeah, I will share a couple of more moments here and while we still have time to look for your questions and we hopefully will take them online right after these couple of points. So in the end we are currently focused on expanding the support for the helpdesk scenario in Utrecht and then the very dedicated type of helpdesk project.

You are going to be able to have almost unlimited reporters and also have support agents in such projects. And we are thinking of paid per user price for the support agents only. And they are going to be customizable, embeddable form so that you can build it into your website or internal portal, for example, and get the support tickets directly to you, Tarek. And also we'll streamline the interface for the support agents to work on these tickets.

For example, use templates and some internal comments that are visible only to team members or publish answers to customers for visible to external customers. And plus Helpdesk will come with editable service level agreements schemes to manage your tickets work for us. And then you will be able to easily set up some escalation rules and some business hours and other other workflows that are helpful for the working with external or internal tickets. It's all coming in the beginning of next year, 2023, and as you can see we are intensively developing new track and planning to add a little bit more. In the future, we are also working on the apps and plugins to be available in Utrecht, to go deeper into the resource planning and management functionality.

And this is the plans for the upcoming year 2023. And also, of course, we are going to polish and deep dive into the better experience with what we already have in Utrecht. And today we've shown you U-Track in English interface, but we've got several languages available for the settings to be set as a main language for the whole U-Track, or also available on a per-user basis, so if you have a team that works globally and works in multiple languages, each user can set up one of the languages for their own to see the interface. in the convenient way.

What else I would like to mention? We usually ask our customers, why did you choose U-Track? And one of the popular answers, of course, more than half of the respondents are usually saying pricing.

And U-Track is available both in cloud and server versions. For the server version, it's also starts with a free plan for 10 users and you can have a granular user packs starting with 15, 25, 50, 100 and so on users. And for the cloud it's a price per user model so if you at some point need more than 10 users it starts with a starting price. It starts with a price of $4.40 per user and the price decreases with the growing of the number of users in your team.

One more answer that we usually get is that it was the functionality. So it's either the team or one of the leaders or the project manager in the team decides that the functionality suits the most. And this is the interesting part of it. of how we try to develop it, right?

Because we're thinking of enterprise teams with multiple functions in the teams, but it also fits for small teams as well. And yeah, this is one of the parts of the answer here. It's because of the free version for small teams, the free version is fully functional.

We have no limitations to it. almost there and it's free for as long as your team is not bigger than 10 members. If you ask about some easy ways to start a new track and to see in action what we have shown you today, we recommend usually to start with the cloud version. You can get it up and running in two minutes.

and use it free forever, like I said, for 10 users. And there are also import functionality for you to migrate tasks from some of the popular trackers. Then if at some point you would like to test the system with the extended team, there are trial versions for you to test it for two weeks in cloud for free. for 100 users and for two months in on server for several thousand of users. This is also going to be a great point for you to create some custom workflows to see if it works for your business processes.

And then if at some point you decide to migrate to a paid version or to add some users into your growing team, then all the data from the trial or from your free training free your track, it will be easily and smoothly migrated to the paid subscription. And here is the thing you might... What I want to know is that the 25% competitive discounts for migrating from any of the competitors to competitive tools is also there for you. So please reach out to us to get it. And for some help along the way, you've got a list of partners, technically certified solution engineers in several companies in various regions in the globe.

And also you direct sales engineer in our... brilliant support team are available to help you with a lot of questions you might have along the way. Yeah, that's it for the part that we prepared for you today.

Thank you for watching. You can see the contacts on the screen, so please feel free to reach out to us if you think of any questions after the webinar. And now we can start with some of them that we already have in chart.

So, thank you for the feedback. Thank you for sharing how you love GitRec and you migrated from another solution. And now to the first question. I can start and then moderate if you want me to. The first question is, when can we get inline comments in the Knowledge Base?

Yeah, this is the popular thing. We've got a... popular uh quite popular feature request you know public uh uh uh tracker on utracjetbrains.com if you haven't heard of that uh we uh use the uh the opportunity to uh to to get feedback from from you from our uh customers in on utracjetbrains.com you can buy pretty much projects for every of pretty much for every of the JetBrains products there and also we of course we follow all the all the requests for for uTorque there are some roles for these and many other updates to knowledge base it's now planned we are planning for the next year for the update for the whole experience for knowledge base not only regarding the e-line comments but some other things that we are still prioritizing for We are still prioritizing among them, but yeah, this is the plan. The next one is probably for you, Anastasia.

Yeah, so the question is how to prioritize the backlog. So if you can debug the issues and prioritize them in backlog. Yeah, sure.

I'd like to share my screen now just to show it. Yeah, here it is. Nice.

Okay, so speaking about the whole Agile story, the Agile board, of course, it's not just a table. That's where it started from, but it provides the fully functional Scrum and Kanban functionality. And of course, you can manage your backlog here.

Your backlog sprints your progress, burn down charts, and the backlog can be opened right on the board. and you can prioritize your issues by dragging and dropping them here. And you can add them to the board.

And you can select the saved filter that is used for the backlog, like a list of issues that is your backlog. You can edit them, and you can also add it in a separate tab. So yeah, the backlog also supports the tree view and the list view. so if you don't want the hierarchy you can just switch to plain plain view and here it is uh so yeah this is uh this is how you can manage your backlog right on the board um and i hope i answered the question yeah it seems to me too so the next question is um You mentioned automatic issue creation directly from incoming external email.

Which program automation do you use there? Yeah, my screen disappeared. Can I get it back? Thank you.

Yeah, so there is a mailbox integration, and its main purpose is to fetch emails from a mail server and convert them into issues in U-Track. It can be configured in literally one minute because uTrac Cloud provides a default mailbox configuration for you. So I'm now on the mailbox integration page and all I need to do is to add new server you see this is a default one but i can configure my own if if i want to the default one is the easiest one you see you are provided with the default mailbox address and um uh yeah i'm now adding the server and now i just need to configure the rule the rule is where i map this integration to project in my u track so all is all emails sent to this address should be converted into issues in my do i have yeah i do in my help desk project and i will be the maintainer and there is also a set of filters i can use for example i can if i don't want all emails to be converted into issues i can filter them for example by recipient recipient address uh or by patterns also i can specify who will be said as a reporter of an issue. So you see the default option is that if such user exists in U-Track, it will be set as a reporter.

Otherwise, I will be set as a reporter. And also, it is possible to apply some actions to create issues. For example, if you want to all issues created from emails to be automatically tagged with, I don't know, tag helpdesk. like that yeah so all issues will be automatically tagged and yeah that's pretty it uh your mailbox integration is configured um yeah so this is how you convert your external emails into issues that's thank you looks great then to the next question maybe uh yeah i can i can probably answer What are the differences between the integration of Slack versus using JetBrains Space, needed as a messenger for the team and for notifications? Well, actually, we think that JetBrains Space is way more than just a messenger.

It's actually a complete development team environment for software development teams that includes code hosting and package repositories and the... CI, CD facilities and also automations and much more. That said, for U-Track we built the integration with space around the source code and VCS commits. Of course, we showed the statuses as you see in the demo.

We showed the statuses in the issues in U-Track. So you can use them of course in parallel. But well, for For the Slack integration in Utrecht, the same as with Telegram, it's mostly focused on delivering notifications to the team.

So for notification purposes, there are integrations with Slack, Telegram. Of course, you can get your notifications in mailbox or in mobile app and also in the building notification center. And space is something that you use as a development environment for the team as an alternative to multiple products.

in a portfolio. I hope that covers it a little bit. And yeah, maybe to the next question then.

The next one is about renaming fields. I guess the question is that if you have mandatory fields that are required to be filled when creating an issue, and if you rename them, how it's possible not to ruin your automations and workflows. Yeah, so the answer is that it is possible when you create a workflow in a JavaScript editor, you specify the requirements of this rule. That means that this rule will run only if all requirements are met.

For example, you define that this project, like your project, should have the due date field. And if you have a specific time period, And if there is any mismatch, for example, you rename the field and now there is no due date field in the project, the workflow will say you like something is wrong. You don't have such a field, please rename it or update the rule.

So it will be like quite transparent for you. You will be able to, you will know that your workflows are now affected and you need to edit them. So yeah, if the question is that you need to rename fields that take part in workflows, specifying the requirements in your rules is the way to go, just to know that the rule is affected. Okay, yeah, I think I think you're covered here.

Yeah So maybe yeah next one is a little bit easier Do you have plans for integration? Microsoft into Microsoft teams. Well, you've got some demand actually they've got a feature request. There are some roles for it But but honestly I cannot share at the moment some estimated delivery time for this, so we are in process of prioritizing it. So please, I will post the feature request details in the comments after the webinar, so you can follow the request and see and follow the updates there.

Actually, by voting for the request and by starting it for yourself using the star thing there, you can subscribe to the notifications and if something changes to the feature request you will know about that. Nastya, do you have your next one? Yes, I do.

The next question is... By the way, can I have my screen back please? Thank you. In your example you're using projects by unit names and the creation of the website is...

cross-unit functionality so the website creation tasks are part of different programs so how they are linked so yeah um it is possible to link issues from multiple from different projects i will show you how it looks um yeah this was lena's task and you see that it is linked with the web development project issue this is design issue and this is web development so they are basically from different different projects. So there is no limitation in linked issues from different projects. You can connect your initiative's issues from different projects using these links.

And we have a set of default links, link types that you can use. And of course you can add your custom links. For example, if you don't like the relate to, you can use your own name.

is more suitable yeah and you see that i can enter i can enter like any uh let it be i don't know uh marketing issue yeah this one yeah it is linked now so no limitation at all uh this is this is the case if you have uh if you have a project for each team so when you need um a combined input, a combined effort of these multiple teams, you can link issues from different projects. But there is also another way you can create a project from scratch that will be devoted to this initiative, like launching a website. So you have a project, launch a website, and you have all issues related to this initiative in this project, if it's easier for you or if it's more suitable.

So it's just It's just about the process you follow. You can choose the one that suits you best and any option is possible here. Yeah, we can move to the next question.

Do you have your next one or do you want to meet? Next one? Yeah, I can. The question is, does the automatic fetch work if you enable... the CI CD and define a job.

In our examples after you create or enable CI CD it stops automatic fetching and you have to recreate the connection. By design automatic fetch automated fetching should work until it disabled explicitly so the behavior you described is not normal And we'll be happy to assist you if you reach out to our support. You can submit a support request, describe the situation, and we'll help to configure it properly so it works without any interruptions.

Sounds great. And the next question. Yeah, go on. Yeah, maybe...

Maybe about the guest dashboard. So the question is how to configure external access to guest dashboard, guest issues list, et cetera. Do guests need JetBrains licenses for access? Yeah, so yeah, since my screen is enabled, I will show you how it can work. So the guest access in U-Track is controlled by a special guest account.

If it is blocked, then external users cannot access your U-Track at all. So you see it's blocked here, but I can unblock it. And then...

Everyone who knows my U-Track address, they will be able to access it according to guest user permissions. So, yeah, my guest account has some permissions. And now let's load out and see what I see when accessing U-Track anonymously.

So you see, I'm not... I am. Let me open an anonymous tab. Yeah, so depending on what permissions you define for the guest user, the guest user will be able to access your U-Track, like your dashboards or your knowledge base or even your issues, if you find it reasonable.

Actually, this is how you provide this external space. So you see this is dashboards. I'm not logged in. And this dashboard can be used as a landing page for my users. And now I'm going to the knowledge base.

It's also open to anonymous access. So I see lots of information. Probably that's not what you should open externally. But.

As I said, it all depends on the permissions granted to the guest user. Yeah, so this is how your external users can access your knowledge base, your public knowledge base. Let me see if we have our announcement. Yeah, public knowledge base.

Yeah, you see. So this is kind of a public knowledge base that external users can access and get their... the answers even without logging in. Speaking about licenses, the guest account consumes one license slot but each user can use this guest account to see this information.

So if the guest account is unblocked then it takes only one license slot from you and anyone can access the information. If you want users to, if you want to, well, you will, in this case, you will not be able to identify your users because they all access your U-Track via guest account. If you want to identify them, then each of users should have their own account and consumer license swap. Yeah. And we can go to, there is also a question about exporting timesheet.

Okay. Yeah, I'll take it. Is it possible to export timesheet via REST API? This endpoint is not public, maybe yet, so it's not documented, but it is possible to export timesheet reports into a CSV file and then you can proceed with it further and log in.

Now we need to log in. Yeah, so I think that's the answer. Most of our reports have an option to be exported into CSV or I should have some, yeah I do. Most of our reports have an option to be exported as CSV file or excel file. So you can use it to export reports and to process the data further.

And we can move to the next question. Great, yeah, we've got one about the SonarQube. Are we having any integration with it for the static, the tool for the static code analysis?

To be honest, this is not something that's on table right now. And that's why I'm actually... we would appreciate if you could stop by our public task tracking that I mentioned, utrack.jetbrains.com and just file a post for us, a feature request, so we could better understand what is expected from the integration.

And just by the way, You probably didn't know about that, but JetBrains is quite recently started to work on the code quality platform for one of your favorite CIs. It's called Kadana. You can check it out on the JetBrains.com slash Kadana. I will post the link here in comments. And yeah, it's actually...

works the way that it's evaluating the integrity of the code that you have and enrich your CI-CD pipelines with some of the popular features that many teams need. Yeah, that's about the integration of SolowQ. Yeah, the next question was about the help desk.

If we have a plan on... keeping in mind solution companies with multiple partners and multiple SLE levels when designing this feature. Do you want to answer or should I take it? Yeah, I can actually.

The short answer is yes, they do. This is actually the scenario we are working on and try to cover. For now, actually the timesheets also is part of this process because we are having in mind teams that are working with multiple partners and do some external services to various counterparts in their work and the same thing with Helpdesk.

We will cover the multiple levels for you to be able to support. several flows of incoming requests. So you can have several helpdesk projects and you can configure each project separately on the project level with all the possible configurations available separately for your various helpdesk scenarios. Yeah. Thank you.

The next one is will you join the tables with you? For example, when clicking on issues so you can have the light version view in the pro version. We actually we are working to bring these two interfaces together.

Yeah, so we're trying to track your request too to make sure that as a result will bring the best. possible experience for our users and take like the best from both versions. The next one is how to add a tag to issue while subtask was added. That's actually a perfect use case for workflows. So yeah, I think I'm not sure I will let's try i'm not sure it can be created with a workflow constructor but let's see uh so our use case is that if um if a subtask was added we need to tag an issue well i'm not sure we'll be able to to check the subtasks but i will show you um a simpler use case um that covers when just an issue was created uh if you created, you should create it, new, yeah, new issue created.

Yeah, when I say that it's not possible to do with the workflow constructor, it only means that it is possible to do with the JavaScript editor. So the total use case is totally, the use case is totally possible, and you can create it. But right now, for the sake of the simplicity, I will show you a simpler case.

When a new issue is added, we will tag it. with, let's use the tag mailbox, yeah, and that would be the marketing project and the name tag an issue. Okay, I hope I have this tag. Let's see how it works. A new issue and I need marketing project.

Check the tag and create this issue. and you see the mailbox tag is added right away. So it was like the simplest automation that can be created like in one minute and of course you can enhance and expand it if you need.

So for example you can assign it automatically to someone or you can check the linked issues like a subtask that was the initial use case and tag issues that have subtasks. Yeah, now we're going to the next question. Yeah, maybe the next one is... Yeah, I will have a couple of next ones because they are relatively easy.

About the Gantt chart, the question is to support, to change the coloring of the issues on the Gantt chart based on the SIE, for example. Actually, for now, the Gantt chart color scheme is based on the time estimation, so you visually see the difference between... the overdue tasks and tasks that are still good to go and still run as planned. So yeah, this is a perfect case for the feature request again on our public tracker utrack.jetbrains.com.

So if you see how it could be helpful for your team, please describe us, trust your scenario so we can see if it's something worth to explore. Thank you. One more of the same kind, but with a little bit different answer. So the question is, will Utrecht Lite ever support Commons?

Yeah, like Anastasia said, we are working on bringing these two experiences of Utrecht Lite and Classic more closer together. So the Utrecht Lite will support Commons. We are actually working on it and planning to release it early in 2023, I hope. And yeah, and one more.

I can start it if you have anything to add, please, please, please help me. So the question is how to use custom queries for swim lanes. The answer is also short. It's not possible yet, but there is a feature request.

So we actually would like to know the demand for it. So please vote for it. We'll post the link in the comments. Please follow it. Yeah, I have a small addition here, if you don't mind, that it is possible to define swim lanes by tags and that provides you a more agile approach because you can mark any issue with a tag and then swim lanes defined by tags will contain issues marked with this tag.

So it's not custom queries of course, where it's something because you can You can configure your processes or automations so that issues that don't have something in common can be defined by a field. They will be united by a tag and you will display them on the board using this tag division. That's it. Oh, yeah.

And the next question is... Next? Yeah, go on.

Go ahead, please. About the user management. Oh, yeah.

We also have a question. Yeah. For the on-premise installation of U-Track, is there a possibility to integrate a third-party user management?

For example, firing off identity management. Yes, it is. Generally, it is possible.

Can I please have my screen back? I will show you what we have here. So currently you can configure authentication via several providers and this is the full list that you can see. So for example if you use Active Directory you can configure your YouTrack so that your users can log in to YouTrack using their Active Directory credentials.

The same goes to Google, Azure AD, I don't know, GitHub, Bitbucket. Yeah. And yeah, we support all 2.0 and XAML and other protocols. Yeah. And there was also a question that it would be nice to have a top of column and bottom of column function on the Kanban board in order to prevent long drag and drops.

Yeah, that's actually a nice feature request. Thank you. We'll share it with the design team, with our UX team to consider. Sure. The next one is, yep, I can answer also.

Do you have an integration with Terola? Yep. The answer is also short, not at the moment. And actually, we're working on the flexibility for agile wars in utrecht to add even more flexibility there uh so um yeah for for the travel we are only considering um to uh to add more automation to import from there and there is a feature request and we will be working on that for sure yeah i promised it could it would be short the next one is the texture yeah next one is the Utrecht Sharp library for integration with Utrecht from C-sharp actively developed and supported? Well, we consider this library more or less feature complete, so we can't say it's actively developed, but we for sure we provide all maintenance and support that is needed for it.

So if you have any questions, please feel free to contact us. The next question is, let's say you have two epics having a few issues. For the backlog, the top will be a mix from these two epics. How can I see backlog respecting the order and still see what epic each issue is part of?

Well, that's a tough one. Well, I guess having a tree view in backlog will not happen. how because it will not maintain the custom order rate i guess that the solution well it may not be the the the beautiful one but you can mark issues with a tag and this stack will uh relate to the epic to the parent topic of this issue so when you will have a list uh about your backlog which is ordered each issue will have a tag that says what etiquette relates to.

Well, that's kind of a solution, I think, because I cannot come up with it. Sorry? Yeah, I mean, it's a resolution.

And I also wanted to add that this is exactly one of the type of the questions when I mentioned that we are going to work on expanding the planning and support for planning boards and planning and resource management functionality. It's kind of related in terms of how we see the implementation. Yeah, but we're going to explore those scenarios and thank you for the example.

We probably can cover it in the future of MAP. Yeah, thank you. The next question is how can you separate tasks, internal only access and external access?

And give access to external users who are outside of company only to those set for external access? I assume group access. Yeah, so the question is that you want to open several issues of your project for external access, but you don't want the external users to see all issues of your project.

Well, generally, you can configure the project settings. Yeah, so first of all, there are several parts of my answer. First of all, there is a setting that controls the default visibility of issues in your project. So by default, issues are visible to everyone who has permissions to see issues in that project.

But you can narrow it down to, for example, your team. Let it be, I don't know. marketing team. Yeah, right.

That's not very smart since it's a web development project. I'm sorry, I'll change it. Yeah, now it is smart.

So now issues in the web development project will be restricted to the web development team. And what we can do next is... Let me show you how it works. So it's web development... um let it be external issue right um Okay, it doesn't work for some reason.

Okay, let it let do it manually. So if we if we limit the visibility of an issue to to the team now External users will not be able to access it even if they have permissions to view issues in this project So this is the approach you can follow you can limit the visibility of issues in your project to your team or for example to your company and then you can manually add separate users like external users or the guest user to this issue to open it to external access. And also once we have the extended help desk functionality there will be like more distinguished support for internal and public visible projects and issues so I think it will it will become more transparent in the nearest future.

Yes, hopefully. And there are a lot of good words from you folks. Thank you for watching, thank you for those thank yous.

There's always this part of the questions as well, and the feedback is also very much important for us, and this is the part that I appreciate the most actually. And thank you on behalf of the whole team for watching and for... for using them for helping us develop the product with all your feature requests and feedback and everything.

Yeah, that is greatly appreciated. We actually feel your support. Thank you.

Yeah, thank you very much for your kind words. Yeah, and also there is a question, when do we expect the next update of uTrack? Well, since we provided a major release like one week ago, I'm not sure if you checked it yet, but please feel free to check. There is a plenty of new features released and I think the next one can be the next major release can be expected in Q1 of the next year, right? We hope for it.

Yes. Yeah. But we also try to, you know, to release minor updates like once in a couple of weeks so that you don't have to wait for for small updates for too long. Oh yeah, one more question. Can someone without access to a project, not a guest, create issues for another project?

Yeah, sure. Actually, the create issue permission works on a per project basis. So you can say that, for example, this user can create issues in project X but cannot create issues in project Y.

Yeah, so project A, project B. Yeah, sorry, I'm lost with the letters. So yeah, I can show you a basic overview of how permissions work.

So basically how access management works in YouTrack. We have a long list of permissions, they are very granular. and they define what a user can do. So, for example, this permissions control, the user can read article or create group or read issue or update issue, and you can combine these permissions into sets, and we call this sets roles.

So you can create custom roles. Of course, we provide a set of default ones. And you can create your custom roles to define the level of access that you need.

And then you can grant these roles to users or groups, either per project or globally. If you grant a role per project, then permissions that work on a per project basis, they will grant this level of access only in the project where this role was granted. And if you grant a role globally, then a user will be able to do all this stuff like in all projects.

So yes, it is possible to allow a user to read issues only in one project or only in two projects or create issues in one project but read issues in a second project. Yeah, that's it. Exactly, exactly. And right in time.

So yeah, we've done with all the questions. That's not it. If you ever have some more questions for us, please feel free to post them in the comments or reach out to us in the support ticket or via email we've shown you today on the slide and we will add it in the comments to this video. Again, thank you for watching. Have a nice experience with Utrecht.

Great amount of success with your projects. Yeah, have a nice day and thank you for joining us today.

Transcript for:YouTrack Demo Overview and Features

Transcript for:
YouTrack Demo Overview and Features