Learn JIRA with real-world examples | Kosh Sarkar | Skillshare

Learn JIRA with real-world examples

Kosh Sarkar

Play Speed
  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x
43 Lessons (2m)
    • 1. Course Introduction

    • 2. JIRA - the What, the Why and the How

    • 3. Agile Concepts Refresher + Scrum + Kanban

    • 4. JIRA Terms - What makes up JIRA

    • 5. Intro to the JIRA user interface & navigation

    • 6. Viewing, editing & understanding Issues

    • 7. Working with Agile Boards

    • 8. Creating Issues

    • 9. Searching for Issues

    • 10. Advanced searching using JQL

    • 11. Search Filters

    • 12. Dashboard customization

    • 13. Quick note on navigation & Summary of videos so far

    • 14. Configuring agile boards - Part 1 (Scrum board)

    • 15. Configuring agile boards - Part 2 (Scrum board continued)

    • 16. Configuring agile boards - Part 3 (Kanban board)

    • 17. Creating projects

    • 18. Creating epics and stories

    • 19. Starting sprints and working on sprints

    • 20. Creating software versions in Scrum

    • 21. Creating software releases in Kanban

    • 22. Creating an agile board with multiple projects

    • 23. Closing sprints and viewing sprint reports

    • 24. JIRA Admin navigation

    • 25. Creating a new user

    • 26. Creating groups and access controls

    • 27. Understanding the different permission levels

    • 28. Global permissions explained

    • 29. Understanding Project Roles - Theory

    • 30. Understanding Project Roles - Example

    • 31. Roles and Permissions Example - Part 1

    • 32. Roles and Permissions Example - Part 2

    • 33. Roles and Permissions Example - Part 3

    • 34. Understanding Jira Schemes & Introduction to the Schemes Example

    • 35. Configuring Issue Types

    • 36. Configuring Screens

    • 37. Configuring custom fields

    • 38. Creating a new workflow

    • 39. Editing an existing Workflow

    • 40. Updating the agile board with new workflow changes

    • 41. Understanding Workflow transitions

    • 42. Working with Project Components

    • 43. Other Jira Administration and summary


Project Description

Learn JIRA with real-world Examples – Project Quiz Questions



  1. True or False: Scrum and Kanban are the only agile methodologies that exist
    1. True
    2. False


  1. What are Epics
    1. Daily 15-minute meetings held every day during a sprint
    2. A larger body of work that is broken into multiple stories
    3. The smallest unit of work, either representing a feature, or part of a feature to be implemented
    4. They are what stories are made up of


  1. Which one of these tasks are not the responsibility of the scrum master?
    1. Ensuring the team has the daily scrum meeting
    2. Ensuring that there are no blockers on team members
    3. Monitoring the progress of the sprint
    4. Can help the product owner groom the backlog
    5. Acts as a supervisor of the development team
    6. Sets up meetings required during the scrum process


  1. What should not happen in a sprint planning meeting?
    1. Sprint backlog is created from product backlog
    2. Dev team provides estimates for issues in the sprint backlog
    3. The team discusses potential improvements to their scrum process
    4. Sprint goals are defined
    5. All team members participate, including the scrum master and product owner


  1. What is not characteristic of the daily standup
    1. Usually takes place at the same location and time everyday
    2. It is kept to no longer than 15 mins
    3. Each team member talks about what they did the previous day, what the plan is for today and if there are any blockers
    4. Scrum master must resolve all blockers before the meeting is over


  1. True or False – both Scrum and Kanban methodologies utilize a board where work can be visualized
    1. True
    2. False


  1. What does not happen with Kanban methodology?
    1. Team determines how work flows from start to completion
    2. Work-in-progress limits are set to identify potential bottlenecks
    3. Work is broken into sprints
    4. Goal is to move issues from left to right


  1. True or False – You can create software versions well in advance of development, for both scrum and Kanban
    1. True
    2. False







  1. True or False – it is not possible to update your home page to be something other than a Dashboard.
    1. True
    2. False


  1. If you have an issue key 'SSP-14', which of the below statements is false?
    1. SSP is the project key to identify the project by
    2. No other projects in the Jira instance can have the same SSP key
    3. SSP-14 is the 14th issue that was created in the SSP project
    4. You can edit or modify the SSP-14 key


  1. Which of the following changes appear in the Issue’s History
    1. Updates to the issue description
    2. Changing the assignee field
    3. Logging work
    4. Moving the issue between columns on the board
    5. All of the above


  1. True or False - The only place in Jira where you can transition issues between statuses, is from the agile board
    1. True
    2. False


  1. The 'Affects Versions' field represents:
    1. The software version where the particular bug was found
    2. The software version where the fix for a bug will be going into


  1. True or False – all searches done in basic-mode using the filters can be translated to Advanced JQL queries, but not all JQL queries can be translated back to basic search using filters
    1. True
    2. False





  1. True or False - Issue statuses and workflow columns are not the same thing, but they can be called the same names
    1. True
    2. False


  1. What is the main thing that determines what issues will appear on a board?
    1. The project the board is for
    2. The filter that the board uses
    3. All issues in Jira can appear on any board


  1. A column constraint determines:
    1. How many issues are allowed in a column before Jira flags it
    2. How many statuses can be mapped to a column before Jira flags it
    3. How many issues are allowed to have a particular status within a column
    4. The number of columns allowed on a board


  1. If a column for an agile board exists with no statuses mapped to it, which of the following is true?
    1. The column appears but does not display any issues
    2. Jira displays an error saying that you cannot have an unmapped column
    3. The column does not appear on the board
    4. You cannot transition any issues to the unmapped status


  1. How many extra fields can be displayed on a card within the board
    1. 1
    2. 2
    3. 3
    4. 4
    5. 5


  1. True or False - Jira allows you to manage a backlog for Scrum projects only
    1. True
    2. False


  1. What could you create a new agile board from?
    1. A new software project
    2. An existing software project
    3. An existing saved filter
    4. Any of the above options


  1. What happens when there are incomplete issues at the end of the sprint
    1. The issue gets deleted
    2. You are unable to end the sprint
    3. Jira gives you the option to move it back into the backlog or another queued sprint


  1. Which one of these are not displayed in a sprint report
    1. Issues that were completed in the sprint
    2. Issues that were not completed in the sprint
    3. Issues that are part of the next sprint
    4. Issues that had a change in the original time estimate during the sprint
    5. A burndown chart for the sprint




  1. Where can you create users, groups and manage application access?
    1. Jira Administration
    2. Site Administration


  1. Where are project permissions configured and then assigned to a project?
    1. Global Permissions
    2. Project Permissions
    3. Permission Schemes
    4. Site Administration Section 


  1. True or false - if a default user or group is put into a project role from the project role administration page, only new projects created from that point onward will automatically get that project role assigned with whoever was set as default.
    1. True
    2. False


  1. How could you create a project that shares the same schemes used by an existing project?
    1. Create the project and then associate each correct scheme one by one from the project settings page
    2. Select ‘Create with shared configuration’ when creating the project
    3. Each project must use different schemes


  1. Where are you able to map a screen to an issue operation (Create/Edit/View)?
    1. Screen configuration page
    2. Screen Scheme configuration page
    3. Issue Type Screen Scheme configuration page


  1. How could you ensure that the assignee field gets updated to ‘unassigned’ every time you mark an issue as ‘Done’ within a workflow?
    1. Display a screen during all transitions to the ‘Done’ status so that the user can manually update the assignee field to ‘Unassigned’
    2. Specify a ‘Condition’ for all transitions to the ‘Done’ status to update the assignee field to ‘Unassigned’
    3. Specify a ‘Post Function’ for all transitions to the ‘Done’ status to update the assignee field to ‘Unassigned’
    4. Contact the project administrator to update the assignee field to ‘Unassigned


  1. What field determines whether an issue is open or closed, according to Jira?
    1. Status
    2. Resolution
    3. Priority
    4. You have to make a custom field for it


For the answers, and better format of the questions, please refer to the attached PDFs.

Student Projects