Automation Test Framework
- 1. Quality Assurance / Software Testing Training Defect Management tool - JIRA
- 2. Page 2Classification: Restricted Agenda • What Exactly is JIRA? • JIRA as an Issue Tracker • JIRA as a Project Management Tool • JIRA Roles • JIRA Request Format • JIRA Workflow Model • General JIRA Structure • Browsing Project issues • Created vs Resolved issue Report • JIRA Help
- 4. Page 4Classification: Restricted Objectives • To obtain a basic understanding of JIRA and the needs it fulfills • To understand what JIRA is currently used for • To gain basic operational knowledge of JIRA’s use and feature set • Know where to go for further information and help
- 5. Page 5Classification: Restricted What Needs Do We Have? • Precisely and conveniently capture a project’s problems • Robust tracking of issues to know when we are “done” with a project • Collect project status, history and metrics • Easily share this information across globally • Doing all of this (and the other needs not listed) easily
- 6. Page 6Classification: Restricted What Exactly is JIRA? JIRA is an issue tracking and project management application
- 7. Page 7Classification: Restricted JIRA as an Issue Tracker • Manage ALL Issues, not just software/firmware bugs • Manage Electrical, Mechanical, Packaging, Documentation and other issues throughout the NPD life cycle across single or multiple projects • Manage versions of software/firmware products • Track all phases of issues (creation, investigation, resolution, verification, closure…) • Easily understood user interface • Easily extensible
- 8. Page 8Classification: Restricted JIRA as a Project Management Tool • Access a project’s real time statistics with regard to issues • Highly configurable reporting and graphing capabilities • Track all aspects of project issues from any level across single or multiple projects • Easily understood user interface
- 9. Page 9Classification: Restricted JIRA Login for first-time users • Access JIRA via the link…. • http://amsdftwkg/secure/Dashboard.jspa • At the Login screen, select Sign-up for an account • Enter • User name (use Lotus Notes short name, all lower case) • Password (does not have to be the same as Notes, but may be) • Confirm password (one more time) • Full name • Email (important to use email address) • At the sign-up acknowledgement screen, choose Click here to Log In • Enter your user name and password to log in • You now have access to all projects and can view all issues. However, you can not enter issues, nor can you change the status of any issues or edit them in any way. Those rights are reserved for specific user “roles” which can only be assigned by the JIRA Administrators. Requests for those must be submitted through the CM database.
- 10. Page 10Classification: Restricted New User Sign-up Screen
- 11. Page 11Classification: Restricted JIRA Login Screen
- 12. Page 12Classification: Restricted Successful Sign-up Acknowledgement
- 13. Page 13Classification: Restricted JIRA Roles Roles and additional rights Project Manager – Can enter, assign and reopen issues (cannot close out issues) Developer/Engineer – Can enter, assign and resolve issues (cannot close out issues) QA – Can enter, assign, reopen and close out issues (does not typically resolve issues although possible) Read Only – Can view issues only
- 14. Page 14Classification: Restricted Requesting JIRA access from CM • CM Request Database is located on Catfish & Musky • All JIRA requests are processed via this database • To gain user access to JIRA – you need to enter a request • There is a specific format to the request that will facilitate the creation of your account and eliminate delays and additional questions… • There is also a procedure for requesting the creation of a new project file or changes to an existing one, but those are specific to PMs and QA users. These procedures are being refined and will be covered in training that targets these groups directly.
- 15. Page 15Classification: Restricted JIRA Request Format • At the CM Request database, choose the Create tab pulldown and select Master Request Form • At the next screen, select Configuration Request • At the Configuration Request form, enter: • Date & Requestor are auto-filled • Date Needed By defaults to approx. 3 weeks from current date, overwrite if required date is different • Description of Problem should be entered in the format - JIRA: Add (user name) as a (role) user. • User name is the Notes shortname that you used to setup your accoun • Role is the position or function you perform from the list (only one role per person). If you are not a PM or a member of QA, you should request to be added as a Developer. If you do not designate a role, it will default to Read Only. • Directly below the Total Weighted Score is a field for additional comments. Enter any special cases or relevant information that is important to processing this request • Nothing else on this form should be completed • Under the File tab in the upper left corner, select Save to submit the request to CM
- 16. Page 16Classification: Restricted Select “Configuration Request”
- 17. Page 17Classification: Restricted Enter Information Into Request
- 18. Page 18Classification: Restricted Now that you have access… what can you do? • Depending on your role, there are several things you can do within JIRA • Everyone can customize the look and feel of JIRA to suit their individual needs and tastes • Everyone can view the status of issues on a particular project or group of projects • Everyone can look at the specifics of a particular issue and view the progress of it’s resolution • Everyone can write and save custom filters to limit the range of projects or issues that are visible • Project Managers, QA and Dev/Eng can enter new issues • Project Managers, QA and Dev/Eng can assign issues to other individuals, depending on their authority on certain projects • Project Managers, QA and Dev/Eng can resolve/reopen issues • Only QA members can close out issues based upon verification testing and/or substantiating documentation
- 19. Page 19Classification: Restricted JIRA Workflow Model
- 20. Page 20Classification: Restricted General JIRA Structure • At the top level, all issues entered into JIRA are currently categorized into one of 9 issue types • SW/FW Bug • Electrical • Mechanical • Packaging • Documentation • Unknown • Improvement • New Feature • Task • NOTE: Currently all issue types include the same fields… future changes will customize the fields for each issue type. • All issues, regardless of type, are entered and managed within the project files that have been created. Project files are created by CM based on input from the PM or QA. • Within each project, the PM has the option to further sub-divide the project into smaller, logical pieces. These can be based upon the type of effort required, the physical sub-systems within the product, the geographical location of the development teams or any other logical way he wishes to segment the project. Typical “components” might be:
- 21. Page 21Classification: Restricted Project Overview Example
- 22. Page 22Classification: Restricted Issue Detail Example
- 23. Page 23Classification: Restricted Searching for Issue
- 25. Page 25Classification: Restricted Browsing Project issues
- 26. Page 26Classification: Restricted Created vs Resolved issue Report
- 27. Page 27Classification: Restricted JIRA Help How to get help JIRA documentation is located at: https://confluence.atlassian.com/display/JIRA051/JIRA+Documentation