Jira Server for Power Users goes beyond the basics and is intended for power users and mid-level administrators. After this course, you should be able to run Jira as a project administrator and understand the best ways to work with issues, JQL, software boards, and reports.
This course is designed to help you get more from Jira as well as share tips and relevant use cases for project configuration. It's intended primarily for users of Jira Server, but if you're a Jira Cloud user, you'll find that much of the course content here applies to you too.
After the introduction, we'll teach you what makes up project administration and how you can interact with it. It's important to take a moment to talk about schemes so that we can understand what exactly you're capable of changing in a project and what you need to request through your institution's Jira change management process. If you're a project administrator, you're able to edit some details of your project as well as your components and versions and update your team by assigning the right people in the proper roles.
Speaking of roles, we'll teach you about users and roles and how you can build your team. Building your team is one of your main tasks as a project administrator. You need to decide what team members are in which roles. The Jira administrator creates the project roles you can use so if you need an additional project role, you need to work with the Jira administrator to build it.
That said, more and more power is being entrusted to the project administrator, so we'll also teach you about the additional project admin permissions that are available and how you can use the extended project admin permissions to configure the workflow and edit screens without involving a Jira administrator.
And before we wrap up chapter 1, we're going to cover a few things that don't fit elsewhere in this course. First, your user profile includes details on your groups, email, recent activity, and your preferences. The user profile gives other Jira users some information about you and what you're working on, but it's also the place where you can change some of that information or some of your settings. We'll cover those settings, and then we'll talk about how releases and versions are used in Jira. Versions are a way to breakdown the issues in your project. They don't actually have to be used to represent releases. Use them as you need to categorize your issues.
Course Overview and How We Take it to the Next Level
Project Admin Overview and Schemes
Users and Roles
Additional Project Administrator Permissions
Navigating and Updating the User Profile
How Releases Are Used in Jira
Creating and Managing Jira Issues
Jira is built for helping you organize issues within projects and work more efficiently. However, as your Jira instance grows, you may find it harder to manage all of the issues you have within the system, especially if you have too many cooks in the kitchen. In this chapter, we'll talk about managing your Jira issues to help you organize your work and provide a solid base for reporting. We look at fields and issue linking, as well as some best practices for getting useful data from your Jira issues. We also talk about the advanced workflow features you may want to use to manage your issue.
As a project administrator, you can't edit or add new fields to an issue type yourself; however, you can view the fields that are used in your project and work with your institution to change management process to add or update fields.
You should link issues so that you have a flow of data that makes sense. Create your links so your team can see where everything is. Providing this transparency helps other users audit themselves. It also keeps teams happy as conflict can arise when you have a user who can't find something. Make it so they never have to reach that point by providing links to appropriate issues and pages.
After we cover issue fields and linking, we'll talk about some of the advanced workflow features you can use in Jira and how best to use them. Remember, workflows are created by the Jira administrator, but you should understand how some of the underlying pieces work so you can work with the Jira administrator to add new features if you need them. Let's spend some time talking about what each of these items does in your workflows with a quick workflow review to start.
And last, we'll cover commenting in Jira, how to generate notifications using comments, and the restrictions that can be associated with comments.
Working with Fields
Advanced Workflow Features
Commenting to Specific People
Advanced Jira Query Language
Now we dive into searching using JQL. We'll do a quick review of the basics and then start working on the steps for you to become a JQL badass.
Once you've got a working search, you'll learn how to adjust the issue navigator columns and save your search as a filter. Use this feature to save columns for your filter and for those you've shared your filter with. And if you need, switch back to defaults to look at the information you may have removed from the filter's columns.
After a brief review of JQL (and if you need more introduction, just check out our Jira Server for Beginners class!), we'll dive into some more complex JQL like how to find a set of issues based on a date or a date range.
Then we'll start to combine JQL statements so we can go beyond simple questions like what issues in a project are assigned to a particular user. Using JQL combinations, you can really power up your queries by combining different operators, values, and functions.
Last, we'll talk about some ways you can extend JQL using third party tools like ScriptRunner. You'll dig deeper into fields and searching, as well as create scripted fields using JQL that can run scripts and calculate information based on data from your JQL.
Search and JQL Review
Configuration and Sharing Filters
JQL Basics Review
Working with Time in JQL
Extend JQL Options
Working with Jira Software Boards
In this chapter, we focus on Jira Software, discussing the use of boards and other features in Jira Software that you might find useful as a Jira power user. While we introduce some agile terminology like scrum and kanban, we don't go into much detail on these frameworks. Instead, our focus is on the basic configuration of Jira Software boards for the power user, and you can check out our Jira Software courses here on Adaptavist Learn for more detail on using Jira Software for scrum or kanban.
If you have Jira Software enabled on your instance, anyone can create a board in Jira. When you create a board, you need to choose to create the board from an existing project or projects, or from an existing saved filter. We'll cover a few quick tips, then talk a bit about the process of working with backlogs, working with sprints, and then working with cards on your boards.
We'll also cover board permissions and some ways you can configure your board to support complex projects and situations that occur in your organization. Most of the advanced Jira Software board configuration is identical for both scrum and kanban boards, so no matter your approach, you'll find help in this chapter.
Last, you may need to use multiple boards in one project to manage different parts of the project. You may also need to see issues from multiple projects on one board to consolidate teams into one space that's easy to view. To handle these situations, we're going to make use of filters and the advanced configuration options available in Jira Software.
Overview and Discussion of Agile Methodology
Boards in Jira Software
Work in Sprints
Advanced Board Configuration
Using Multiple Boards for One Project, and Multiple Projects in a Single Board
Creating and Interpreting Jira Reports
Before we dive into reports in Jira, we're going to do a quick review of dashboards and best practices for using dashboards. Remember that dashboards are made up of gadgets and displayed in Jira, and the gadgets can contain information on issues, user activity, charts, and more. In Jira, you have a system dashboard that you can't change. This dashboard is set by the Jira administrator for the entire Jira instance. However, you can create and use your own dashboards.
Within Jira, you find several different report options. These available reports depend on what project template you choose as each Jira application has different options. For this course, we focus on Jira Core and Jira Software reports, but if you're interested in learning more about Jira Service Desk, check out the Service Desk course where we cover reports and dashboards for Service Desk projects. Notice that there are some standard Jira reports that are in both Core and Software projects. These reports include the Average Age report and the Time Since Issues report.
After we talk about reports in Jira and advanced JQL, we're going to dig into issue filter subscriptions. Why would you want to subscribe to a filter? Think of issue subscription as another way to get information and updates about your issues in Jira outside of dashboards and reports.