*************
Course Title:
*************
- Understanding JIRA for users, managers and admins
-
Course link
============
https://www.udemy.com/course/introduction-to-jira/learn/lecture/19656544?
components=buy_button%2Cdiscount_expiration%2Cgift_this_course%2Cpurchase
%2Cdeal_badge%2Credeem_coupon#overview
JIRA Account Details
====================
> Free account - Sign on with Google
>
[email protected] > Site link:
manoj-kumar-nanduri.atlassian.net
*************************************************
Introduction
*************************************************
Agile Basics
===============
> Software dev methodology centered around helping teams get more done by self
organizing their work
> Ever evolving and changing
> Adapt rapidly to changes
> no right or wrong - only what is right for your team
Agile Board
==============
TO DO IN PROGRESS DONE
----------------------------------
> Over the course of the sprint, we should aim to move all tasks from todo to in-
progress to done. We dont want any task lingering in IN PROGRESS for long
> Two ways to organize - scrum and kanban
> one key difference - scrum has sprints and kanban does not
Scrum
------
> same structure of board - TODO/INPROGRESS/DONE
> Team works in sprints where a set of tasks are agreed to be completed in a
pre-determined amount of time
> sprint is a pre-determined amount of time where teams determine the work to
get done
> start with shorter sprints preferably and figure out the right period
> Have sprint meeting at the end
> discuss last sprint
> what went well
> what did not go well
> what can we do better next sprint
> discuss and agree on work to be completed in next sprint
> Team can have daily standup meetings as well to discuss progress
Kanban
------
> same structure of board - TODO/INPROGRESS/DONE
> No sprint. No time-based agreement of tasks. Team works on tasks in ongoing
basis and new tickets keep getting introduced as team progresses with tasks
> Team might need to rely more on daily standup meetings to discuss progress and
challenges as there are no pre-deteremined sprint meetings
JIRA Stories and Epics
=======================
> #User Story
- As a <type of user>, I want <some goal> so that <some reason>
- Ex: As a driver, I want my car's dashboard to be voice activated so that I
can get directions safely while driving
- Ex: As a cashier, I want to have the total calculated for me so that I can
give the correct change back to the customer
*** technical details are not usually part of the user story as the user may
not care about these
*** the way user stories are written may not follow a set convention and rules
depending on what type of project the team wants to complete - marketing/software-
dev/sales etc
> #Epic
- A story that is too big for single sprint
- It is broken down into multiple user stories
- when all those stories are done, the epic is completed
- Ex: Epic: Android Auto and Apple CarPlay functionality for our app
~ Story1: As a driver, I want the app to be voice activated so that I can
start playing music safely while driving
~ Story2: As a user, I want playlists for my music so that I can queue
upmusic for my next drive
~ Story3: As a user, I want to sync the music from my mobile and computer
with the app so that I can have access to music I have purchased across devices
> Typically, stories in JIRA are user stories and epics are parents to multiple
to user stories
Issues and Projects
===================
> #Issues
- Stories, epics and bugs are the typical types of issues in JIRA
- custom issues can be created too
- issues hold the fields that contain your data
- Example fields - description, summary, assignee, due date etc.
> #Projects
- Projects are containers for the issues
- projects organize things about your issues
- Ex: Regulatory Trade Reporting is a project which contains all
epics/bugs/stories and other issues related to this team. Similarly, PostTrade,
MIFID, etc all are different projects. Classification can be even more granular or
less granular depending on requirements and what works best on case by case basis
- Access can be controlled at the project level. So, person in one project may
not be able to access issues in other projects etc.
Next-gen Projects
==================
> introduced in 2018
> does not require admin permsissions to create
> entities (issue types, statuses etc) live inside the project
> greatly simplified compared to classic projects
> Next Gen project vs classic project
> Next-gen
-----------
> project scope entities. Ex: if an issue type SoftwareBug and Testing Bug are
created in one project, they are visible only in that project unless specifically
created in others as well
> no special permissions are needed to create them
> fast and easy to setup and maintain
> Classic Projects
-------------------
> Global entities. Ex: issue types created like Bug, Story etc are visible
across all projects and there are no issue types or entities specific to one
project
> admin permissions needed to create them
> more complicted to setup and maintain
Versions of JIRA
================
> JIRA Core
> Team Project collaboration
> business focussed project management
> task management
> JIRA Core version DOES NOT include "Agile"
> JIRA Software
> Everything in JIRA Core + agile functionality
> Kanban and scrum project management
> Software development integrations and tools
> this is more targeted towards software dev teams
> JIRA Service Desk
> Everything in JIRA Core + helpdesk fucntionality
> IT Support and helpdesk ticketing
> Troubleshooting management
>*** This course uses JIRA Software which has scrum and kanban board management
JIRA Licensing Options
======================
> Cloud (web) or Server (install on your own server)
> JIRA Cloud
> lower cost subscription model
> automatic updates included
> atlassian support included
> JIRA Server
> Not a subscription (purchase instead)
> install on your own server
> extreme customization possible since it's your own server
> This course uses JIRA Cloud
***********************************************
Basics of JIRA
***********************************************
> Keyboard Shortcuts are Global
> c --> create issue
> / --> search option
>
> Looking at Projects in JIRA
> Starring a project gives quick access from Projects dropdown
> If a project does not have agile board, clicking on the project name will give a
view with list of issues and few things etc...
> However, if an agile board is setup, JIRA changes the default view of the
project to the agile board
> Reports section within projects. Not covered in this course in detail. Easy to
explore. Not a lot of customisation in these reports. You have what you have.
> components is another feature... explore**
> admins might see some extra options like Add Items, Project Settings etc
Creating Issues
===============
> c is shortcut to display create issue screen
> only admins can create custom issue types (something more than bug/epic and
story)
> what type of fields contain within issues are controlled by the JIRA Admin. THey
can add or remove field types and even create custom fields as well
> admins can create custom fields
Searching for Issues
====================
> search using the jira number or description/summary
> search using keyboard shortcut /
> or search using the search box at the top
> for other search, use advanced search
> this has several custom filters
> you can also fiilter by project, issue type, status, assignee etc.. all of
them
> USE JQL
---------
> trivial query language
> there is a syntax help for JQL with ? icon just on the search bar. This has
great documentation on jql syntax
> using jql, you can add complex seach queries and get desired results
Overview of the issue detail view
==================================
> Comments, History, Work Log
> By default, reporters would be marked as watching the issue
> Link Issue
> Understand more about Linking issues and what they mean
> Use Link issue at the top of each issue
Working with Filters
=====================
> You can write filter queries using JQL to get desired data and can also save
them
> Once a filter is created, JIRA uses this at multiple places. Ex: A filter can
be used in an agile board to show only the results that were requested
Scrum Agile Board Overview
===========================
> ScrumBoard/KanbanBoard
> Quick Filters
-- these are additive - not OR (AND is applied on multiple filters)
> Explore the agile board layout and menu
> Check if you have permission to create quick filters and if you dont, reach out
to the one with Admin permissions and get some quick filters setup
> Play around with the scrum board and the quick filters in your own project
Continuing Scrum Agile Board Overview
=======================================
> Once you close a sprint, JIRA will ask you what to do with the pending tasks -
they can be assigned to new sprint or moved to a backlog?
> Before the sprint, ask everyone in the team to go to the backlog and re-
organize the tasks
> Then review the tasks in the sprint and the backlog and the n go person by
person and assign the tasks to be picked up in the sprint
> Columns on the board - usually correspond to different statuses of the issues
- if any column is not mapped to a status, you may not be able to move an issue to
that column. You will need admin permissions to change these settings
> Explore how the mapping of columns to statuses is done *****
Kanban Agile Board Overview
============================
> QUESTION - Is it possible to have a kanban board and a scrum board for a
single project? Also, is it possible to have multiple scrum boards (probably based
on different filters) on a single JIRA project?
> Anything moved to DONE would stay in that column for 2 weeks. This setting can
be changed though by admin
Continuing Aglie Kanban Board Overview
=======================================
> Kanban boards do not have sprints
> But they can have backlogs - so that the in Progress does not have too many
tasks
> If you want to move things in and out of backlog, go to backlog and drag/drop
> Filters in boards are additive. not OR.
> Once an issue in kanban is done, it will stay in DONE for 2 weeks
> Settings > general
> Filter determines what issues to show in the kanban board
> ***Can we have multiple kanban boards for single project to have different
views?***
Next-gen projects
=================
> NON-administrators can create next-gen projects too
> Boards are mostly similar to Classic
> We can create issues from the board though in next-gen
> Has a group-by option -- by asignee, subtask, none etc....
> Add new columns in the board itself
> Ability to manage rules
> several rules - ex:whenever you move an issue to a certain status, assign
it to specific person
> ROADMAP
> ...
Working with epics in Classic Projects
=======================================
> Epic Creation - same as creating any other issue
> Creating issues in epic
> Traditionally, epics are used more in Scrum because epics span multiple
sprints
> In Kanban, Epic is not on by default, but admin can add that as well
> You can have Epics in backlogs within kanban board
Working with Epics in next-gen projects
========================================
> Same way of creation as epics in classic projects
> Roadmap view lets you see all epics you have and other issues etc.
> Is GoJIRA next-gen project based?
> New issue types can be created in next-gen (something other than
Epic/Bug/Task/Story)
> Custom Issue types are specific to the project
===============================
Section-2: Manager Perspective
===============================
> Working with teams
====================
> In classic projects, managers do not have specific permissions apart from team
and no admin permissions. If they want to do some extra stuff, they will need admin
permissions
> In next-gen however, managers do get permissions above the other team members
even though they are not admins
> **** This section uses next-gen projects to demonstrate ****
> People tab on top
> Start a team
> invite people to it
> teams work independently of the projects - people can be same/different/mix-
match between teams and projects
> You can view tasks, comments etc of all people in last 90 days
> Deleting a team will delete all the information in the team. USers will remain
intact though.
Creating a scrum board
======================
> IN classic projects, all agile boards live within the project. SO, go to the
project in order to create a board ->choose scrum board
> towards the left, you will see boards and in the dropdown, you will see an
option to create a new board
> You can create a board either directly off of a project or you can use a JQL
query to set what issues should be displayed on the board
Editing a scrum board
======================
> Active Sprints
> In order to customize what is visible on a board
> Go to ... (settings - three dots on top right corner)
> go to board settings -> General
> edit filter query (default is to show everything on the project)
> Filter query can be updated using user interface options as well.
> apparently, one board can contain issues from multiple projects ***confirm
> Go to columns
> You can map the board columns to status of each issue. By doing this, moving
an issue to a column automatically changes the status of that
> You can have multiple status mapped to each column. This way, moving an issue
to such columns will give you options to choose across all those statuses
> Swim-lanes
> You can use this to visually breakup your board based on your preferences
(breakup by assignee/issuettype/etc...)
> Quick Filters
> setup quick filters that can be accessed from the board
> Card colours and layouts
> change them as needed
> Estimation
> change these time tracking details so reports are better informative
> Working days
> what days are working days etc to factor into burndown chart etc
Creating a Kanban Board
=======================
> One of the powers of classic projects is that you can have both scrum and kanban
boards
> go to project, go to the left pane to expand the boards -> to create a board ->
choose kanban board
> choose existing project or a custom jql filter
> Scrum board only shows issues in active sprints -> kanban boards show all issues
in the project
Editing a Kanban board
======================
> Go to ... -> board settings
> Filter Query
> Go to General - > Update the query to control what is shown on the board
> Editing columns
> Kanban backlog - Go to Board Settings -> Columns -> you will see a kanban
backlog at the bottom next to the columns
> Move the Todo column to the backlog and you will see the option for backlog
visible
> What this does is all the TODO issues are moved to the backlog. These are
remoed from the kanban board view. THis helps us to view the issues in progress to
the kanban board and the others in the backlog
> One thing unique to kanban board is the release button on the top right of the
Kanban board. What this does is essentially create a version for all the tasks on
the Done column and they disappear from the board.. All these issues are visible in
the release tab on the mid left section
> what if you want issues to disappear from the board immediately after they are
moved to DONE
> to do this, simply update the filter query to hide all issues with
status=DONE from the board
Working with Dashboards
========================
> Create a dashboard and share it with whoever you want. If you want it to be
private, simply do not share it with anyone
> On the top pane, go to Dashboards -> Create a new dashboard -> name, desc, and
access addition to ppl
> now, add the gadget (gadgets are various charts and graphs/tables etc.)
> Filter results gadget is useful***
> go to saved filter -> create new filter (go to filters on top -> advanced
issue search -> switch to basic)
> now go back to the dasboards and addthis filter to our gadgets
> in this filter results dashboard, you can choose to have whatever columns you
want
Saving filters for your team
============================
> Sometimes, created filters dashboards that are shared with your team do not
display data . THIS IS BECAUSE YOU NEED TO GIVE ACCESS TO YOUR TEAM TO BOTH THE
DASHBOARD AND THE FILTER INDEPENDENTLY*****
BULK Creating Issues
======================
> You can create bulk issues using an excel
> Create -> Import Issues (top right on the create window pop up)
> use a csv file in the below formate
> header fields can be anything -> you will get an option to choose which JIRA
field to be mapped against every csv field
> You can also map values for these fields to those in JIRA. Just check the Map
Value box.
Bulk Edit Issues
=================
> Search for your issues (may be using a query) and on the top right, choose ...
-> bulk change all issues -> choose/remove any you want to skip ->
