Jira Project Yashoda CLG

Shivaji University, Kolhapur
CHAPTER NO. 1
INTRODUTION TO THE STUDY AND METHODOLOGY
1.1 Introduction:
Jira Software is part of a family of products designed to help teams of all types
manage work. Originally, Jira was designed as a bug and issue tracker. But today, Jira
has evolved into a powerful work management tool for all kinds of use cases, from
requirements and test case management to agile software development.
Jira Software provides planning and roadmap tools so teams can manage stakeholders,
budgets, and feature requirements from day one. Jira integrates with a variety of
CI/CD tools to facilitate transparency throughout the software development life cycle.
When it’s ready to deploy, live production code status information is surfaced in the
Jira issue. Integrated feature flagging tools allow teams to roll out new features
gradually and safely. Bugs are just a name for to-do's stemming from problems within
the software a team is building. It is important for teams to view all the tasks and bugs
in the backlog so they can prioritize big picture goals. Jira’s powerful workflow
engine ensures that bugs are automatically assigned and prioritized once they are
captured. Teams can then track a bug through to completion.
1.2 ManagementProblem:
The management problems are lack of supervisor support, lack of training and
development JIRA further comes with a number of features to meet varying
requirements of agile QA teams. In the organization too much workload is there.
Management needs that job security and workplace safety in the organization. Lack of
human resource and tools and technologies.
1.3 Statement of Research Problem:

Study on effectiveness of JIRA software testing tool on web development
applications with reference to Qlogiciel technology, Satara.
1.4Objective of the Study:

1. To study the features of JIRA testing tool in web development .
2. To study the effectiveness of JIRA tool in testing phase.
3. To study the reasons of JIRA testing tool using in web development.
YSPM’S Yashoda Technical Campus, Satara Page. 1

1.5 Scope of the Study:

1.5.1 Geographical Scope:
Geographical scope of the study is confined Qlogiciel Technologies Pvt. Ltd’s,
satara. Plot No.43, S.N. 20K, Lakshmi Vihar Building, Visawa Park, Sadar Bazar,
Satara, Maharashtra 415002
1.5.2 Conceptual Scope:
In this chapter include Introduction of JIRA software testing tool, features of JIRA
testing tool, uses of JIRA testing tool, JIRA test case management, differences in test
case approaches, how to write test case in JIRA, objectives.
1.5.3 Analytical Scope:
Analytical scope of study refers to percentage method, graphical method used for
data analysis
1.6 Importance of the Study:

Many IT companies nowadays adopt agile project management methodology to deliver
custom software applications within a short amount of time. Agile project management
methodologies emphasize on continuous planning, continuous testing, and continuous
integration. In an agile environment, QA professionals need to perform a variety of
testing repeatedly and consistently. Hence, they need specialized tools and frameworks
to evaluate the software efficiently in an agile environment. Most software testing tools
come with features to simplify and speed up test case development and execution.
Also, these tools are not developed by keeping in mind the varying requirements of
agile software testing. Atlassian JIRA is designed specifically as an agile software
testing. The commercial testing tool is used widely by QA professionals for tracking
environmental and project level issues in addition to bugs and defects in agile
environments.
1.7 Research Methodology:

The main type of research is descriptive survey study.
1.7.1 Data Required:
The data is qualitative research study.
1.7.2 Data Sources:
The data contains discussion, observation, organizational records, company
website and also other websites.
1.7.2.1. Primary Source:
The primary data collected through questionaries and observation method.

1.7.2.2. Secondary Source:

The secondary source collected through company website and other websites,
articles, journal, book, magazine, newspaper etc.,
1.7.3 Sampling Design:
1.7.3.1. Sample Unit: Samples are taken from main branch of the company.
1.7.3.2. Population: Total number of employees are 32
1.7.3.3. Sampling Size: Researcher has taken 32 samples.
1.7.3.4. Sampling Technique: Researcher has used convenience sampling
technique.
1.8 Chapterization:
Chapter 1: Introduction to the study and methodology
This chapter deals with introduction of the study, management problem, statement of
research problem, objective of the study, scope of the study, importance of the study,
research methodology of the study and organization of project.
Chapter 2: Theoretical background
In this chapter include Introduction of JIRA software testing tool,features of JIRA
testing tool, uses of JIRA testing tool, JIRA test case management, differences in test
case approaches, How an Issue Created in Jira, Jira For Requirements & Test Case
Management, What Is Roadmap In Jira objectives And objective.
Chapter 3: Company Profile
This chapter contain Name of the Unit, Location or Address of the Unit, Brief History
of the Unit and Present Position, Strategic Intend of Organization, Milestones
Achieved by Bank, Awards, Certifications, etc. Human Resource Scenario of
Organization, Future Plans of Organization, Organization chart
Chapter 4: Analysis and Interpretation of Data
In this chapter, the data collected by researcher is analyzed and interpreted.
Chapter 5: Finding, Suggestions and Conclusion.
In this chapter researcher has mentioned finding, suggestion and conclusion.
Appendices:
In appendices contains Bibliography and Questionnaire.

CHAPTER NO. 2
THEORETICALBACKGROUND
2.1 Introduction of JIRA software testing tool:

JIRA is a type of issue tracking tool developed by the Atlassian company that is
Australia based organization. The Jira testing tool is mainly used for tracking the
bugs, tracking issues and also used for the project management activities. It is mainly
used for finding the bugs in mobile applications and software. The dashboard of Jira
tools offers various features and functions to its users that can be used for finding the
bugs. It is used for group projects as the managerial work and activities can be easier
using the Jira testing tool.
2.1.1 What is Jira Testing Tool?
The Jira testing tool is mainly used for tracking the software activities and also to
track and plan the activities related to projects. The Jira platform is beneficial when
the project uses the agile methodology in the development. Using this tool the
workflows can be customized and group activities can be performed better and
software can be developed easily using this platform. The main reason for the
development of Jira testing tool is for testing software that uses agile
methodology.The agile methodology is used in many projects so that the development
time of the project can be reduced. The agile projects use nonstop testing, constant
joining for the project activities. The Jira tool was developed in the year 2003 that is
developed for track the bugs to improve the software. The software can be improved
by proper planning the project activities and track the project activities. The Jira is not
an open-source tool and user need to take monthly subscription for using the services
offered by the tool.
2.1.2 Audience of Jira Testing Tool
The Jira testing tool is mainly used by the development teams, support teams and
other department teams to manage the project activities. The QA teams uses the Jira
testing tool widely as the bugs can be easily tracked using this tool and also helps to
maintain proper bug tracking environment and solve issues. The industry that works
related to testing widely use this tool in their project testing.There are basically three
concepts of the Jira tool that includes issue, project and workflow. The bugs, task or
any type of enhancement request which can be generated or that can be track is

defined as issue. The other features related to issues are issue types, screens,
workflow, issue attributes and fields. The group of issues is known as project. The
workflow is defined as a collection of steps that goes from the starting phase to
completion phase. The complete cycle is known as workflow. The issues that are first
generated is the first one to get processed and then complete the issue to get into
closing phase. The items that are created in the tool can be displayed and can also be
tracked using the Jira testing tool.
2.2 Features of Jira Testing Tool:
Given below are some of the fascinating features:
1 The Jira testing tool uses the MySQL, PostgreSQL, Oracle and SQL as the
backend server technology for tracking the bugs and issues in testing tool.
2 The other feature is the flexibility and integration with other platforms. It can
be incorporated with other tools like Mercury, GIT, Subversion, Clear case,
team foundation, concurrent version type system and other platforms.
3 The other feature is the capability of incident management and manage the
project management activities.
4 The other feature is compatibility with other operating systems. It is defined
as stage free type tool that means it can integrate with multiple operating
system like Linux, windows and many more.
5 The Jira testing tool supports many languages like English, German, Spanish,
French and many more. Support of multiple language creates more user
opportunity for the tool.
2.3 Uses of Jira Testing Tool:
1. Catch Bugs
The Jira testing tool is mainly used for finding the bugs present in the software and
catch that bug for further processing. Once the bug is identified in the software, the
further processing is done on the bug that include finding every possible detail related
to bug, level of seriousness, version, screenshot and other related details of bug.
Thebug can be related to anything that requires to solve them to make the software
bug free
2. Organize and Allocate

When the tool identifies the bugs in the software, the next task is to allocate the
seriousness level and organize the issue according to effect and assigned in critical
bug group. The organizing of bugs is important as the bugs having higher priority
needs to be solved first. This will make the software better and will produce better
results.
3. Track Bugs and Solve
As the bugs are allocated a group, the next job for QA team is to select a procedure to
solve the bugs. The issues that are raised are displayed on the Jira dashboard that
helps to aware the team about current issues and bugs present in the software. By this
the team will have the knowledge to solve the process and allocate the resources to
enhance the issue and make them solve.
4. Getting Informed
When the bugs are caught in the software, it can be immediately raised and can be
displayed in the dashboard of the tool. By this the target can be set for employee to
solve the bug immediately. And when one bug is solved and if another bug is raised it
can be immediately forward to other employee so that it can be take care off.
2.4 Jira Test Case Management:
Jira has been around for some time now, and is considered a key part of the Atlassian
tool family to perform defect and issue tracking. Like many management-type tools,
Jira is fundamentally a repository designed to facilitate documenting and tracing issue
reports. And, it does that job very well.The repository nature of Jira has prompted
some people to explore the idea of using Jira as a test case management tool as well.
In essence, one would be treating test cases the same as an issue/defect report. So, the
question of “Can Jira be used as a test case management tool?” is “Yes, it can be.”
But the process is not all that simple and straightforward.
2.5 Differences in Test Case Approaches:
In my experience after reviewing thousands of test case approaches and

documentation, I don’t think I have seen any two approaches exactly alike. This is
both good and bad.The good side is that you can be in control of how you define your
tests. The bad side is that there are many nuances in test case design and it is very
easy to commit to a test case approach and format that is not scalable or has similar
issues.That said, there is an architectural view of how test cases can be effectively
structured to facilitate traceability, maintenance, reuse, scalability, execution and
measurement.Issue and defect reports also have attributes that can greatly facilitate
tracking, traceability and resolution.When comparing the way test cases and issue
reports are formed and used, we can see some clear differences. If a tool is designed
primarily for issue reporting, it will likely not be optimal for test case management.
2.6 How an Issue Created in Jira:
Whenever an issue or defect is encountered while testing, it needs to be reported so

that the developers can work on it and take the necessary action to fix it.We will see
step by step as how an issue is created in Atlassian JIRA.
a) Log in to your JIRA account by using valid credentials and get directed to the
dashboard.
b) Click on ‘Create’ button displayed and you will be navigated to a window for
creating an issue.
c) Enter all the necessary details as required to create an issue. The below field
example can be understood better by the image below.
In the Project field, a project for which we are creating an issue is selected. In this
example: STH_Learning(STHL) is selected from the dropdown containing all the
available projects.
In the Issue type field, the nature of the issue is selected from the dropdown which
contains options like Bug, Task, Improvement, Story, New Feature, etc. In this
example, ‘Bug’ is the nature of the issue.
The Summary field contains the oneline title of the issue which imparts the critical
information about the issue in a summarized way. The more effective the issue
headline, the more you can show the criticality of the issue. Of course, the headline
should be easily understood without any chances of misinterpretation. The example I
have taken here, however, is not much critical.

The Reporter is the one who reports the issue. In most of the cases, the name of the
Project Manager is selected in this field.
In Description field, the detailed description of the issue is written. As you can see in
the below example screenshot, Steps to reproduce the issue, Actual result, Expected
result are included in the description.
Priority field defines which issue should be considered first to be fixed. Tester selects
the priority of the issue from the dropdown based on its effect on the application. This
example issue is basically of a medium priority.
In the Attachment field, any video or screenshot related to the issue is being uploaded.
2.7Jira for Requirements & Test Case Management:
2.7.1Jira for agile teams:
For teams who practice agile methodologies, Jira Software provides scrum and
kanban boards out-of-the-box. Boards are task management hubs, where tasks are
mapped to customizable workflows. Boards provide transparency across teamwork
and visibility into the status of every work item. Time tracking capabilities and real-
time performance reports (burn-up/down charts, sprint reports, velocity charts) enable
teams to closely monitor their productivity over time.
1. Issue tracking
2. Customizable workflows
3. Estimation and work logging
4. Progress reporting
5. Project backlogs

2.7.2 Jira for project management teams:
Jira Software can be configured to fit any type of project. Teams can start with a
project template or create their own custom workflow. Jira issues, also known as
tasks, track each piece of work that needs to pass through the workflow steps to
completion. Customizable permissions enable admins to determine who can see and
perform which actions. With all project information in place, reports can be generated
to track progress, productivity, and ensure nothing slips.
1. Issue and task management

2. Roadmaps
3. Report and analytics
4. Project backlogs
5. Granular user permissions
2.7.3 Jira For Software Development Teams:
Jira Software provides planning and roadmap tools so teams can manage stakeholders,
budgets, and feature requirements from day one. Jira integrates with a variety of
CI/CD tools to facilitate transparency throughout the software development life cycle.
When it’s ready to deploy, live production code status information is surfaced in the
Jira issue. Integrated feature flagging tools allow teams to roll out new features
gradually and safely. The DevOps template is designed for high-performing teams to
save time and reduce errors by managing work from a variety of tools in one
centralized place.
1. Releasing planning
2. Sprint planning
3. Issue management
4. Developer tool integrations
5. Feature flagging
2.8 What Is Roadmap In Jira:
Roadmaps in Jira Software are team-level roadmaps useful for planning large pieces
of work several months in advance at the Epic level within a single project. Simple

planning and dependency management features help your teams visualize and manage
work better together.
2.8.1 What Is Backlog In Jira:
Your backlog is a list of tasks thatrepresents outstanding work in a project. Usually, a

project would have issues in the backlog, and you can add these issues to a sprint so
your team can work on them. Since Teams in Space is a new project, you won't have
issues on your backlog. Let's create some work for your team.
2.8.2 Purpose of Jira Tool:
Jira Software is an agile project management tool that supports any agile
methodology, be it scrum, kanban, or your own unique flavor. From agile boards,
backlogs, roadmaps, reports, to integrations and add-ons you can plan, track, and
manage all your agile software development projects from a single tool.

2.9 Objectives:
1.Finding defects which may get created by the programmer while developing the
software.
2.Gaining confidence in and providing information about the level of quality.
3.To prevent defects.
4.To gain the confidence of the customers by providing them a quality product.
5. To make sure that the end result meets the business and user requirements.

CHAPTER NO. 3
COMPANY PROFILE
3.1 Name of the unit

QLOGICIEL TECHNOLOGIES PVT LTD. SATARA
3.2 Location or Address of the Unit
Name of the Company Qlogiciel technologies Pvt ltd. Satara
Address Plot No.43, S.N. 20K, Lakshmi Vihar Building, Visawa

Park, Sadar Bazar, Satara, Maharashtra 415002
E-mail Address info@qlogiciel.com
Phone Numbers +02162-231119
3.3 Brief History of the Unit & Present Position

Qlogiciel Technologies is an offshore web design, software development and digital
marketing company in India that makes your communication and transaction on the
internet more effective and useful. We ensure this through appropriate content and
suitable internet tools, sufficient enough to reach far and wide markets. Qlogiciel
Technologies services leverage deep domain expertise in the industry, technical
expertise in leading internet technologies and a cost-effective global solutions
delivery model. The services are provided under the aegis of our communications and
e-business practices
Modern Infrastructure, our technology-inspired Infrastructure consists of fully
equipped & controlled environment of approx. 1200 sqr. ft. for development, with the
most advanced IT assets situated within a LAN. It has 24-hour adequate Power
Supply with 8 hours backup through UPS. It has a discrete feature that is
uninterrupted 24*7-hour high-end Internet Connectivity through ADSL (2Mbps)
connection, with an ISDN & Broadband and backup facility.
Qlogiciel Technologies Pvt. Ltd.’s an emerging software solutions company, which
delivers quality services of any complexity to clients all around. We have hand-on
experience in web Designing, software development, ERP solutions, web hosting
services , digital marketing, SMS gateway, payment gateway, e-commerce along with

project guidance.
Qlogiciel Technologies Pvt. Ltd.’s provides various IT solutions for small scale
companies. We use client-based development model, so each product we produce is
absolutely unique. always follows client first policy to make sure clients need should
be satisfied. We never compromise in Quality, which made us to improve to this
position. Increased consumer demand for innovative products at lower costs presents
tremendous challenges for companies trying to satisfy both requirements.
1. Android Application Development.
2. E-Commerce Website Development.
3. Web Designing.
4. Industrial Training
5. Internship program
3.4 Strategic Intend of company

3.4.1 Objectives:
1 Determine the need to make changes to manufacturing processes, process
controls, in-process tests or product specifications
2 Determine the need for re-validation of existing processes
3 Identify product or process improvements
4 Provide our customers with the Variety of brand and products
5 Verify the consistency of development processes
3.4.2 Mission of company:

1 Well defined policies and processes
2 Long term engagement with multiple project opportunities
3 continuous improvement of our Services, Products, Processes and People.
4 To provide customer high quality solution and satisfaction through great
service.
5 Create best organization to satisfy the customer and business needs of the
company.
3.4.3 Vision of company:
1 Delivery of Product and Services which are globally competitive.

2 Provide innovative solution in software consulting, staffing and outsourcing. .

3 Continuous improvement in service quality, long – term customer

relationship, value to our customers.
4 Continuous improvement of our products, processes and people.
3.5 Milestones achieved by company, awards, certifications etc.

The Company is under of Central mainstay of incorporation.
3.6 Marketing Scenario of company

Marketing management is a process of controlling the marketing aspects, setting the
goals of a company, organizing the plans step by step, taking decisions for the firm,
and executing them to get the maximum turn over by meeting the consumers'
demands. There are many ways we reach an audience such as email marketing, social
media marketing, digital marketing and public relations.
3.7 Human Resource Scenario of company

The roles and responsibilities of HR are not just limited to a particular domain but it is
spread over the overall functionality of a company. Their role will slightly differ
depending on the size of the company and type of industry but it is more than just
administrative responsibilities which is a common misconception. It ranges from
human resource planning, recruitment and selection, employee support and welfare to
ensuring personal well-being, health and safety of employees and a lot more.
3.8 Research and Development

Research and Development(R&D) is the key element of many organizations. When it
is well planned and used it enables a business to generate increased wealth from time
to time. Most of the people associates the research and development function of a
company with the invention of new project. Overall Research and Development is
important for a firm to gain knowledge to develop, design, enhance, and modify
company’s products, services, technologies, business plans, processes and sometimes
vision. Research and Development plays an important role in enhancing the capability
of companies because they stimulate innovative methods of production, reduce costs
and improve product quality.

3.9 Competitors Information

1. Refresh Infratech Pvt. Ltd.
2. I-Soft Software Solution Pvt. Ltd.
3. Varad It Solution
4. Jijauit solution & services
3.10 Future Plans of the Organization
1. To provide proper as well as quick services to the customers.
2. To solve maximum problems in minimum time of period.
3. To become a successful organization in an information technology sectors.
4. Daily innovations and daily satisfactions.
3.11 Organization Chart:
CEO
Development
QA management HR & operation Finanace
management
team management department
team
Development
team QA team

CHAPTER NO. 4
ANALYSIS AND INTERPRETATION OF DATA
4.1 Introduction:
This chapter include the data analysis and interpretation of Qlogiciel

technologies Pvt. ltd Satara. Interpretation is the result of analysis, which
enables conversion of data in to statement, propositions, or conclusions, which
ultimately completes the research objectives. This chapter deals with data
processing, tabulation, presentation, analysis and interpretation of data.
4.2Analysis and interpretation of data

Data analysis deals with analysis of whole data collected through various
techniques. Researcher hasanalyzed the data with the help of tables and
graphs.The researcher has selected 32 Employees as a sample for research
purpose.

4.2.1 Basic purpose of using JIRA Tool:
Table no.: 4.2.1
Basic purpose of using JIRA Tool
Sr.No. Features No. of responds Percentage (%)

1 Bug Management Tool 13 41
2 Content Management tool 6 19
3 Project Management Tool 6 19
4 Test case management Tool 7 21
Total 32 100
Graph No:4.2.1
Basic Purpose of Using JIRA Tool
14 41%
12
10
8 21%
19% 19%
6
4
2
0
Bug Management Content Project Test case
Tool Management Tool Management Tool management Tool
Basic Purpose of Using JIRA Tool
Interpretation:
From the above graph the basic purpose of using JIRA Tool is observed that the
mainly 3 purposes in parameters. i.e., bug management tool, content management tool
and project management tool .In above observation the first basic purpose is bug
management41% uses that is high ranking for using JIRA tool. Then content
management tool is 19% and project management tool is also 19% and all these 3
parameters have 21% basic purpose of using JIRA tools.

4.2.2 Use of JIRA tool for the organization:
Table no. 4.2.2
Use of JIRA tool for the organization

1 To improve QA process 5 15
To make a centralized location to
2 5 15
store project details
3 To improve development process 17 55
4 Above All 5 15
Total 32 100
Graph No. 4.2.2

Use of JIRA Tool for the organization
18 55%
16
14
12
10
8
6 15% 15% 15%
4
2
0
To improve QA To make a To improve Above All
process centralized location development
to store project process
details
The use of JIRA Tool for the organization
Interpretation:
From the above graph the use of JIRA Tool for organization is observed that the
mainly 3 purposes in parameters. i.e., to improve QA process, to make a centralized
location to store project details and to improve development process.In above
observation the first use of JIRA tool for organization is to improve development
process 55% that is high ranking . then to improve QA process is 15% and to make a
centralized location to store project details is also 15% and all these 3 parameters
have 15% the use of JIRA tools for the organization.

4.2.3 The reason behind using JIRA software
Table No. 4.2.3
Reason behind using JIRA software
Sr. Strongly Strongly

Reasons Agree Neutral Disagree
No. Agree Disagree
Upfront and fair
1 15 15 50 12 8
licensing policy
Features that is not
2 28 32 22 12 6
available elsewhere
Get the latest update
3 on the progress of 34 22 16 16 12
projects
Itruns anywhere and
4 recognized with many 12 10 34 22 22
famous companies
Easily extensible and
5 12 18 40 18 12
customizable
Graph No. 4.2.3

Reason behind using JIRA
18
50%
16
14
40%
12 34% 34%
32%
10 28%
8 22% 22% 22%
22%
18% 18%
6 15%
15% 16%16%
12% 12% 12% 12% 12% 12%
4 8% 10%
6%
2
0
Upfront and fair Features that is Get the latest It runs anywhere Easily extensible
licensing policy not available update on the and recognized and customizable
elsewhere progress of with many famous
projects companies
Strongly agree Agree Neutral Strongly disagree Disagree

Interpretation:
From the above graph the reason behind using JIRA Tool is observed that the mainly
5 purposes in parameters. i.e., Get the latest update on the progress of project, It runs
anywhere and recognized with many famous companies, Easily extensible and
customizable, Feature that is not available elsewhere and Upfront and fair licensing
policy.
In above observation the first reason behind using JIRA tool isGet the latest update on
the progress of projects is 34% uses that is high ranking reason. ThenFeatures that is
not available elsewhere is 28% and Upfront and fair licensing policy is 15% and
Itruns anywhere and recognized with many famous companies is 12% and last Easily
extensible and customizable is 12%.

4.2.4 The most useful tool for the bug tracking.
Table No. 4.2.4
Most useful tool for the bug tracking

1 INTELLIJ 5 15
2 SQL 10 32
3 HPQC 7 21
4 JIRA 10 32
Total 32 100
Graph No. 4.2.4

Most useful tool for the bug tracking
12
32% 32%
10
8 21%
6 15%
4
2
0
INTELLIJ SQL HPQC JIRA
Most useful tool for the bug marketing
Interpretation:
From the above graph the most useful tool for the bug marketing is observed that the
mainly 4 purposes in parameters. i.e., INTELLIJ, SQL, HPQC, JIRA.
In above observation the first most useful tool for bug marketing is SQL 32% and
JIRA is also 32% that is high ranking. HPQC is 21% useful and INTELLIJ is 15%
useful tool for the bug marketing.

4.2.5 – The problem face while using JIRA tool in organization.
Table no.: 4.2.5
Problem face while using JIRA tool in organization.

Excel is still required ; JIRA cannot
1 16 50
provide me everything need
Complex workflow and to many
2 9 29
required fields
3 The many views confuse the users 5 15
4 It takes a lot of time to load page. 2 6
Total 32 100
Graph No. 4.2.5

Problems face while using JIRA tool in organization
18 50%
16
14
12
10 29%
8
6 15% 6%
4
2
0
Excel is still Complex workflow and The many views confuse It takes a lot of time load
required;JIRA cannot to many required fields the users page
provide me everything
need
Problems you face in while using JIRA tool in organisation
Interpretation:
From the above graph the problems facewhile using JIRA tool in organization is
observed that the mainly 4 purposes in parameters. i.e., Excel is still required JIRA
cannot provide me everything need, complex workflow and to many required fields,
The many views confuse the users and It takes a lot of time to load page.

4.2.6 - Rank view on whether employees agree or not with the Jira tool features
for agile team
Table no. 4.2.6
JIRA tool features for agile team
No. of Responses in percentage (%)

Sr.
Parameters Strongly Strongly
No. Agree Neutral Disagree
agree disagree
1 Issues tracking 41 41 6 12 0
Customizable 12
2 6 28 22 32
workflow
Estimation and 12
3 16 34 22 16
work logging
Progress 15
4 15 23 32 15
reporting
7
5 Scrum board’s 18 22 28 25
6 Kanban boards 18 22 18 25 17
7 Project level 12 10 34 22 22
permission
8 Project backlog 16 16 28 22 18
9 Email 12 18 40 18 12
notification
10 Roadmaps 18 38 3 12 28

Graph no.: 4.2.6
JIRA tool features for agile team
Strongly disagree Disagree Neutral Agree Strongly agree
12% 28%
Roadmaps 3%
18% 38%
18% 18%
Email notification 40%
12% 18%
18% 22%
Project backlog 28%
16%16%
22% 2…
Project level permission 25%
10% 12%
17%
Kanban boards 18% 22%25%
18%
7% 25% 2…
Scrum board’s
18% 22%
15% 5
Progress reporting 32%
15% 2…
12%16%
Estimation and work logging 22%
16% 34%
12% 32%
Customizable workflow 22%
6% 28%
0 12%
Issues tracking 6% 41% 41%
0 2 4 6 8 10 12 14
Interpretation:
From the above conclude that rank view for jira tool features are included in the
analysis and interpretation of data. In the issue tracking high response from the
employees is strongly agree in 41%. In the customizable workflow high response
from the employees is disagree in 32%. In the estimation and work logging high
response from the employees is agree in 34%. In the progress reporting high response
from the employees is neutral in 32%. The scrum board high response from the
employees is neutral in 28%. In the Kanban boards high response from the employees
is disagree in 25%. The project level permission high response from the employees is
neutral in 34%. In the project backlog high response from the employees is neutral in
28%. The Email notification high response from the employees is neutral in 40%. In
the roadmaps high response from the employees is agree in 38%.

4.2.7: You have any option to create different version of same project in JIRA
Table no.:4.2.7
Any option to create different version of same project in JIRA
Sr.No. Parameter No. Of Responds Percentage(%)
1 Yes 23 72
2 No 9 28
Total 32 100
Graph no. 4.2.7

Any option create different version of same project in JIRA
28% Yes
No
72%
Interpretation:
From the above conclude that to create different version of same project in JIRA.
In above table and graph showing 72% of employees are said that there is an option to
create different version of same project in JIRA and should be implemented in so
create different version else remain 28% employees are thinking opposite and not
agreed to implement.

4.2.8 Is it possible to access JIRA cloud site via a mobile device.
Table N o.4.2.8
Possible to access JIRA cloud site via a mobile device
Sr.No. Parameters No. of Responds Percentage (%)

1 Yes 21 66
2 No 11 34
Total 32 100
Graph No. 4.2.8

Possible to access JIRA cloud site via a mobile device
Yes
34%
no
66%
Interpretation:
In above table and graph showing 66% of employees are thinking like Is it possible to
access JIRA cloud site via a mobile device and should be implemented in so
development company else remain 34% employees are thinking opposite and not
agreed.

4.2.9: we create duplicate copy of any issue in the Jira.
Table no.: 4.2.9

Create duplicate copy of any issue in the Jira
Sr. No. Parameters No. of Responds Percentage (%)
1 Yes 17 54
2 No 15 46
Total 32 100
Graph no. 4.2.9

Create duplicate copy of any issue in the JIRA
Yes no
46%
54%
Interpretation:
In above table and graph showing 54% of employees are thinking like create duplicate
copy of any issue in the Jira and should be implemented in so development company
else remain 46% employees are thinking opposite and not agreed.

CHAPTER No. 5
FINDING, SUGGESTIONS AND CONCLUSION
5.1 Findings:
5.1.1 41% employees said that the basic purpose of using JIRA tool is Bug
Management. (Table No. 4.2.1)
5.1.2 55% employees said that the use of JIRA tool for the organization is to improve
development process. (Table No. 4.2.2)
5.1.3 50% employees said that in the organization the reason behind using JIRA is
easily extensible and customizable. (Table No. 4.2.3)
5.1.4 32% employees said that most useful tool for bug management is SQL and
JIRA. (Table No. 4.2.4)
5.1.5 50% employees said that the problem face in while using JIRA tool in
organization that is excel is still required ; JIRA cannot provide me everything need.
(Table No. 4.2.5)
5.1.6 The JIRA tool features for agile team is having the result is issue tracking for
strongly agree in (Table No. 4.2.6)
5.1.7 Have any option to create different version of same project in JIRA the having
result from employees is yes in percentage response is 72% in (Table no. 4.2.7)
5.1.8 It is possible to access JIRA cloud site via a mobile device the having result
from employees is yes in 72%. (Table No. 4.2.8)
5.1.9 We create duplicate copy of any issue in the Jira result find is 54% employees
responded yes and 46% responses no. (Table No. 4.2.9)
5.2 Suggestions:
1. Teams can create custom workflows to drive the progression of issues on a

scrum or kanban board.
2. Time tracking allows teams to record the amount of time they spend working
on issues.
3. Scrum boards enable teams to manage their sprints and backlog.

4. A kanban board allows teams to visualize the flow of work and limit work in

progress.
5. A backlog contains outstanding issues for a team to work on.
6. Roadmaps create a visual representation of all the epics a team is working on,
so teams can plan large pieces of work in advance.
5.3 Conclusion:
During the internship of completing a project, issues will always come up. In a
software project, developers call these issues bugs. A bug or any other type of
issue is a source of delay that can impact successful project delivery. Jira remains
to be a viable solution among development teams. Businesses of various sizes
across industries are need to further their cause, methodologies, and disciplines
with the help of the software. It can be concluded that a software project has too
much workload, employees are needed communicate to each other, they get easily
understands the issues and helps to the reducing bugs and errors in project. There
is need to knowledgeable human resource, tools and equipment for reducing
connectivity issues.

APPENDICES
BIBLIOGHRAPHY
1. Books:
LI, L. (2018). Jira software essentials. UK: Packt Publishing.
Load, C. (2017). Scrum your jira!. UK: Kindeel.
2. Website:
atlassian-exploring. (n.d.). Retrieved Jan 2, 2022, from atlassian: www.atlassian.com
softwaretestinghelp/ info-jira. (n.d.). Retrieved Dec 20, 2021, from

softwaretestinghelp: www.softwaretestinghelp.com

Jira Project Yashoda CLG

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

Jira Project Yashoda CLG

Uploaded by

Copyright:

Available Formats

Shivaji University, Kolhapur

1.3 Statement of Research Problem:

1.4Objective of the Study:

YSPM’S Yashoda Technical Campus, Satara Page. 1

1.5 Scope of the Study:

1.6 Importance of the Study:

1.7 Research Methodology:

YSPM’S Yashoda Technical Campus, Satara Page. 2

1.7.2.2. Secondary Source:

In appendices contains Bibliography and Questionnaire.

YSPM’S Yashoda Technical Campus, Satara Page. 3

2.1 Introduction of JIRA software testing tool:

2.1.1 What is Jira Testing Tool?

2.1.2 Audience of Jira Testing Tool

YSPM’S Yashoda Technical Campus, Satara Page. 4

2.2 Features of Jira Testing Tool:

Given below are some of the fascinating features:

2.3 Uses of Jira Testing Tool:

2. Organize and Allocate

YSPM’S Yashoda Technical Campus, Satara Page. 5

3. Track Bugs and Solve

2.4 Jira Test Case Management:

2.5 Differences in Test Case Approaches:

In my experience after reviewing thousands of test case approaches and

2.6 How an Issue Created in Jira:

Whenever an issue or defect is encountered while testing, it needs to be reported so

YSPM’S Yashoda Technical Campus, Satara Page. 7

2.7Jira for Requirements & Test Case Management:

2.7.1Jira for agile teams:

YSPM’S Yashoda Technical Campus, Satara Page. 8

2.7.2 Jira for project management teams:

1. Issue and task management

2.7.3 Jira For Software Development Teams:

2.8 What Is Roadmap In Jira:

YSPM’S Yashoda Technical Campus, Satara Page. 9

2.8.1 What Is Backlog In Jira:

Your backlog is a list of tasks thatrepresents outstanding work in a project. Usually, a

2.8.2 Purpose of Jira Tool:

YSPM’S Yashoda Technical Campus, Satara Page. 10

2.Gaining confidence in and providing information about the level of quality.

3.To prevent defects.

YSPM’S Yashoda Technical Campus, Satara Page. 11

3.1 Name of the unit

3.2 Location or Address of the Unit

Name of the Company Qlogiciel technologies Pvt ltd. Satara

Address Plot No.43, S.N. 20K, Lakshmi Vihar Building, Visawa

E-mail Address info@qlogiciel.com

Phone Numbers +02162-231119

3.3 Brief History of the Unit & Present Position

YSPM’S Yashoda Technical Campus, Satara Page. 12

3.4 Strategic Intend of company

3.4.2 Mission of company:

3.4.3 Vision of company:

1 Delivery of Product and Services which are globally competitive.

YSPM’S Yashoda Technical Campus, Satara Page. 13

3 Continuous improvement in service quality, long – term customer

3.5 Milestones achieved by company, awards, certifications etc.

3.6 Marketing Scenario of company

3.7 Human Resource Scenario of company

3.8 Research and Development

YSPM’S Yashoda Technical Campus, Satara Page. 14

3.9 Competitors Information

3.10 Future Plans of the Organization