Jira-SoftwareTestingMaterial.cJira-SoftwareTestingMaterial.com Questions and Answers 2024/2025om Questions and Answers 2024/2025
1 view 0 purchase
Course
Jira Administrator
Institution
Jira Administrator
What is JIRA?
JIRA is an issue tracking product developed by Atlassian which allows bug tracking
and agile project management. The name "JIRA" is inherited from the word Gojira, the
Japanese word for Godzilla, which is a reference to a competitor Bugzilla.
2. Why is JIRA used?
Atlass...
Jira-SoftwareTestingMaterial.com
Questions and Answers 2024/2025
1. What is JIRA?
JIRA is an issue tracking product developed by Atlassian which allows bug tracking
and agile project management. The name "JIRA" is inherited from the word Gojira, the
Japanese word for Godzilla, which is a reference to a competitor Bugzilla.
2. Why is JIRA used?
Atlassian JIRA is an issue tracking and agile project management tool which allows us
to track any project by following a proper workflow. Following are the reasons behind
using JIRA.
JIRA is a platform independent that could run anywhere
JIRA can be run anywhere
In JIRA, a workflow can be easily customized based on our requirement
JIRA acts as an issue tracking as well as project management tool
JIRA allows us to track the progress of a project from time to time
3. What are the differences between JIRA and Bugzilla?
JIRA and Bugzilla are the two bug tracking tools that are widely being used by
several organizations for quite some time now.
JIRA BUGZILLA
JIRA is a commercial tool Bugzilla is an open source tool
JIRA is a user friendly tool compared to Bugzilla Bugzilla is not so friendly tool compared to
JIRA
Drag and drop issue prioritization is available in JIRA Drag and drop issue prioritization is not
JIRA has configurable link types with user-defined semantics. JIRA also has pluggable remote
issue links, that allow to link an issue to any other entity outside JIRA Bugzilla has only one link
type: blocks/depends, plus a Bug ID custom field
Unlike Bugzilla, JIRA allows to define multiple workflows which are applied based on the
issue's Project and Type Unlike JIRA, Bugzilla can let users select the initial status of a new
issue
Custom field types available in JIRA are too many to list, and even more custom field types
available from plugins Custom field types available in Bugzilla are Text fields, Multi-selection,
Drop-down, Date/time, Bug ID
JIRA allows conditional configuration based only on Project and Type fields Bugzilla lets you
show/hide the whole custom field or specific values based on the value of some other field
JIRA lacks advance-level search options. JIRA has flexible JQL language (JIRA Query
Language) that allows you to build arbitrary boolean expressions Bugzilla's comes with a
powerful advanced search option
4. Can Jira be used for test case management?
Although JIRA was not designed to serve as a Test Case Management, it can be
configured to support test case management in two different ways.
You can either change native components in JIRA to meet test case management needs or you
can use one of the add-ons available in Atlassian Marketplace (Example: Zephyr of JIRA)
Workflow is defined as a series of sequential tasks that need to be completed in
order to reach a certain goal. A workflow in JIRA is defined as a series of sequential
tasks (such as create/open a bug, Work in progress, and completed/closed) involved
in the life cycle of a bug or an issue.
Create: Create an issue or bug
Work in progress: Series of actions performed to fix the issue
Closed: Completion of the issue after verification
JIRA Workflow
6. Explain working with workflows in JIRA?
A JIRA workflow is a set of statuses and transitions that an issue travels through during
its lifecycle and normally represents processes within your organization. There are pre-
defined built-in workflows that can't be edited; however, you can copy and utilize
these workflows to create your own.
Working with Workflows in JIRA
7. What are the limitations when editing an active workflow?
Limitations apply when editing the draft for an active workflow:
It is not possible to edit the workflow name
Workflow statuses cannot be deleted
If a status has no outgoing transitions, it cannot have any outgoing transitions added, regular
or global
The step ID cannot be changed
8. What is a Workflow designer in JIRA?
1|Page| GradeA+ | 2 0 0 2 5
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller TestTrackers. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $12.49. You're not tied to anything after your purchase.
