What are boards & how to create/access them?

What is board?

You need a board so that you can view and work with issues in JIRA Agile. A board displays issues from one or more projects. You can either use a board that someone else has created, or create a new board for yourself. You can create as many boards as you like.

There are two types of boards:

  • Scrum boards are for teams that plan their work in sprints.
  • Kanban boards are for teams that focus on managing and constraining their work-in-progress. Because work is not planned in advance using discrete time periods or versions, Kanban boards are visible in Work mode but not in Plan mode.

Before you begin, please note that you will need the JIRA ‘Create Shared Objects’ global permission before you can create a board. If you don’t have this permission you can still create a board, but it will not be visible to other people as its filter will not be shared.

You can either copy an existing board, or create a completely new one.

How to create a board

  1. Log into JIRA.
  2. Select Agile > Manage Boards from the top navigation bar.
  3. Choose Create board at the top-right of the page.
  4. Either you can create Scrum or Kanban board. There are two tabs – Presets and Advanced. In Presets you can just enter name of board and default swimlanes are created. But in advanced mode, you need to have at least one saved filter based on which board is created.
    Important: You need to have a JIRA Administrator privileges to create board. Otherwise you wont see Agile menu.


    How to view a board

    1. Log in to JIRA.
    2. Click Boards from the top menu
    3. Depending on your privilages, you may or maynot have access to create board.
    4. List of boards are shown. Click on any project board or you can click View all boards to view all boards
    5. There are three mode to view board in JIRA. They are Plan, Work and Report

    Plan Mode

    In Plan mode you can:

    • Prioritise the Backlog — Create issues for your backlog, rank and estimate them, and drag-and-drop to add them to a sprint.
      (info) Right-click selected issues to add them to a sprint, send them to the top/bottom of the backlog, export them to Excel, view them in the JIRA Issue Navigator, or perform

        Bulk Operations

      .

    • Estimate Stories — You can use the ‘J’ and ‘K’ keys to move through issues in the backlog and get details on the right-hand side of the screen. Plug in your estimates orstory points as you go.
      (info) Note that, by default, the Story Points field is only available to issues of type ‘Story’ or ‘Epic’ — you can change this as described in JIRA Agile – JIRA Configuration.
    • Create Sub-Tasks — To break a story (issue) down into implementable chunks, go to the sub-task section (click the sub-tasks icon) to view and create sub-tasks.
    • Organise via Epics — Group related stories into an epic. Click EPICS to view the Epics panel, where you can create epics, drag-and-drop issues into epics, and filter by epics.
    • Plan Versions — Assign issues to upcoming versions. Click VERSIONS to view the Versions panel, where you can create and edit versions, assign issues to versions via drag-and-drop, and filter by versions.
    • Plan, and Plan Again — When you’re happy with the stories for the iteration, start a sprint and the stories will move into Work mode. While a sprint is active in Work mode, you can still plan subsequent iterations in Plan mode (click Add Sprint), but you won’t be able to start them until the active iteration is completed. (You can, however, drag and drop an issue in Plan mode onto the active sprint.) Note that you can only start (or complete) a sprint if you have ‘Administer Projects’ permission for all projects that match the board’s filter.

    An issue will only be visible in Plan mode if:

    • the issue is not a Sub-Task;
    • the issue matches the board’s Saved Filter (seeConfiguring Filters);
    • the issue’s status maps to one of the board’s columns (but not the ‘Done‘ column);and
    • there is at least a status being mapped to the right mostcolumn. Eg. If you have the columns To Do, In Progress,and Done, ensure that you have a status mapped to In Progress at least. If you map all the statuses to the first column (To Do), you will not be able to see any issues in the Backlog.
    TAB LEGEND
    Tab Click to …
    Resize the Issue Detail View
    View the issue’s details:

    • Summary
    • Story Points (editable)
    • Remaining estimate (if you have Time Trackingset to ‘Remaining Estimate and Time Spent’)
      (if the issue has sub-tasks, the Remaining estimate for the issue and sub-tasks will be rolled up in the parent issue)
    • Status, Component, Labels, Affects Version and Fix Version, plus any fields you have added
    • Reporter, Assignee, Date Created, Date Updated
    • Links (plus a button for quickly creating new links)
    View the issue’s Description field.
    View any comments on this issue.
    View any files attached to this issue.
    View a convenient summary of the issue’s sub-tasks (plus a button for quickly creating new sub-tasks).
    View any test sessions for this issue (if you are usingBonfire).
    View any commits for this issue (if you are using theDVCS Connector).

    Work Mode

    In Work mode you can:

    • Work on Issues — Choose the highest ranked issues in the ‘To Do’ column and drag them to the ‘In Progress‘ column. (See Transitioning an Issue.) As you complete each issue in the ‘In Progress‘ column, drag it to the ‘Done‘ column.
      (info) Right-click selected issues to add them to a sprint, send them to the top/bottom of the backlog, view them in the JIRA Issue Navigator or perform

        Bulk Operations
    • Release a Version — Click Release to create your new version and mark it as ‘released’ throughout JIRA and JIRA Agile. (See Releasing a Version (Kanban).)

    (info) Note:

    • column constraints apply to the total number of issues in a column, regardless of whether some issues are currently hidden because a Quick Filter is in use.
    • swimlanes can be based on criteria of your choice. Swimlane issue counts are affected by Quick Filters, that is, issues hidden by a Quick Filter will be excluded from the swimlane count.
      (tick) Press “” to expand/collapse all swimlanes.
    • for Kanban boards, you can specify a Work sub-filter, which refines the issues returned by your board’s filter (see Configuring Filters). By default this sub-filter includes issues with no fix version or unreleased fix versions. So when the Release link is used to release a Kanban version, the completed issue will no longer be shown in the Done column.
    • an issue will only be visible in Work mode if:
      • the issue matches the board’s Saved Filter (seeConfiguring Filters); and
      • the issue’s status maps to one of the board’s columns; and
      • the issue is in an active sprint.
    • the board will be refreshed every 30 seconds, if the browser window does not currently have focus. If you have focus on the window, it will show a message asking you to refresh. Note, this auto-refresh functionality only works in Work mode.

    Report Mode

    The following reports are available:

    • Control Chart
    • Burndown Chart (for Scrum boards only)
    • Cumulative Flow Diagram
    • Epic Report (for Scrum boards only)
    • Sprint Report (for Scrum boards only)
    • Velocity Chart (for Scrum boards only)
    • Version Report (for Scrum boards only)

    Reports are board-specific, that is, they will only include issues which match the board’s Filter.

    Source – https://confluence.atlassian.com

Leave a Reply

Your email address will not be published. Required fields are marked *