Jira Data Center® Quick Start: Master the Basics in 1 Hour

1. 1.1 Introduction to Jira Data Center: And welcome to the course. I'm thrilled to have you here. Right now, you are looking at my screen showing the Jira Data Center system debt. I'm just going to move my mouse around slightly so we can see you're alive. But before we click a single button, I need to address elephant in the room, what is Jira Data Center and why we are looking on it instead of Jira Cloud. If you have worked in QA or Development recently, you're probably familiar with Jira Cloud. It is Atlassian primary product. Jira Cloud, Atlassian hosts everything. They manage the servers, they handle the security, and they push updates whenever they want. Convenient like renting an apartment. But what if we are massive game studio protecting unreleased source code? What if you are a global bank with strict data compliance laws? Renting an apartment is not secure enough. You need to own the billion. That is what Jira Data Center is. It is the enterprise grade, self hosted version of Jira. Your company installs it on its own servers or Private Cloud. You control the data entirely. You decide exactly when updates happen, and most importantly, it is built for a massive scale capable of handling tens of thousands of users simultaneously without any crashes. So whether you're a complete beginner, looking to start your career or Jira Cloud better run, moving into an enterprise corporate environment, this course is for you. You are going to master heavy duty version of Jira. Let's take a look around. 2. Understanding Issue Types: Now that we know our way around the dashboard, let's learn the current terminology of Jira by jumping into actual workspace. I'll go ahead and click Projects, top down on the top bar and select our example project in the list. In VIA, a project is simply a container. It is a dedicated folder where a specific team organizes all their work. Over here on the left, I'm hovering over the project side bar. This allows you to navigate inside this specific project. You have your backlog for planning and your words for visual tracking. Side this project container, we have the actual work. In Jira, every single piece of work is called an issue. Let's look at the main list here in the center. Notice Hi MacrosursHing or the letters, X 12, 11, nine, is the project key because we are in the example project, every single issue, create a here automatically get the X prefix. This numbering system ensures you never lose track of a bug, but not all issues are the same as a hover over small icons. Next to the issue keys like this red square or blue keyboard, we are looking at issue types. Depending on what your team needs, an issue can be a bug that needs fixing a task that needs doing or a story representing a new feature data center allows us to create entirely custom issue types, which is perfect for specialized QA and deep teams. To summarize, I will put my mouse back to the top right gear icon. Users do the work. They do it inside projects. The work itself is broken down into issues, and everything is tied together by invisible rules called chimes, energy right here in administration. Now that we speak the language, let's move the Model two, where we will learn how to build and install the entire system from absolute scratch. 3. Downloading the Software and Initial Setup: Come to Section two. To master Jira data center, we need to build it from the ground up. Exactly how Enterprise ADT would do it. Jira's fundamental Java application. In a two professional environment, administrators install and manage S Java development kit SGDK separately to ensure maximum performance. I will share the link with you in description to this lesson, and you need to open the Oraco website and see exactly the same page with archived on loads. What you should do, you should scroll a bit down and find your operational system. Mine is Windows and download the Installer. When you will download Installer, I suggest you to create three folders, Java 17, Jira App, and Jira Home. Java 17 is needed to have everything on one drive to have Jira work properly, to find it and to see it. And Jira App and Jira Home, I will describe later in the next lessons. Basically when you will download, simply launch Installer. You will see such Window Setup Wizard, you press Next, you press change, and you need to find your preferred drive where three folders was created. And here you should create new folder, name it ra 17, press K, verify it. It is gra 17, press next, and it will install it right here, as you can see, all the files are here. So we did successful installation of DDK, which is the foundation of our Jira server. In the next asson we're going to build the vault where our database. 4. Database Creation and Configuration: Come back. A massive enterprise application needs a high performance relational database. The absolute gold standard for this and adolescents top recommendation is post gree SQL. I will share with you this link. This is official link on the load of Postgre SQL. We need to download version 16.13, this one. The same as GDK, select your operational system, click on the load. Once the executable is downloaded, simply launch it. It will take a bit of time to properly launch. Like a few seconds, then proceed. Select the desired installation directory. We can stick to our volume, create here folder, name it, database, select next. Everything is okay here. Next, data directory data, this is fine. Password. Enter some password here and please note it down, not to forget. Next port, keep the same. Okay, Okay, Okay. Install. Give it a while to install properly, and then we will run the application. Now when installation is complete, let's type and search and find PG admin form. This is our database application in which we will create our database for Jira. You need to expand servers, find first degree skill, expand it. Enter the password which you created, and in databases, you need to create database, type here Jira database, and save. Here we go. We have our database, which is named Jira database and which will be connected to our Jira instance which we will install in the next lesson. 5. Step-by-Step Data Center Installation: Have Java and we have our database. Now it is time for the main event. Let's get back to the browser and use the link I shared with you under this lesson in description. This is our Tira data center, download Archives. Here, select any kind of that. It doesn't matter. Simply press, download, select your Presion system. Agree, submit, and download. We'll start. You will download, you will see Atlas Jira software executable here and simply started. It will prepare installation. Yes, next here, select Custom Install and here, select your volume where you created three folders, and first of all, select Jira app folder. Next, during this step, select Jira Home folder. By two because this is enterprise best practice. The installation directory is where the application code leaves the software engine, and the home directory is where all your attachments, log files, and search indexes are stored. The engine separate from cargo is how administrators ensure the system stays first during upgrades. So once we dedicated them, let's press next. Let's press next. If you will notice such kind of message, simply the name to Samson else, it is just a group in your Windows main menu. Use default ports, press low and install. Once it finishes, I will make sure to select star Jira software now and we will finish with installation hero like it looks Next, and our children should be launched in a few seconds. Keep this tick and finish. As you can see, everything is setup. Right now, we have local host AT 80. We have our first initial setup page, something working in the ground. So let's fill this out in the next lesson. 6. Finalizing Data Center System Setup: Welcome to the final step. In the local host page from the previous lesson, we see database setup window. We have here database type, host name, port usertain and passwords. I'm going to click this two down and select Pos gree SQL, which we already installed for the host name local host as it suggest me here, words should be remained the same, then the base. Jira database as we created in Postgre, then use your post green and user name and password. We had there postgress and password, which you created for the Jira database. Schema is public, the test connection. If you see the green message, then we proceed, press next. Now Jira works with the Postgres q to create database to fill all required fields, and this meta can be. Now it asks us application title, the mode, and the best UL. This is actually fine, so we press next, and now it asks us about license key. To have a license key for 30 days, you need to navigate to my atlaen.com. Also share this direct link. You need to log in using any kind of method. Then you need to click New Trial license, select product Jira and Jira Data Center. Then romanization, type anything you would like here, something like test, then server ID, you copy from here to here and press generate license. Here is your license scheme which you should put here and press next. Now it should configure your license and show you your first page in Jira Data Center. Finally, Jira asks us to set up administrator account. Just put your full name, mail address, create some user name, some password for this, and press next. You can set up a mail notifications if you would like, but you can press also later. Here we are. We are in the system report. We are finishing our preparations, and I suggest you not to create a blank project, but you preloaded with some simple data. It will be easier for us to navigate through the course. So press Create sample project, select Scrum software development, press next, type name for it, something like example project, and the key for it will be x like example project, or we can name it like mobile app development, something like this. And the key for this should be should actually automatically use the prefix of your name. For me, it doesn't work for some reason, but it will be like MA or MAD or something. But to make things consistent, I suggest you to use example project name and the key X then submit, and we are into our hier data center system. Regulations. You have successfully installed, configured, and even licensed enterprise grade Jira Data Center instance from absolute scratch. Now take a breath. In the next section, we're going to transition into choose a daily user and explore how Q engineer or developer actually interacts with this system. 7. Comprehensive Issue Breakdown: Welcome to the Section three. Before we start configuring enterprise schemes, we need to know how to simply survive at Tuesday morning in Jira. If you are a QA tester or a developer, your entire day revolves around the G ratio. Let's learn basically how to read one. I'm going to start here on our system board. I will move my cursor to the top navigation bar and click issues drop down and select one of the recent issues. The ticket opens, it can look like a wall of text. But let's break it down into three logical sections. First is our details. We have the type, we have priority, affected versions, labels, sprint, and our status is like resolution and expression. The more important thing is our key, project key, and summary because summary is basically the title of the task. Just below everything is description where the product manager or tester explains the full scope of the problem. So it is our text, and at the right, we have the people. We have information, who is reporter, who is assigned we have something like votes, vouchers, and dates created, updated. Everything could be maintained and set in the layout. So the fields may vary and change project to project. We will look later how to set up this. 8. Collaboration Tools: Comments and Watchers: Come back. Jira is not just a filling cabinet four box. It is a communication platform. If you find a problem with a ticket, you communicate directly inside Jira. So, the entire company and all the people has permanent record of the conversation. I'm still here on X 17 ticket, and I'm going to scroll down past description to the activity section at the bottom. This is where the collaboration happens. Click into add a command box, and now if I will type something like B, it will be added to the ticket, but nobody gets an alert. To force Jira to send an email notification to specific person, use a mention. I'm going to type mention symbol, pick from drop down a person. I only have myself, so I will pick myself. And after you finish typing your message, something, something, click at and this will send a notification to this developer or QA or project manager or anyone. So he basically knows you need something from him or you updated something in this ticket or you have a question. Finally, let's take a look at the top right corner of the tickets under the people section we have here, watchers. If you are not the assignee and not the reporter, Jira will not notify you when this ticket updates. But if you click start watching this issue, Jira adds you to the notification list. You simply will watch the ticket, and you will now receive mail or notification into the Jira when someone leaves a comment or changes something in description or changes priority type or any kind of changes. 9. Tracking Productivity: Logging Work: And for the final lesson of Section three. We know how to read the ticket and we know how to talk to our team. Now it is time to actually do the work. Here on our X 17 ticket, I'm going to bring Microsoft to the top row of the buttons right under the title. This row represents the workflow. Currently, the ticket is in progress. I'm going to click the button that says in progress and change it to done, for example, or move it into do. By doing this, I'm broadcasting to the entire company that I have actually returned the ticket to Todo or finished it by making it done. This status immediately updates and notifies people that are watching the ticket. Now in a corporated enterprise environment, it is not enough to just finish a task. You often have to prove how much time you spent on it for capacity planning. We do this by login work. I will move my mouse over the right hand saver, click more button, and press log work. A new window appears. In the time spent box, I will type something like two H. This means 2 hours. You can log here like weeks, days, or hours. Actually, if you will type one week or 40 hours, this equals. For now, I will use 2 hours. I can also at a brief work description. Here like I did something. And then I will click Log. If we open W log, we see that developer locked some work with some description, and everyone, like project manager who is assigned on this ticket also sees that and understands the capacity and the velocity the project moves. This concludes our daily user basics. You now have the row of skills to navigate Jira. Starting in the next section, we are going to completely shift years. We're going to put on our administrator heads and learn how to build the enterprise architecture that controls everything we just learned. 10. Understanding Project Schemes: Come to the section for in the previous section, we looked at Jira from the perspective of daily user. We saw how to open a ticket, log over time, and click those workflow buttons at the top of the screen to move task to done. But how does Jira actually know which buttons to show you? How does it know that a bug should have different feels than user story? It is time to step behind the curtain and put on our administrators heads. If you're coming from Jira Cloud, you might be used team managing projects where anyone can change their own worklo. Jira Data Center does not allow that level of chaos. In Data Center, everything is highly standardized using shared schemes. Let me show you exactly what I mean. I'm starting right here on our system board. I'm going to click on the projects, drop down, select our example project. Once the board loads, I will follow my cursor all the way down to the left hand projects at bar to the very bottom, and click the gear icon here project settings. Took at this summary page. As I slowly scroll down, you want to notice a specific word that appears everywhere on the left side. Scheme have an issue type scheme. We have workflow scheme, screen scheme, and permission scheme. In Jira Data Center, a scheme is Master rulebook created by system administrator instead of every single project having its own unique isolated rules. The admin creates one enterprise software scheme and applies it to 100 different projects at once. If your team decides to add a new mandatory testing step to the workflow, the admin doesn't have to edit 100 projects manually. They change master scheme once and all 100 projects update instantly. This tri currents enforces compliance and keeps the base lighting fast. In the next lesson, we're going to see the strictness in action by adding a custom field to the tickets we explored. 11. Adding Custom Fields to Schemes: Previous section, when we looked at the right hand panel of our ticket, we saw standard fields like priority and Assignee. But what if we need to capture something completely unique to our company? Imagine you're testing our example project software. When you lock it bo, you need to tell the developers exactly what device you are using. We need a custom drop down field code device type. Jira Cloud, you might just open a ticket and drag a new field onto the screen. But in Jira Data Center, use the screen scheme engine. It prevents massive database pload by ensuring fields only appear exactly when and where they are needed. I'm going to move a cussor to the top right corner on the screen, click the global Keer icon to open ministration menu and select issues. This takes us to the administrator axis. Screen. Enter your password, and we're here. On the left side bar under the fields. Section, let's click on custom fields. Now I will go to the top right and click the at custom field. Butt. Jira gives us a massive list of field types. Since we want a simple drop down, I will select select List, single choice. Select list, single choice. Let's name it as we zire device. List or device type down in the option box. Type AS, type Android, and press next. Select create if you want your issues to apply in selected projects or to all issues. Actually, select example project. Great. Now we have our custom device type field. It was successfully created. After we have successfully created our device type, navigate to schemes, find your default scheme or bug screen scheme, open it. Now you will see all the fields that are applicable for bug and make sure device type is turned on here. To verify, let's get back to our X 17 bug, and in details, we see device type. Now we can select the types we entered on the step before. And basically what's the reason we do such things is separation. By strictly separating the field from the screen, Jira data center ensures that your tickets never turn into cluttered mess of 50 relevant fields. You only see exactly what you need and exactly when you need. By applying it to box screen, this device list will appear only on issues with Type bug, but type story or type task will not contain it. If you need to separate, for example, some fields from QA and developers or Project Management or some product owners, you need to it screen schemes, adding the rules to each one separately. 12. Linking Related Issues for Better Traceability: To the final lesson of Section four. We have explored our project structure and our custom screens now capturing the right data, but enterprise work never happens in isolation. If you are a Q tester and you find a critical bug, simply clicking Create is only half the job. You need to mathematically reflect this bug is actively stopping a new feature from being released, we do this through issue Link. Let's the get to create button. Let's make sure that our project is a example project and issue type is back. Type summary like minu crashes in on load. Let's say, good. Now, scroll down a bit, find the linkit issues. We have here a lot of them like blocks or blocked by another issue, clones, some issue or is cloned by another duplicates and relates to a lot of types of relationships. But mostly QAus duplicates if they found some duplicated issue or blocks, some task example, we don't have tasks here or probably let's find some. Okay, we don't have tasks for now created. Let's block some user story and press create. So as you can see, we linked our user story, or it could be task, for example, which means that this bug is blocking some tasks from being done. Doing such things, we are tying this bug to the feature. In enterprise environment, release managers use the specific block links to run automated reports. If software release has even one unresolved blocking link, attached to it, the system knows that software is absolutely not safe to launch. This concludes model four, we have successfully transitioned from daily users to project architects. In the next section, we are going to take a step further and learn how to manage thousands of these tickets at once using bulk operations and advanced to close. 13. Configuring Simplified Workflow Schemes: Come to Section five. In a small Jira Cloud environment. Moving a ticket from to do to done is usually just a simple dragon draw. But in enterprise Data Center environment, we don't want people dragging tickets whenever they please. We need strict processes, and we need workflows, I'm going to start here in our example project. I will move Microsoft down to the left side bar and click on project settings. Then I will click on Workflows right here. This brings us to the For close chem page. You can see that we are currently using the software simplified for closed Kim. I'm going to bring my mouse over to the right side under actions and click this small pencil icon. This opens the visual workflow designer. It might look a bit intimidating, but at first, it's actually just a flow chart. Notice how I hover over these solid boxes to progress and done, these are statuses. This is where the ticket currently is. And now look at the lines and arrows connecting them. Notice how the arrows have a small gray page that says, A. This is a global transition because this is a simplified defaulting plate. Jira is currently allowing a user to move a ticket from any status to any other status. But in a strict enterprise environment, don't want all. We want a strict linear pass. If you delete those all transitions and draw a single arrow directly from to do to in progress, the system will literally block user from skipping steps. Let's try. Let's click on todo, delete transition, and then move to in progress. Let's name this one as to do slash in progress in progress. That creates for us a new line with a name of it to understand what happens actually. It's also remove transition progress. Deer data center goes even deeper. If I click on one of these transition arrows, for example, you can see the menu that appears on the right. I'm hovering over the conditions, validators and post functions. These three are the whole grail of enterprise QA. By clicking validators, an administrator can enforce a rule that says a developer, for example, cannot click the transition to done unless they attach a screenshot or the fixed code. If they try Jira throws a red error screen, where flows ensure your team cannot cheat the system. Lesson, we're going to look at what happens when you need to bypass individual tickets and manage data at Messer scale using bulk changes. 14. Efficiency at Scale: Performing Bulk Changes: Come back. Imagine a scenario. A Edveloper leaves you a massive software studio. They have 250 open box tickets, assign it to them. Are you doing to open 250 browser tabs and reassign them one by one? I think you will not do that. In Jira Data Center, we use the bulk change too. I'm going to bring my mouse up to the issue strop down and select search for issues. This brings us to the issue navigator. I'm going to run a quick search. Let's click the assignee button and select, for example, user that you have me. And then let's set resolution to do, for example. We have our list of tickets for on them. Let's navigate to the top right to the tools. Here you can see bulk change option, which will apply all four issues. Let's click it. First, I will check this Msterox at the very top to select every single issue on the page and then click next. Step two asks what you actually want to do. Let's select Edit issues and click next. Here in that huge list, you select what you exactly want to change. The change priority, fixed versions, affect version, SIE or any kind of another label that you have in your tickets. For example, I will change priority, and for example, I will change an environment. Obviously I will set here on Mac OS. Then I press next. This is our confirmation screen. Here we press confirm, and operation starts. Now it is done. Let's check each of that issue has highest priority and environment is set to MacOS. So this bulk change is your superpower. It allows you to manage thousands of tickets in seconds. You simply select the issues you need to change by using filters, you receive a big list of them. For example, 100 issues in your sprint, which is ending, you need, for example, to set priority to change priority or to set some label, extra label or change environment or change sprint, for example, for 100 issues. You simply navigate to your search, you find these issues, create a list of them, use bulk change, and like we did, change the fields you need on the results you need, and in seconds or minutes, if you have a load, everything will be changed to your desired result. In our next lesson, we will look at how to hide tensity data using issue security. 15. Implementing Issue Security Levels: Welcome to the final lesson of Section five. In a large corporation, not everyone should see everything. What if your HR project contains salary requests? What if your software project has tickets detailing a massive unannounced feature spoiler, or if a standard user searches the project, they will see it. We need to those specific tickets down. Jira Data Center, we use issue security levels. Here in project settings, we have a tab, which is named issue security. As you can see on the screen right now, it says that issue security is currently not enabled for this project. In Jira Cloud, hiding tickets can sometimes be quick toggle, but in Data Center, we have to build a master template first. Let's try. Under the actions, we should click Select a scheme and click to add a new security scheme at issue security, and here, let's type something ip only. And now we have an empty scheme, but we need to create actual security level inside of it. Let's click on security levels action, and let's add here, for example, only for Admins. Now we have our security level, which will be available only for Admins administrators of that genre, and we need to assign the proper person or people. Right here, we can click Edit and find here user management. Assign a proper person, you need to click then select for example group, Jira system administrators or Tira administrators, for example, or we can give the t to single user. But for example, if we say that this filter will be only for admins, let's touch everyone who is Jira administrator press. Here we go. We have security level only for Admins, which will actually be only for administrators. Now let's actually attach those VAP only filter for the project. We need to return back to issue security under the project settings. Link action, select the scheme, and under Associate issue security scheme to project, select our created VP only. Then click Associate. In a few seconds, it will apply this security scheme to our project, and now we have it for our administrators, and this means that our project is locked down. This one is in the press vault, ensuring your most sensitive data never leaks across the company. So basically, if you have 1,000 users under your data center, Jira, and some of them like developers, UAS finance team, they will be under their group, for example, Jira users and Tdministration team of data center or of company, I would say, they will be assigned to Jira administrators, and then administrators of the project can set up visibility things for some tickets for some reports or other things. And Jira users will not see such reports at all. Like here, for example, we have our current project, and someone simply will not see this project and we will be able to even open it. This concludes Section five. We have learned to manipulate and secure mass amounts of data. In the next one, we're going to look at how to structure our case organizing our projects technically and chronologically. I will see you there. 16. Organizing Projects with Components: Welcome to the Section six. As your zero project grows, it will accumulate thousands of tickets. If you just dump them all into one massive backlog, your team will spend hours just trying to find that to work on. We need to slice the project into logical pieces. We do this using components. Here, under components section in the left side bar, the last button. Can create a component which will make default SNE on, for example, bugs with selected component. Let's try that out. For example, I type here front end component. I select developer that, for example, that works under the front end. Description is optional. If you need a default SNE, we put component lead, which will automatically select person who you select. Then you press d, we have created the component front end. Then, for example, when your QA or project manager or anyone in your project will create a bug, for example, which is something tent related, and related, and select component from tent and prescript, the SNE will be exact the same person automatically, which we set under this component rule. Basically, you can create a lot of components, for example, one for front end, another one for back end, a third one for logic manager, a fourth or any other kind of. For example, in am development, we have a lot of components like level art, level design, server issues, online issues, any kind of PC related issues, hardware issues. And if you know that we have exact person who will deal with online issues or only with art issues, we can create such kind of small automation, assign that person, and never look at assignee button. Of course we can scroll down a bit and type here the name of developer or select him from a list. But why should we do that if we have a mass amount of tickets and we just spend ten or 12 or whatever seconds for ANE, if we can type some summary and then right after that select component, which will automatically select a person for you. I think that is a great time saving thing and convenient for everyone to create tickets. 17. Managing Timelines and Version Releases: The last lesson, we used components to organize our work by technical area. But what if we want to organize our work by time? When stakeholders ask, what exactly is going into the next patch update? They don't care about Bend versus front end. They care about the release. To track this, we use fixed versions. I'm going to move my cursor to the project sidebar and click on releases. Here we have a few versions, template versions, but let's create a new one. Let's go here and type, for example, version. We don't have Version one point. Let's have version 1.0. Okay, let's have 4.0. This actually doesn't matter. Let's have here release date, for example, 16th, April and preset. So for the version four, we have release date, 16 April of 2026. Now we have a bucket for our release. Let's get back to our backlog. Block. And let's select, for example, this bog. And let's go down P two fixed versions and select here our version one. Now we should have the real time progress bar. We need to return back to our releases, and here should be the progress. Actually, I think here we don't have anything right now because of the issue which I selected, which is not probably yet done. Let's make it done, for example, and let's set already done issue, the same version one, press ak, and let's change one issue two in progress and also set here version one. Version one green tea. Let's turn to releases. Oh, I'm sorry. I'm so sorry. We should click version four, but I'm using Version one. Let's change to version four, here, and for example, here, version four, which we have, for example, Version four here. Let's get back to releases. Yes, now we have progress, and we see that we have three issues in total. One is in progress and two is two are in to do. And simply manager when we open the release tab, he will see all the versions of a software and release dates. Example, for example, he plans, releases three months in advance. He created version one, two, three, four, and then managing the tickets, he set for some of them version four, some of them version three, some of them version two. And upon the completion, developers or quas or even that manager will change statuses to done or in progress or return back into do, and he will not be needed to open backlog and to navigate each task, clicking each task to understand what happens with it. Does it happens to appear in another version. Simply opens, releases and sees the progress of such release. 18. Project Lifecycle: Archiving Inactive Projects: Welcome to the final lesson of Section six. I want to end this section by showing you a feature that is absolutely exclusive to Jira Data Center. If your company has used Jira for years, you probably have millions of closed tickets and hundreds of debt projects. In standard Jira versions, all the dead weight is in the active database. It makes searches painfully slow. You can't just delete them because enterprise companies need to keep historical records. The solution, Data Center archiving. I'm going to move my mouse to the top right corner and click the global and select projects. This is our global project list for administrators. For example, let's find not completed project in this list. We don't have such but let's pretend our example project is outdated one and we know more needed. Here under Actions, we have three dots and click them, and here we can archive that project. When administrator clicks this ira physically removed project from active search to it just hides it. It disappears from all drop down menus we have. I will disappear from here from issues, from bords and other things that are related to example projects. But the data is not gone. If an auditor even needs to see it, administrator can simply c restore, and the project comes right back. So this one is completely different to Jira Cloud. And if your company needs to hide a lot of that projects, it's better to use Jira Data Center and simply archive unneeded ones, and to have possibility to restore in case of N. This wrap ups a Section six. We have fully structured our enterprise workspace. In the Section seven, we're going to learn how to extract all these data by mastering Jira query language, that's met there. 19. Fundamentals of JQL (Jira Query Language): Welcome to the Section seven. Up until now, we have been using Jira, basic interface to find our work. But if you want to be true Jira professional, you cannot rely on simple drop down menus. You need to speak Jira native language, JQL or Jira Query Language. Here we are run the system dashboard. I'm going to move my mouse up to the issues, drop down in the top navigation bar and select search for issues. By default, the issue navigator shows us these basic drop down filters but I'm going to move my mouse over the right and click this button on the Say switch to JQL under the advanced. The screen changes, and now we have a command line. This is where the magic happens. A JQL query has three simple parts a field, an operator, and a value. Say we're testing our example project and they want to find all the box from it. Simply click on the search bar and type project, equals example project, and issue type equals B, the press search, and notice how Jira have to complete your list of box automatically. Instantly the list updates for you. So here, the project is our field, equals is our operator. Example project is our value representing our example project. And the word is a keyword that strings multiple rules together. And also as you. So when I was typing something, here it is autocomplete of your fields and operators and values. You just need to know what you're looking for. You can easily find box with component that equals content, which we created recently, Fine search, and you will receive only one ticket which has front end components. A data center instance with millions of tickets, JQL is the only way to surgically extract the exact data i. In the next lesson, they're going to look at advanced operators that will make you look like cheer wizard. 20. Advanced Queries for Power Users: Imagine you're testing a new software built. Developer tells you they fixed the critical back end pack yesterday, but today, the buck is back. You suspect someone secretly reopened the ticket, but the current status, says just open. How do you prove it? Standard basic search cannot do this, but our Jira Query Language has a time travel operator called Vos. I'm going to delete the previous query and type this into search bar. Project equals our current project, and status was a and stat use example equals to do. Here we go. This query acts like detective. It asks Jira Data Center to search the historical database logs and find any ticket that used to be completely finished but has somehow been moved back to the Open the log. Let's look at the history as we can see it was done, but 2 minutes ago, it was moved into do again, which basically means that our query works and it finds us the lick that was done already before, and now its status is to do. So it returned from completed tickets to uncompleted. Let's look at another power move, dynamic functions. If you want to see box, assign it to you that were created today, you don't type your name in today's exact date. I will create the field and type athE equals current user or you can select your just name and surname then and create it more or equals, for example, third of day search. There are two tickets. By using current user, I can share this exact query with my entire queer team or Def team or Project manager team, and it will dynamically adapt to leaks it. Start today means that today, actually, all the things to show all the things created today or change today. And as you can see, we see here two tickets which was created today 25. Ago, this one, 23 minutes ago. This one, it works, and it helps you to sort out thousands or billions or whatever amount of tickets to find exactly what you need. And now that we know how to write these powerful queries, let's try to save them. Let's do that in another lesson. 21. Creating and Managing Filters: To the final lesson of Section seven. We just wrote a brilliant query to find our actual box for the example project, but we don't want to type this out every single morning. We need to save it and reuse. I will clear the bar once again and type again project equals example project. And for example, let's find issue types that equals BC and status of it equals, for example, in progress. We have one of such type, and now I want to save it. Here we have safes. We need to type some filter name. I suggest you to keep naming simple. Actually, B in progress or box in progress filter. Here you can see it appear on the left side under this panel like your favorite filters. So you can switch to basic filters or select your safe filter and return back whenever you want or whatever you need. Now let's try something out. Here I will click on details on top of this page and see that there are also a few buttons that we haven't discovered yet. Here we can set textually permissions for this filter. This is a crucial data center concept. By default, your filter is private. But if you want to use this filter on Team dashboard, for example, or share it with somebody you must share it. You must set permissions to not the owner or editors. You simply click Edit permissions. You can add viewers, for example, those people who are assigned to project example project, and clicked. So now your filter is visible for everyone who is inside of the project. But the editor, for example, is no one except you. If you want to give rights to edit this filter for another que or another manager or anyone, you simply can select the user type here, the name of that user and press ad, and that user receives the same filter but he will open or like, yeah, you can press. You need to press Save. Then here on the page, this filter will appear for the person or people with whom you shared this ticket. And please remember that if you will change something here in Query, example, you will add another condition. For example, let's at Samson. If you will search, you will notice that your save button is now active, which means you need to save this filter each time you do the changes to the queria. This is important because there might be a situation when you look for something specific or you edit by situation. This filter, you type complex query, for example, to find some very, very old and I'm coming back and you just forget to press Save. I will reset to your previous one once you load your page or switch, for example, or Logo and log in or So remember us to save. All right. I think we have our saved optimized filters, and this basically concludes this section. In the next one, we're going to use all of that to build an enterprise great reporting dashboard. 22. Dashboard Basics and Layouts: Welcome to the Section eight. A gira expert doesn't just find data. They visualize it. In this lesson, we're going to build a common center. I'm going to move my mouse up to the top navigation bar and click the Dashboards down and select Managed dish boards. Here at right at the top right, you can see creating the word button. Let's click it. And let's give some name for our neuter let's type command center as I announced. Let's start from blending board and not share with everyone. Here we go. We have our new dashboard, which is currently blank. Over the right hand side, you can see add gadget and edit buttons. To have something visualized here, you need to add a new gadget. You simply click it from the initial start, you will only have two filters, but you can press load all gadgets and select from a lot of them. For example, let's start with assign it to me gadget, and example, let's add filter results. Here you can type the number of results you would like to have the more the better, but it should be not more than 50. You can select columns to display. If you need, for example, components to see or due date, you simply add this one and whether you need to refresh or not, please press a dig. Now you can see, we assign it to you issues, box, stories, tasks, tasks, and other things sort by type key, summary, priority components, and things you add. Also, you have here actions, you can simply do everything you can do with your ticket from dish board, which is super convenient or you can navigate to it or you have freedom of choice to them. But the main thing is visibility. You simply open your dashboard and you see assign it to you, for example, and let's use our recently created filter box in progress with number of results, 15, and let's keep it the same. Currently, we don't have issues in progress, which means that we need to add something. Let's create some in progress ticket in progress ticket. Let's set some priority to seal, let's set some. Label, new label, we will try to change it as N, and let's set our current sprint let's create it. Let's navigate to it first, change status in progress because we are hunting for in progress things and return back to airport. Here we see that our filter works and gather for us a box that are in progress actually related to the filter we created in the previous lesson, which means that you can right now navigate to your filters. You can create any filter you would like, any filter you need to help you speed up your job, then save them and create a board to easily visualize the things when you get back to work at morning, you simply open your dashboard and see what is assigned to you and in the same time, see the results from filters. It may be filter, for example, created, created today or created yesterday, for example, and you will not be needed to look through all the tickets on the board. You simply see them right here. The only one disadvantage is layout. You can have only two of them or maximum three columns. As you can see, you can dry out which one suits you better, the longer, the shorter or three small ones, but the space is pretty tight, so you can have only one, two or three columns to store your favorite things. 23. Sharing Dashboards with Your Team: Welcome back. Let's talk about the single most common mistake people make Jira boards. You spent an hour building the perfect rebard. It looks amazing. You copy the URL of it pasted into your team's chat and say, Hey, everyone, look at our new QA matrix rebotF example. 5 minutes later, your developers reply, the report is empty, it is broken. Why did this happen? It is all about data center permissions. I'm going to move my mouse to the top writers report screen and click these three dots and select shared their board. Here I can add permissions, so my whole team can use this page. It's basically the same we did with filters. If you need to share it with someone, you select project or anyone or log in user into your company or group, actually, which should have the access, you create a project terpress ad and after that, after you update your report, you can reply that everything is fixed. Right now. And now the developer will see your gadgets and non black actually blank dashboard and say, thank you for a great job. But also remember that if you have in your dashboard assigned filters which are not shared with your team, they still will not see them, not see the results here. For example, Box and Progress filter was shared with everyone. But for example, issues and Progress filter that you created recently is not shared with everyone. It is private, and share when you will share your dashboard with everyone, and they will open it, they will see only the left part of it. This one will be blank because of the privacy settings. So don't forget to set on filters and dashboard privacy settings, the possibility to watch for everyone in your group or specific people that you would like. 24. Data Visualization Techniques for Reporting: Welcome to the final lesson of Section eight. The reports are great for real time right now, data. But what if management wants to see historical trends? Are we actually getting better or are we just treading water? I'm going to move my mouth to the projects down and select our project. Then on the side of it, I will click on Reports, button right here. Look, look at this. Jira Data Center comes with a massive suite of build in HL reports that do require any custom Jira Query Language. Let's find created versus resolved issues report. Here it is. Let's click on it. Then let's keep the defaults, and here it is. The red line shows how many new bugs are being reported, and the green line shows how many box developers are actually fixing. If the red line is consistently higher than the green line, your clock is growing, you are mathematically losing the battle and the software is not ready to launch. Jira Data Center takes the emotion out project management. Gives you undeniable data. This concludes our section. We have visualized our data and analyzed our reports. In the next module, we're going to look at agile boards and how to manage a daily grint of Scrum and comb. 25. Advanced Agile Board Configuration: Welcome to the pection nine. Up until now, we have been looking at our data as a list of tickets or chart, but AGL teams live and breathe on visual air booards. If you use Jira Cloud, you probably use team managed boards, which are very simple. Jira data center uses heavily configurable HR boards, but there is a massive conceptual difference you might understand first. A board is not a project. Starting here inside of our example project, let's click on active sprints at left. Then let's click on Word button and select board settings or configure. In Data Center, board is simply a visual lens. It is a piece of glass looking at projects we say with to recovery language filter. If you can see, we have also a filter here, filter, for example, project board, which shows you our project ordered by running. Also we have here columns which we can edit. For example for now, we have to tune progress and and what if we need, for example, testing column? Now we have testing column, which is under in progress category, which means that while your ticket is under testing, it is still in progress. So if you need some column which will not be in progress or done, you can add a column, for example, named suggestions. And select to do. I actually should be not track tests in progress while doing reports, while doing some filters or other things. Then we have here swim lanes. As you can read here, it is a row on the board that can be used to group issues. So you can select from what you have here. Let's group, for example by projects. Then we have here the quick filters. Then we can adjust, for example, these filters are simple buttons, which will do some query without need of typing the query in advanced search. Then we have card colors, like when we assign the color to the card, they they will be different. And we can select, for example, color is based on issue types. And if we have black, color actually should be, I think, red. For sub task, it's okay, but for story, usually we have green color. Then we have card layout. For example, we can at component, we can add some resolution and other things. You cards will show up to three extra fields you select here. I will show you. Then you have estimation, we can change estimation statistic from story points to time estimate, for example, not to estimate points, but our regular time can change time setting and what else? Working days. We can set up here region, which will be accountable for all the issues across that project, across the board. Actually, BRT is not a project, as I said you. So this will be applicable for our board. But if you have one more board, for example, you can set up it with another region. For example, you are leading two different time zone projects, and you need to remember that you need to change the time to appear it correctly for everyone. Team. Also, if you have non standard working week, you can set it right here, and the count of different reports and statistics and estimates will be changed accordingly to your workdays. And the last step here is issue detail you. Here you can add or delete the fields you need or don't need, actually. So that's basically it. Let's back towards and see that as we have changed the colors, now we have slight blue and pretty green color. Which were different from the previous setting, and also we have here two more fields that are on the card, not inside of it previously to look at resolution and components was needed to open your kicket and find in the list. But now they are right on the ticket, and you can log here useful information for you. 26. Managing and Adding Plugins: Hello again. As part of Section ten, let's talk a bit about the marketplace and apps you can install. Jira is a phenomenal issue breaker, but if you are, for example, managing complex test cycles, SQA for the project, standard tickets are not always enough. You need some dedicated testing tools, or if you're a manager or some time logging tools that are not provided by atlas. You can do. You can click manage apps under the glopoting and we get to market place for Jira. Here you can see a lot of different plugins and tools that are actually most of them are free, but some provides trial, then you need to subscribe to them. But if your company can provide you some, let's say, tool that will speed up your testing process or managing process or development process, this can be example, if you are QA, you may be accustomed with Zephyr to you can find here in the press solution that will simply install our ira into your Jira, and it will create for you new should type named test case, and you can write step by step instructions directly inside the Jira ticket. Can group these tickets into test cycle to present regression pass of your software in opening a user story. Instead of just seeing the description, these plugins inject the new panel right into your ticket, showing every single test case, link it to the story and whether it's passed or failed, it is built. So it turns your Jira from issued tracer to centralized QA command center, and the same is applicable for another tools that are provided by marketplace. So calendar plugins to do better visualization, some time TrekerF zero data center, handlers and kit hop integrations. Basically, you can just navigate to marketplace and try each one that you might need to do better job. 27. Basics of Jira Automation: Come to the final section of our course. We have built a massive traceable system, and now let's make it work for us. In Data Center, we use automation for Jira to strip away repetitive tasks. I'm going to nagate to the example project, which I'm currently in. Click on project settings right here and find the automation. Up. Automation relies on a simple three part grammar, trigger, cognition, and action. I will click create rule in the top right. First, the trigger, what was to rule up? I will select issue transition. And let's select from in progress to two testing. Let's press Save. Next, the condition. We don't want to for this root to fire for every single TGType. Let's select new condition, select issue fields condition and say issue type equals B. Finally, the action. What does Jira actually do? I will click New action, select assign issue, and choose a specific engineer's name from the list. For example, me, because no one is locked in the zerra instance. Then let's name our automation as J automation and turn it on. It has been turned on with no codin required, we just build a digital system. The second, a developer moves the bock to sting instantly and silently, we assign it to the QA which is literally time saving thing and very convenient. Actually, we did a simple automation. We just transition from progress to testing and notifies QA that the bug is already ready to review. It is ready to test. But imagine if we have more complex automation, which will do unimaginable things. Automation is incredibly powerful, but here is a critical warning for anyone transitioning from Jura Cloud. Injera Cloud, the Pasian limits how many automation rules you can run per month. And if you run out, your automation is simply turned off until next month. Injurra Data Center because you own the servers, there are absolutely no biding limits on automation executions. You can run 5 million res month if you want to, but there is a catch. Hovering over our new rule details, imagine if I set this up to trigger every time, any field is updated of any ticket. If it loops through thousands of issues, I'm forcing my local server CPU basically my machine CPU to do all that mess so poorly written automation rules are the number one cause of ier data center crashes or lags for users. As a rule of thumb, always use strict conditions to ensure rules only fire exactly when they need to respect the server. 28. System Maintenance: Understanding Indexing: Welcome to the final lesson of the course. I want to leave you with the ultimate trouble shooting tool for your administrator. Sometimes in data center, you will create a new custom field or change dire language scheme, and suddenly your searches break. Tickets you know exist are no longer showing up on your HL boards. And basically, when this happens, the search index is out of sync with the database. To fix that, you need to navigate to the global server press system. Navigate to the bottom of the list, advance section and press indexing. This is the reset button. The ad option here called index is background or full. I suggest you to select Bground index. Because when administrator clicks this, Jira quietly scans the entire message database and repeats the search directly from scratch without kicking users offline. If your query language queries orderbards ever start acting crazy. Bground index is almost always the cure for that. So it will be selected for you as default option and you simply tick index. And it will do indexing without kicking users from Ser gira. As you can see, it does re index in a second. For more complex Jiras it may take, for example, some minutes, but then after this is done, your user just need to reload the page and everything will come. And with that, you have officially Master Jira Data Center. We started with a blank server in total database built strict enterprise schemes and master Jira Korea language and fully automated flows. You now have the skills to not just use Jira, but to come and it at massive corporate scale. I thank you so much for taking this journey with me. Best of flag piling, testing, and watching amazing things.