Software Bug Tracking using JIRA for Small Business Website

This report focuses on software bug tracking within the context of a small business website, utilizing JIRA as the primary tool. It begins with an introduction to the importance of bug tracking in software development, defining bugs and bug tracking processes. The report then describes JIRA software, its features, and its suitability for bug tracking. The report identifies key bugs to be considered, including compatibility issues across different browsers, responsiveness problems on various devices, and functionality errors in links, buttons, and forms. The roles of a software tester and a system developer in the bug tracking and fixing process are explained. Finally, the report outlines bug-related information, such as browser compatibility, device responsiveness, and error messages, to confirm the presence of bugs. The references used in the report are also mentioned at the end.

Running Head: SOFTWARE BUG TRACKING 1
SOFTWARE BUG TRACKING
Student Name
Institution
Course
Date

SOFTWARE BUG TRACKING 2
Introduction
In the current era where cybersecurity has become a threat to information systems, bug
tracking is a very important aspect in the development and deployment of IT systems. Bugs are
defined as the issues which arise in the design, requirement, specifications and coding of a
system that may lead to incorrect results. On the other hand, bug tracking is defined as the
process of capturing, reporting and managing errors and exceptions that occur in the software
development process. it is one of the most important steps of software development without
which the whole process is incomplete. For every project to maintain quality, save time and
resources, bug tracking is very important. Bug tracking entails two services: task management
systems and bug capturing tools. These two services work hand in hand to ensure that the
software delivered is of high quality, reduce the cost of development, smooth communication
among the developers, detection of software issues early enough and lastly to ensure that
customers or users of the system are satisfied. This paper describes how bug tracking will be
achieved in a small business website using JIRA software (Wright, 2016).
Description of JIRA Software
JIRA is Atlassian software that had been developed primarily as an incident management
tool and a bug tracking tool. The software provides complete recording, reporting and other
workflow related features. It integrates fully in different code development platforms, a feature
that makes it a perfect tool for developers (Wright, 2016). In 2003, tracking and management of
bug features were added to this software. Since then, it has kept expanding to help developers
track all the aspects of the software development process, from release management to backlog
grooming.

SOFTWARE BUG TRACKING 3
Although there are many bug tracking tools available in the market, JIRA’s excellent
planning features, comprehensive search functions and powerful workflow engine is
incomparable to any of them With JIRA, bugs can be captured anywhere in the software and
once identified, it allows creation of an issue to gather all the relevant details of the bug
including description, severity and screenshots. Due to its capability to track any kind of issues,
it is capable of supporting agile projects (Wright, 2016).
Description of Bugs to be considered
Being a website which is expected to be used by different users with different preferences
and tastes for browsers, the first bug to be considered will be its compatibility problems in
different browsers such as Mozilla, Chrome and Opera. Different browsers have different
features which must match with the browser where the website will be optimized. In a case
where the website has sections which are not supported by a certain browser, it is expected that
the appearance will be different in such a browser (Error, Error & Curran, 2019).
It is also expected that the website should be responsive in different devices hence the
second bug will be based on the responsive mistakes. The website is expected to work in both
small screens like mobile screens and large screens like desktop screens. However, the developer
might test it in one among those screens and assume it is okay, which is not the case in the other
screen (Kanij, Merkel & Grundy, 2015).
All the site links, buttons and forms will be tested to ensure that they are working as
expected. Many are the times during website development that developers use place holders for
forms, links and buttons. Placeholders are used in this case to just make the layout look like it
should be. They, however, tend to forget and can end up submitting the projects to clients

SOFTWARE BUG TRACKING 4
because pages are looking right. Clicking everything is hence very important because it confirms
that all the functionalities of the website are met (Error, Error & Curran, 2019).
Description of who will track the bugs and Implement bug fixes
Bugs in the website will be tracked by a software tester. A software tester is a person
involved in the quality assurance stage of software development and deployment and whose
main role is to conduct automated and manual tests on software or a system to ensure that it fits
the purpose by identifying any issues or bugs which might be compromising the functionality of
the system (Li et al., 2019). Through that, potential risks on the system are averted and any
vulnerability which might be exploited to cause harm in future. The bugs identified will be
reported to the system developer who is the only person aware of the coding and how the site has
been organized to fix the bugs identified by the software tester (Karre, Shukla & Reddy, 2017).
Description of bug-related information
The website should be working on different browsers such as Chrome, Mozilla and
Opera. However, if the website fails to work on a certain browser, it will be an indication that the
website has some sections which are not supported by the browser features. In that case, the
website is confirmed to have bugs which must be removed for it to work well (Tamura &
Yamada, 2016). The website is also expected to be responsive to different browsers and devices.
In a case where it changes appearance when a browser is minimized or does not work in some
devices, it is an indication that the website is not responsive as expected. Lastly, when a click on
certain links, forms or buttons returns an error message, it is a confirmation that the website has
some bugs.

SOFTWARE BUG TRACKING 5
References
Error, B., Error, C., & Curran, B. (2019). U.S. Patent Application No. 10/205,623.
Kanij, T., Merkel, R., & Grundy, J. (2015, May). An empirical investigation of personality traits
of software testers. In Proceedings of the Eighth International Workshop on Cooperative
and Human Aspects of Software Engineering (pp. 1-7). IEEE Press.
Karre, S. A., Shukla, A., & Reddy, Y. R. (2017). Does your bug tracking tool suit your needs? a
study on open source bug tracking tools. arXiv preprint arXiv:1706.06799.
Li, H., Gao, G., Chen, R., Ge, X., Guo, S., & Hao, L. Y. (2019). The influence ranking for testers
in bug tracking systems. International Journal of Software Engineering and Knowledge
Engineering, 29(01), 93-113.
Tamura, Y., & Yamada, S. (2016, September). Reliability analysis based on deep learning for
fault big data on bug tracking system. In 2016 5th International Conference on
Reliability, Infocom Technologies and Optimization (Trends and Future Directions)
(ICRITO) (pp. 31-36). IEEE.
Wright, R. (2016). JIRA Strategy Admin Workbook: Templates for the application administrator
to set up, clean up, and maintain JIRA. CreateSpace Independent Publishing Platform.