Jira-SoftwareTestingMaterial.com- Questions
with Correct Answers
1. Why an issue is labeled in JIRA? ✔️✔️Labeling an issue in JIRA allows you to find which
category an issue belongs to. Issues can be easily searched with the help of labels. Labels can be
initially set at the time of creating the issue. It can also be modified if required.
2. How is an issue linked in JIRA? ✔️✔️Linking means establishing the relationship between the
two. In JIRA, an issue can be linked with other issues on either the same or different JIRA
servers.
An issue can be linked with other issues as follows
An issue may relate to another issue
An issue may duplicate another issue
An issue may block another issue
3. What is the use of Move Issue wizard in JIRA? ✔️✔️Move Issue wizard enables you to specify
another project in your JIRA instance. The Move Issue wizard permits you to change certain
attributes of the issue such as Issue Type, Issue Status, and Custom Fields.
Issue Type: If your issue is a custom issue type that does not exist in your target project, you
must choose a new issue type.
Issue Status: If you have assigned a custom status to your issue, and it does not exist in your
target project, you must select a new issue status for your issue.
Custom Fields: If you have defined required custom fields for your issue that does not exist in
your target project, you must set values for them.
4. How to schedule an issue in JIRA? ✔️✔️To schedule an issue, populate its Due date field. This
can be done either when creating an issue, or at a later stage by editing the issue. Only users
with the schedule issues permission can populate the Due date field.
5. How project details are listed in JIRA? ✔️✔️All the projects have some attributes that are
displayed under the project summary section.
, The list of attributes in JIRA is
Nature of the project
Keys for the project
Components
Version
6. What are the issues types in JIRA? ✔️✔️Each Jira application comes with default issue types.
You can use these default issue types or create your own to suit the needs of your projects and
teams.
Here's an example of specific issue types within each Jira application:
Jira Core default issue types:
Task - Task that needs to be done
Subtask - Smaller task within a larger piece of work
Jira Software default issue types
Story - Functionality request expressed from the perspective of the user
Bug - Problem that impairs product or service functionality
Epic - Large piece of work that encompasses many issues
Jira Service Desk default issue types
Incident - System outage or incident
Service request - General request from a user for a product or service
Change - Rollout of new technologies or solutions
Problem - Track underlying causes of incidents
7. What is Cloning an Issue in JIRA? ✔️✔️Cloning, or copying, an issue lets you quickly create a
duplicate of an issue within the same project. The clone issue is a replica of the original issue,
containing the same information stored in the original issue — e.g. Summary, Affects Versions,
Components, and so on. The clone issue can likewise be connected to the original issue.
A clone issue is a different entity from the original issue. Tasks of the original issue has no
impact on the cloned issue and vice versa.
with Correct Answers
1. Why an issue is labeled in JIRA? ✔️✔️Labeling an issue in JIRA allows you to find which
category an issue belongs to. Issues can be easily searched with the help of labels. Labels can be
initially set at the time of creating the issue. It can also be modified if required.
2. How is an issue linked in JIRA? ✔️✔️Linking means establishing the relationship between the
two. In JIRA, an issue can be linked with other issues on either the same or different JIRA
servers.
An issue can be linked with other issues as follows
An issue may relate to another issue
An issue may duplicate another issue
An issue may block another issue
3. What is the use of Move Issue wizard in JIRA? ✔️✔️Move Issue wizard enables you to specify
another project in your JIRA instance. The Move Issue wizard permits you to change certain
attributes of the issue such as Issue Type, Issue Status, and Custom Fields.
Issue Type: If your issue is a custom issue type that does not exist in your target project, you
must choose a new issue type.
Issue Status: If you have assigned a custom status to your issue, and it does not exist in your
target project, you must select a new issue status for your issue.
Custom Fields: If you have defined required custom fields for your issue that does not exist in
your target project, you must set values for them.
4. How to schedule an issue in JIRA? ✔️✔️To schedule an issue, populate its Due date field. This
can be done either when creating an issue, or at a later stage by editing the issue. Only users
with the schedule issues permission can populate the Due date field.
5. How project details are listed in JIRA? ✔️✔️All the projects have some attributes that are
displayed under the project summary section.
, The list of attributes in JIRA is
Nature of the project
Keys for the project
Components
Version
6. What are the issues types in JIRA? ✔️✔️Each Jira application comes with default issue types.
You can use these default issue types or create your own to suit the needs of your projects and
teams.
Here's an example of specific issue types within each Jira application:
Jira Core default issue types:
Task - Task that needs to be done
Subtask - Smaller task within a larger piece of work
Jira Software default issue types
Story - Functionality request expressed from the perspective of the user
Bug - Problem that impairs product or service functionality
Epic - Large piece of work that encompasses many issues
Jira Service Desk default issue types
Incident - System outage or incident
Service request - General request from a user for a product or service
Change - Rollout of new technologies or solutions
Problem - Track underlying causes of incidents
7. What is Cloning an Issue in JIRA? ✔️✔️Cloning, or copying, an issue lets you quickly create a
duplicate of an issue within the same project. The clone issue is a replica of the original issue,
containing the same information stored in the original issue — e.g. Summary, Affects Versions,
Components, and so on. The clone issue can likewise be connected to the original issue.
A clone issue is a different entity from the original issue. Tasks of the original issue has no
impact on the cloned issue and vice versa.