Get a basic overview of JIRA administration.
- [Instructor] So by now, you should feel very comfortable with the role of a user within JIRA. You should understand the basic functionality of the software and are ready to move on to the management and customization of your own instance. This means you are ready to take the mantle of administrator. But what does this mean really? JIRA administration requires the ability to not only control the JIRA instance, but to gather requirements from different teams, strategize on the best way to utilize custom elements, and control the look and feel of the instance itself.
It requires patience and listening with different types of people. Prepare to be in a lot of meetings and to advise many people in your company's structure. Depending on your unique situation, your start as an administrator may be difficult, simple, or somewhere in the middle. A more advantageous situation is starting the instance from scratch with the company. This allows you to advise from the beginning the best practices and knowledge needed to create a healthy and robust system. However, more often than not, you'll find yourself in the unfortunate situation of picking up where someone else left off, and that someone, or someones, might have set up JIRA improperly or in a manner you may not be entirely familiar with.
This will require much more testing and care in your work. As anyone in software development will tell you, testing is key to ensuring a quality product is released to the public. As a JIRA administrator, the users of your environment are your public, and you want to provide them an instance that is free from errors or walls that prevent the user from creating issues, searching information, or even logging in. The key to this is setting up a proper test environment that ideally replicates the live environment as much as possible. This requires access to the server and the ability to import and export both instances and projects, which may require assistance from someone in the IT department.
If this isn't available to you, a small setup in the cloud or on your local machine will suffice. Think of the "dev" environment, or test environment, as a playground, where you can experiment with these concepts without any far-reaching repercussions in your live environment. If you're feeling overwhelmed, don't worry. We're going to go over some of these concepts in more detail in the coming chapters. The most common things you will encounter while being a JIRA administrator are modification requests. I advise setting up your own project within JIRA to field these requests, like I've done here, as opposed to having users file requests in their own project.
By controlling your own project, you define the process in which you field these requests and can tailor it to your individual recording style and requirements. In addition to workflow and project requests, you will be tasked with user management, creation of filters and dashboards, system-level changes, and maybe even adding icons to individual issue types. But don't get overwhelmed. The good news is the flexibility and design of JIRA ensures there is usually more than one way to solve any problem, and you'll soon have the knowledge needed to manage the most advanced system requests.
For many areas of industry, JIRA provides a way to fully digitize and report on a variety of processes within any given company or organization. From manufacturing to DevOps, software development to customer service, understanding basic JIRA administration will make you comfortable enough with the platform to customize your instance for a variety of required tasks.
- User management
- System administration
- Project administration
- Creating new issue types
- Creating new issue type schemes
- Roles and groups
- Adjusting notifications