PO5 - JIRA - Assignment TEAM C

410-P05-NA PROJECT MANAGEMENT TOOLS
COURSE- Project Management
Team C
SATNAM SINGH TEJI 2220074

VIREN KHARE 22301143
SEHAJPREET SINGH 22202154
CARLOS EDUARDO 22300665
MARILIA BRAGA 2220037
JIRA- SFT INSTANCE
Overview for Jira project leaders
Scheme &
Issue Types Components Screens Fields Custom Fields Github & Jira Gitlab & Jira
Associations
JIRA, BY ATLASSIAN
 JIRA is a tool developed by Australian Company Atlassian. It is used for

bug tracking, issue tracking, and project management. The name "JIRA" is
actually inherited from the Japanese word "Gojira" which means
"Godzilla".
QMetry. (2016, April 15). Qmetry test management for jira (QTM4J). Atlassian Marketplace. Retrieved March 21, 2023, from
https://marketplace.atlassian.com/apps/1215144/qmetry-for-jira-test-management?hosting
JIRA, BY ATLASSIAN
 The basic use of this tool is to

 track issue and bugs related to your software and Mobile
apps.
 It is also used for project management.
 The JIRA dashboard consists of many useful functions and

features which make handling of issues easy.
PRIVACY AND SECURITY
 Privacy policy
 Atlassian's privacy policy is not applicable to the use of this app. Please refer
to the privacy policy provided by this app's partner.
COLLABORATE BETTER WITH
BDD AND CI/CD INTEGRATIONS
Author & sync feature files to BitBucket, GitHub & GitLab. Enable continuous
testing with CI/CD tools - Bamboo, Jenkins. Automated testing through REST
APIs & BDD tools - Cucumber, JUnit, TestNG, SpecFlow, QAF, UFT.
ENTERPRISE GRADE TEST
MANAGEMENT FOR AGILE
TEAMS
Maximize Testing with easy import-export of test cases, automated authoring of

test cases using Exploratory Testing. Increase efficiency and reduce duplicate
efforts with test case reusability across projects..
CROSS-PROJECT REPORTING
AND REAL-TIME ANALYTICS
End-to-end traceability between stories, test cases, executions and defects with
Traceability Reports. Publish QMetry macros on Confluence pages using free
QTM4J Confluence Integration app
JIRA SCHEME
 Inside JIRA scheme, everything can be configured, and it

consists of
 Workflows
 Issue Types All those definitions are instantiated and

associated together in order to define the
Custom Fields
information that will be contained, edited
 Screens and visualized in each Jira project
 Field Configuration
 Notifications
 Permissions
JIRA SCHEME ASSOCIATIONS
Visibility and other
properties are
specified in:
Field
Field
Configuration
Configuration
Scheme
Field
Is mapped to Issue Types by:

Is mapped to Issue Is associated
Operation by: Issue Type to a:
Visualized Screen Screen PROJECT
by placing
it on: Scheme Scheme
Screen
Is mapped to Issue
transition (Open
Close …) by: Workflow
Workflow
Scheme
ISSUE TYPES
All types of items that can be created and tracked via
JIRA.
Name type Description
Bug Standard A problem which impairs or prevents the functions of the product.
Created by Jira Software - do not edit or delete. Issue type for a big
Epic Standard user story that needs to be broken down.
Improvement Standard An improvement or enhancement to an existing feature or task.

Incident Standard
Issue template
(WBSGantt) Standard Issue template
New Feature Standard A new feature of the product, which has yet to be developed.
Question Standard
Created by Jira Software - do not edit or delete. Issue type for a user
Story Standard story.
Suggestion Standard
support Standard New issue type for support tickets required from Savannah import.
Task Standard A task that needs to be done.
Bug sub-task Sub-Task
Improvement sub-
task Sub-Task
Sub-task sub-task The sub-task of the issue
Technical task Sub-Task A technical task.
ISSUE SCHEMES
An Issue scheme
in Jira is a
collection of
different types of
Jira Issues
COMPONENTS
 Components are sub-sections of a

project; they are used to group issues
within a project into smaller parts.
 Components add some structures to
the projects, breaking it up into
features, teams, modules, subprojects
and more.
COMPONENTS
 Using components you can generate

reports, collect statistics, and display it
on dashboards and so on.
 To add new components, as shown in

the screen below, you can add name,
description, component lead and
default assignee.
JIRA SCREEN
 “Screen”, is used by Jira to build the

interface in order to create, modify and
display an issue.
 A Screen is defined with
 a name and description
 …. it needs to be configured by adding
a list of fields
JIRA SCREEN
 “In order to associate a Screen to an

issue operation it is needed to create a
“Screen Scheme” by assigning a name a
description and a “Screen”
In this example the specified fields of a “bug” issue

type are displayed by using the following screen:
JIRA FIELDS
Actual End Epic Status LOCKED Planned End
Actual Start Epic/Theme Planned Release
Affects Version/s External issue ID Planned Start
Approver External issue URL PlannedEnd
Ariadne External reporter PlannedStart
Assignee Finish date (WBSGantt) Platforms
Attachment Fix Version/s Priority
Baseline Effort Flagged Progress (WBSGantt)
Baseline End Gantt Chart Project/Package
Baseline finish date (WBSGantt) Gantt Options Rank (Obsolete)
Baseline Start Group watchers Rank (Obsolete) LOCKED
Baseline start date (WBSGantt) Issue Type REQUIRED Rank LOCKED
Bug / Feature Item Group Release Version History
Business Value Labels Reporter REQUIRED
Cause Latest End Request/Incident domain
Change scope Latest Start Resolution
Comment Linked Issues Savana Fields Container
Component/s Locking Savannah Fields Container
Customer Log Work Security Level
Date of Baselining Manually scheduled (WBSGantt) Severity
Description REQUIRED Milestone (WBSGantt) Should Start On
Destination sites MS-Project ID Sprint LOCKED
Development LOCKED Operating System Start date (WBSGantt)
Due Date Original Reporter Story Points
Effort Originator Email Summary REQUIRED
Environment Other Custom Fields Tag
Epic Colour LOCKED Output types Time Tracking
Epic Link LOCKED Percent Complete Units (WBSGantt)
Epic Name REQUIRED LOCKED PercentDone Velocity %
JIRA CORE STANDARD FIELDS
JIRA CORE STANDARD FIELDS
JIRA SOFTWARE STANDARD

CUSTOM FIELDS
CUSTOM FIELDS
 It is possible to create new customized fields for each project whenever there is need for
that.
 It may be useful in some cases to use project specific custom fields because the projects are
dynamic and may change their requirements in time.
 Jira disposes of a wide type of field types that may be chosen from a predefined list which
is shown in the next slide
STANDARD CUSTOM FIELD TYPES
JIRA AND GITHUB
Connect Jira Cloud to GitHub
When GitHub is linked to JIRA Software,

branches, commit messages and pull requests
are all seamlessly referenced in JIRA Software
issues.
This allows JIRA Software to display
information about your development activity in
the corresponding issue
JIRA AND GITLAB
GitLab Jira integration
Once the GitLab project is integrated

with the Jira instance, its possible to
automatically detect and cross-
reference activity between the GitLab
project and any of project in Jira.
This includes the ability to close or

transition Jira issues when the work is
completed in GitLab.
CONCLUSION
 The SFT Jira instance is a private instance which is maintained by our

group for all functional aspects and we ask for the support of IT for
specific issues like “upgrade” or for complex problems that we cannot
solve.
 It has the advantage of being able to define as many new specific
“Screens” and “Custom fields” as needed for the best functionality of our
projects. This is not possible in the central instance of Jira because of the
high number of projects.
REFERENCES
QMetry. (2016, April 15). Qmetry test management for jira (QTM4J). Atlassian Marketplace. Retrieved March
21, 2023, from https://marketplace.atlassian.com/apps/1215144/qmetry-for-jira-test-management?hosting

PO5 - JIRA - Assignment TEAM C

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PO5 - JIRA - Assignment TEAM C

Uploaded by

Copyright:

Available Formats

410-P05-NA PROJECT MANAGEMENT TOOLS

COURSE- Project Management

SATNAM SINGH TEJI 2220074

 JIRA is a tool developed by Australian Company Atlassian. It is used for

 The basic use of this tool is to

 The JIRA dashboard consists of many useful functions and

Maximize Testing with easy import-export of test cases, automated authoring of

 Inside JIRA scheme, everything can be configured, and it

Is mapped to Issue Types by:

Improvement Standard An improvement or enhancement to an existing feature or task.

 Components are sub-sections of a

 Using components you can generate

 To add new components, as shown in

 “Screen”, is used by Jira to build the

 “In order to associate a Screen to an

In this example the specified fields of a “bug” issue

JIRA SOFTWARE STANDARD

When GitHub is linked to JIRA Software,

Once the GitLab project is integrated

This includes the ability to close or

 The SFT Jira instance is a private instance which is maintained by our

You might also like