Jira.pptx

JIRA How to guide Version 04/23 Table of Content Click on hyperlink to access content • 1. JIRA First Steps • • • • What is JIRA? Logging in to JIRA Finding a project on JIRA Issues Page • 2. Search and Filters • Searching for issues • Using filters • Advanced search • 3. Reporting a bug • • •...

JIRA How to guide Version 04/23 Table of Content Click on hyperlink to access content • 1. JIRA First Steps • • • • What is JIRA? Logging in to JIRA Finding a project on JIRA Issues Page • 2. Search and Filters • Searching for issues • Using filters • Advanced search • 3. Reporting a bug • • • • Adding a new bug Filling in the info (4 slides) Attachments Uploading a bug • 4. Linking & Hyperlinking • Linking bugs • Hyperlinking in a comment or description • 5. Regression • How to regress bugs This guide explains how to use Jira as a software, NOT how to report a bug. Please refer to your project information for bug template and more info. JIRA First Steps What is JIRA? JIRA is a database in which you write your bug reports for developers to fix. We use many different databases depending on the project, but JIRA is the most common one. JIRA allows testers to view all issues reported for projects, the statuses of those issues, the ability to report/create a new issue, searching for issues reported, and so on. Universally Speaking’s JIRA database can be found using the following link: https://universallyspeaking.atlassian.net/ secure/BrowseProjects.jspa JIRA First Steps Logging-in To log into your JIRA project database, find the link and credentials to log into JIRA on the Project Channel (in "Daily Task" or "Project Info"). *Login details are provided on a project basis, so make sure you are using the correct account. (Please also note that access to JIRA for some projects requires access through a VPN – this information will be available from the Project Info or from your Team Lead) JIRA First Steps Finding a project Upon logging into JIRA, you will initially load into the "Projects" screen, which will display the projects assigned/accessible to the specific login credentials. From here, you can manoeuvre into different projects and observe, create, and regress issues relating to the specific projects. Then you will see this screen. JIRA First Steps Issues page Once you have proceeded to the "Issues" page, multiple issues may display to the user which will be specific to the selected project. You will see overviews of reported bugs for the project, in a listed format underneath the search bar. To open and view an issue fully, select the bug number or summary. Search & Filters Searching for issues Search bar It's important to check if a bug has been reported before you create one. To search through Jira, you can use the search bar at the top of the "Issues" page on a project. Search & Filters Using filters You can select several filters (by default: Project, Type, Status, Assignee), add more, and save some filters if you'll be using them often. Filters Search & Filters Advanced search Go to Advanced Search Selecting "Go to Advanced Search" allows you to filter through the issues with more options. Selecting and using additional search filters will add more options to search, such as including date reported, reporter/assignee etc Reporting a bug Adding a new bug Then you will see this screen. To begin writing a bug report, click “Create” at the top of the page and start filling out the fields. Before adding a new bug: - Check if your bug has been reported already (both in JIRA and bug tracker) - LQA - make sure all languages are checked in the bug tracker - Get the project Senior/Lead to search for the bug to ensure minimal duplicate bugs are created. Reporting a bug Filling in the info Most of the information you need to fill in will be available in the Bug Tracker and/or in the Project Info. This is a quick overview of the main sections, but these sections may vary by client and by project. • • Project and Issue Type: Double check you have the correct option selected. Summary: This is essentially the title of your bug. It should briefly announce what the issue is, and follows a particular format: •LQA: Platform (optional) – Languages codes/Global – Issue Area – Brief Summary •FQA: Problem-Action-Location Reporting a bug Filling in the info Most of the information you need to fill in will be available in the Bug Tracker and/or in the Project Info. This is a quick overview of the main sections, but these sections may vary by client and by project. • Assignee: Check the project information on Teams or ask the lead if this information is missing. • Class (Severity/Priority): Choose the severity of the bug. • Affected version: This is the specific build number that the issue was found on. • Labels: Keywords to help with sorting and searching, ask your lead to see if you need to include some if this is not mentioned In Reporting a bug Filling in the info This is a quick overview of the additional sections, but these sections may vary by client and by project, and you might not have them at all. • Component: Select the area that your bug is occurring in. • Bug Type: The type of bug that is occurring. • SKU: What type of build you have (DebugOpt, Master, or Both). • Reproducibility: How many times that the issue happens – usually out of 10 (e.g., 10/10 - 100%). Reporting a bug Filling in the info • Description: •The layout is usually as follows: Description, Steps to Reproduce, Reproduction Rate, Actual Result and Expected Result followed by any Additional Information. •Please check in your project's channel for more information. • Steps to reproduce might be included in the Description or have its own separate box. •Don't forget to stick to the bug template, it's a way of displaying how good our attention to details is. • Platform: Tick all the platforms that the issue occurs on (e.g. Xbox One, PC, etc.) • Language (LQA specific): Select the languages that are affected by the bug. Reporting a bug Attachments Always attach a screenshot or a video that shows the issue in-game. • If you attach a screenshot, you should use Paint to put a square red box around the issue. Sometimes, attaching a media won't work the first time. In that case, upload your bug, and return to it to add your media. • Screenshots should always be in .jpeg format. • Video size is client dependent but 10MB maximum is usually the standard (per attachment) and should always be in .mp4 format. • Always rename the files. Please check your project information for more info on how to name the media but it is usually named as the bug number followed by A, B, C etc. E.g., USS-1234-A. • LQA: Always attach a screenshot in the affected languages and in English. • FQA: For all crashes and assert/debug breaks, include a debug log or crash dump if possible (unless asked for more). *Please check other How to guides to understand how to edit media. Reporting a bug Uploading a bug • Once the bug is written, click on “Create” at the bottom on the page • Please check with your Senior or Lead first if they want to vet your bug before you press Create. • Copy the link and bug number and add it to the relevant documents used in your project (e.g. bug tracker, testcase/checklist...) Linking Bugs Bugs can be linked together for many reasons, the most common for QA being “relates to”, “blocks”, and “is blocked by”. 1. To link one bug to another, first select Link Issue at the top of the bug. This can be done during bug creation or after the bug has been created. 2. Select the desired reason for linking, then search for and select the issue it’s linked to. Hyperlinking in a comment or description You are also able to hyperlink inside bugs to other bugs in JIRA. This is helpful in comments when you are referring to another bug. This is also necessary when marking a bug as BLOCKED, as you’ll be directing people in your comment to the bug that is blocking the one being commented on. To Hyperlink in JIRA, just write out the bug number in the comment as it is written on the bug. Capital letters, hyphen, numbers, no spaces. Example: WWE2K23-9215. When the comment is entered, this will automatically set it as a hyperlink. If the bug doesn’t hyperlink, this will mean that it was not entered correctly for some reason. Possibly due to spaces include, or words not being capitalized. If you have any questions, please ask a lead. How to regress bugs Once a regression has been tested, click on the status dropdown and update JIRA using the following status depending on the result: BUG CONFIRMED AS FIXED: • Leave a comment: “Fix verified on XXXX (console) in build XXXX” • Click on “Fixed->Closed”. Sometimes we need to regress a bug on all platforms before we fully close the issue. In these cases, just the "Console Status" will be changed before all platforms have been checked. Once all platforms are checked, we can then close the issue. BUG FIX FAILED (ISSUE STILL PRESENT): • Click on “Fix Failed->Open” • Leave a comment: “Issue is still present on XXXX (console) in build XXXX” • Provide a new screenshot or video from the current build *Who opens and closes bugs depend on the project, Practice We have a training account that you can use anytime to practice using Jira. Please do not delete any bugs. LQA Training: LT board - Agile board - Jira (atlassian.net) QA Training (FQA, CQA & VR): FQA Training - Issues - Jira (atlassian.net) Login Username: [email protected] Password: UniTrain1! Do not use this account to report any bugs in your projects. THANK YOU We want to keep this guide up to date and relevant for all departments. Want to add or edit some information? Want to remove outdated information? Send an email to [email protected] with the subject: How to guide – Suggestion – [HowtoguideName]