Jira fundamentals and bug tracking tool Guide

Editor's Notes

• #3: Explain to students why do we need to have a system for tracking project activities and why this is so important. Give examples of Project Management and Issues Tracking tasks
• #4: JIRA is advanced highly customizable issue tracking system. In JIRA you could customize workflows to any business process and integrate JIRA with existing systems to manage tasks, track activity and ensure you meet your deadlines. You could add as many plug-ins as you need to expand it capabilities. All this makes JIRA a flexible project management tool whether you can track bugs for a single application, managing software development for several products or running countless projects throughout your entire company.
• #6: Training Agenda
• #11: Components Components are sub-sections of a project. They are used to group issues within a project into smaller parts. (A component is the first and most basic way to classify and identify about which part of the software your issue report will be.) The next operations could be done with components: Add — Make new components under which issues can be classed. Delete — Remove a component from a project. Edit — Update/change the details of a particular component. Select Default Assignee — Set the default assignee for issues created in a particular component.
• #12: Versions are points-in-time for a project. They help you schedule and organize your releases/sprints . There are two ways how you could create version: I. Create version from Administration section:     1. Go to 'Administration' section in Jira, choose project to which you want to add version.     2. You will now see a page displaying the project details. On this page all the configurable actions available on the project are easily accessible. On the lower right, a summary of the versions is displayed along with the link to the version management interface. The summary indicates the version status and the scheduled release date for that version.    3. Click the 'Manage' link to display the 'Manage Versions' screen, which shows a list of versions and each version's status. From here you can perform the operations described below.
• #13: JIRA consist of a set of Projects. A project component is a logical grouping of issues within a project. Each project may consist of various components (or none), depending on your organization's needs. For example, a software development project could consist of components called 'Documentation', 'Backend', “UI”, 'Email Subsystem’ etc. Any issue can belong to one or multiple components within a project or component may not be selected at all. Versions are points-in-time for a project. They help to schedule and organize releases and sprints. Any issue can belong to one or multiple versions within a project or version may not be selected at all (it will be shown as unresolved by default). Each issue belongs to a project but may not belong to component or version.
• #14: In our Jira / Confluence configuration we have single sing-on login (this mean if you are using one browse to enter to your Jira / Confluence, and currently you are already enter to one of them you don’t need to login to another system will automatically log you in). The Dashboard is the first screen you see when you login to JIRA. - The navigation bar (at the top of the screen) is the same on every screen in JIRA. It contains links which give you quick access to many of JIRA's most useful functions. - The white area of the screen, below the top navigation bar, can be customized to display 'gadgets' showing many different types of information, depending on your areas of interest. Dashboards The JIRA Dashboards is the first screen you see when you log in to JIRA. It can be configured to display many different types of information, depending on your areas of interest. If you are anywhere else in JIRA, you can access your JIRA Dashboards view by clicking the 'Dashboards' link in the top left corner of the JIRA interface. Projects This screen provides a general overview of your project, with a variety of easily accessible reports for your project's issues, builds and source code reviews, from which you can 'dig down' into further detail. Issues JIRA provides a powerful issue search facility. You can search for issues across projects, versions and components using a range of search criteria. If you need to find issues based on time-tracking details, then the standard 'simple search' interface also allows you to search against the work logged on issues. JIRA also makes custom fields available as search criteria, allowing you to refine your searches even further. Agile Link to GreenHopper section, you also could choose one of the view: Planning Board, Task Board, Chart Board, Released Board. Administration In this section you could find information about your project (Name, Project Key, URL, Project Lead, Default Assignee, Operations View and Edit). Click Edit if you want to edit project info or Project Name link to enter to project info tab.
• #16: JIRA Issue (or entity) represents any distinct logical piece of project scope. Different organizations use JIRA to track different kinds of issues. Depending on how the organization is using JIRA, an issue could represent a software bug, a project task, a helpdesk ticket, a leave request form, etc. Technically there are 2 types of issues – parent and child (or sub) issues. It means that sub-issue is the one level down of parent issue and can detail the scope of its parent. 4) Each entity type has its own properties (defined through custom fields) and a lifecycle (defined through the workflows, states and transitions between states)
• #17: While User Story describes the distinct piece of functionality, the Epic may reflect the high-level functionality, component, sub-system overview from which user stories might be derived. In simple words, Epic is a big user story that needs to be broken down into smaller pieces. “Referenced Epic/User Story” - a text field to put ID of Epic that originated given User Story Usually either Epics or User Stories are used within a project. However, there are cases when project scope is tracked in Epics by non-technical project staff (Product Managers, Sponsors, upper-level managerial staff, etc)
• #18: 1) Sub-Task issue type can not be tracked autonomously, since it’s configured as sub-issue and there is no much benefit of tracking just pieces of work
• #36: The 'Work Ratio' search is based on the Actual work logged against an issue versus the original Estimated work duration. Work Ratio Percentage = (Time Spent / Original Estimate) x 100%
• #37: The 'Work Ratio' search is based on the Actual work logged against an issue versus the original Estimated work duration. Work Ratio Percentage = (Time Spent / Original Estimate) x 100%
• #38: The 'Work Ratio' search is based on the Actual work logged against an issue versus the original Estimated work duration. Work Ratio Percentage = (Time Spent / Original Estimate) x 100%
• #40: The 'Work Ratio' search is based on the Actual work logged against an issue versus the original Estimated work duration. Work Ratio Percentage = (Time Spent / Original Estimate) x 100%
• #44: The 'Work Ratio' search is based on the Actual work logged against an issue versus the original Estimated work duration. Work Ratio Percentage = (Time Spent / Original Estimate) x 100%
• #45: Resolved recently- Project: !TEST Workflows - Demo Resolved: From 1 week ago to anytime Outstanding- project = TESTWFLL AND resolution = Unresolved ORDER BY updated DESC Most Important -project = TESTWFLL AND resolution = Unresolved ORDER BY priority DESC
• #47: QC subtasks: project="!TEST Workflows - Demo" and "Task Type"= "Quality Control“
• #48: Select filter Tools> Bulk Operation
• #49: Select filter Tools> Bulk Operation
• #50: To choose which columns (i.e. issue fields) to display in your Issue Navigator, Click the 'Issues' link in the navigation bar at the top of the screen. The Issue Navigator will be displayed. From the 'Tools' menu at the right of the screen (above the search results), select 'Configure Columns'. To choose how many rows (i.e. issues) to display on each page of your Issue Navigator: Click your user name at the top-right of the page to open your User Profile. Click 'Edit Preferences', under 'Operations' in the left-hand column of the screen. Enter your preferred 'Number of Issues displayed per Issue Navigator page', (The default is 50). Click the 'Update' button.
• #53: Dashboard> Tools>Create Dashboard You can now customise your dashboard as follows: Choosing a Dashboard Layout Adding a Gadget Moving a Gadget Removing a Gadget
• #54: You can also share your dashboard pages with other users, as well as adding dashboards shared by other users as favourites. Each dashboard page appears as a separate "tab" on the dashboard. You can view a dashboard page by simply clicking its name in the tab list.
• #63: GreenHopper 'contexts' help streamline the view of your project by filtering and highlighting issues based on preset criteria. You can hide and/or highlight certain issues via a saved JIRA filter or custom criteria. Contexts are available in the Planning Board, Task Board, Chart Board and Released Board. A different context can be used on each board. You can select a context for each of the following: Planning Board — 'Project Overview' mode Planning Board — 'Version' mode Planning Board — 'Component' mode Planning Board — 'Assignee' mode Chart Board Released Board Task BoardYour choices for each of these will be remembered. GreenHopper comes with 2 built-in contexts: - 'On the fly' context — A non-deletable context that will allow all logged-in users to build new contexts (See the 'Creating a New Context' section below). Any changes that a user makes to this context will only persist for the current session and will not be saved. - 'Default' context — A non-deletable context that only the project administrators can edit and that is shared to all users and anonymous users (if your project is public). It is very important to note that editing this context will affect all users that use that context. To modify a context: 1. Log into JIRA. 2. Click the 'Agile' menu in the top navigation bar. 3. Select the Planning Board or other board to which this context applies. If you have chosen the Planning Board, select the mode to which this context applies. 4. Select 'Manage' from the 'Context' dropdown (next to the project dropdown). The 'Edit Context' window will display. - 'General' tab: 'Context name' — Edit the name of your context. 'Share' — Check this checkbox to share the context with other users. User will then be able to select this context from their context dropdowns. Please note, you must be a project administrator to share a context. - 'Sorting' tab — Select a different field by which to sort your context. - 'Filter' tab — Edit the filter criteria as described below. - 'Highlight' tab — Edit the highlight criteria as described below. - 'Delete' — Click this button to delete the context. You must be the creator of the context to delete it. Please note that once you have deleted a context there is no way to restore it. You will need to recreate it manually.