JIRA Terms - What makes up JIRA

Kosh Sarkar
A free video tutorial from Kosh Sarkar
Product Manager
4.5 instructor rating • 2 courses • 49,784 students

Lecture description

We'll define some of the key Jira terms like issues, projects, versions, and components

Learn more from the full course

Learn JIRA with real-world examples (+Confluence bonus)

Learn to work on, manage & administer agile projects with this comprehensive course on JIRA Software & Confluence

11:16:33 of on-demand video • Updated May 2020

  • Understand what JIRA is, benefits of JIRA and how to use JIRA
  • Understand Scrum - the stakeholders, events and overall flow of work
  • Understand Kanban flow of work
  • Use JIRA as a user working within an agile team - creating, working on and searching for issues, customizing dashboards etc.
  • Use JIRA as a manager of an agile team - configuring agile boards, managing the backlog, sprints and releases etc.
  • Administer all aspects of JIRA - create users, groups, set permissions, configure issue types, screens, fields, workflows etc.
  • Use examples presented in this course to customize and use JIRA based on your own unique needs
  • Get ideas (through examples presented in the course) on how JIRA can be utilized for different scenarios or situations
  • Learn the basics of Confluence
  • Learn how you can use both JIRA and Confluence together to work better and be more productive in general
English [Auto] Let's take a look at some of the terms that make up year an issue is the essence of Jiya and basically represents a work item. Any work item or anything that requires an action from a person. So when you create a ticket injuria you are essentially creating an issue. In other words Epic's stories bugs feature Quest's tasks. All of these are issues of a different issue type. So when you create an issue you can create an issue of an epic issue type or a story issue type or a task issue type Ixora you can create your own issue types. INJURIA as well but ultimately every ticket created in gear is referred to as an issue. It contains basic fields such as title description due dates priorities status etc. and you can make your own custom fields as well. A project pretty much represents the normal term or meaning of a project and is basically a collection of issues. It can be a software dev Project Help system. The general task manager so on and so forth. Obviously if you're looking at using Jira agile or Jira software you're most likely engaging in software development projects. Pretty much everything can be customized within a project including who gets access to it. The issue types available in a project the workflows use and many more. Which brings me to workflow or workflow is a set of statuses that an issue in a project can have along with the transitions between statuses that the issue can go through this image is an example of a workflow and what it looks like in gear. So when you create a ticket or issue it goes into the to do status. From here you can transition into two different statuses either in progress or done and the arrow basically represents what that transition is. So for example if I have an issue sitting in the to do state I could either transition or initiate the transition or start progress which will take the issue to the in-progress status. Or I can initiate a transition called done which would take the issue to the Done state and transitions and Jira are basically represented by a button on the issue details page. So if I'm looking at an issue that is currently in the in-progress state or with that status then I would see two buttons. One would be stop progress which when clicked would take the issue back to the to do status and the other button I would see would be done which would take me to the Done state. And similarly if issue is done then I could transition to the reopen transition by clicking on the reopen button back to do. Or I can click on reopen and start progress which will take the issue back to in progress. So this is what a workflow is and is fully customizable on Jira to fit your needs. In fact remember how I said that an issue can be of various types such as epic story Bhag etc. and a project can have different issue types associated with it. So for example a software dev project would definitely want the issue types of story and epix and maybe even tasks but a general task manager project would only need the issue types of tasks and subtasks and not really need stories or Epic's since it's just a general task manager and not a development project. So you can associate different issue types of the project and in Jira you are able to actually configure a different workflow for each issue type within a project to give you a high level taste of how configurable workflows can be. Enjoy. Now versions basically help track releases of software. So remember when I mentioned that at the end of a sprint you should have a shippable product or group of features. So for tracking purposes Jira allows you to create a version and add whatever issues that are going to be released into that version. You could either create a version at the end of every sprint if you're releasing that often. Or you could create a version over a set of sprints where if you've already identified the stages at which you want to release the software you can create your different versions well in advance and assign the respective issues to each version. In scrum a version is usually pre-planned and is released when the planned work is complete whereas in Kanban a version can be released at any time and will contain all the issues that are complete or in the down state at that time. Djourou components are just a feature that Jira offers to create subsections of a project. They are basically used to group issues within a project. So for example perhaps your project is broken into back end development and front end of it so you could create both of these as components and be able to group your issues accordingly. Its almost like a category of work and in and an advantage of having components is that you can configure issues created under a component to have a default assignee so that when created it's automatically assigned to that person. So for example you want all back and Dev issues to be assigned to your lead back end developer who can then delegate it out to other developers. You can do this through component configuration and last the Jira also uses the other common agile terms that we've already discussed such as scrum can ban backlogs sprints etc.. All right. Now that we've identified the main Jira terms we are now ready to take our first dive into Jira starting off as a user working within an agile team.