MCQs on Issues and Workflows | Jira MCQs Question Answers
Jira is a powerful tool for project management, especially in agile environments. Understanding how to manage issues, epics, tasks, and subtasks effectively, along with customizing workflows, statuses, transitions, and resolutions, is key to streamlining your workflows and enhancing productivity. This set of MCQs will test your knowledge on these concepts.
Managing Issues, Epics, Tasks, and Subtasks
- What is the main purpose of creating an Epic in Jira?
a) To track user stories related to a feature
b) To manage high-level project tasks
c) To manage an entire project timeline
d) To track individual bugs - What type of issue can be created as a subtask?
a) Epic
b) Task
c) Story
d) Bug - Which of the following issue types is usually used to track project-level work?
a) Subtask
b) Epic
c) Task
d) Story - How do you assign an Epic to an issue in Jira?
a) By linking the issue to the Epic
b) By creating a subtask under the Epic
c) By changing the issue type to Epic
d) By using a custom field - Which Jira issue type is typically used to track individual, actionable items?
a) Task
b) Epic
c) Subtask
d) Story - Which of the following is a default issue type in Jira?
a) Task
b) Feature
c) Request
d) Test - What relationship is used to connect a subtask to its parent task in Jira?
a) Parent-Child
b) Dependency
c) Link
d) Blocked - What is the primary benefit of creating subtasks in Jira?
a) To split large tasks into manageable pieces
b) To create dependencies between tasks
c) To track different versions of the same task
d) To allow for easier reporting - Which Jira field is typically used to assign a task to a specific person?
a) Assignee
b) Reporter
c) Creator
d) Owner - What does the “Fix Version” field in Jira typically represent?
a) The release version of a feature or bug fix
b) The target completion date for an issue
c) The priority of an issue
d) The estimated effort for the issue
Customizing Workflows: Statuses, Transitions, and Resolutions
- What is a Jira workflow?
a) A sequence of issue types in a project
b) A process through which an issue progresses
c) A set of conditions applied to issues
d) A method to track time for an issue - Which of the following is a default status in a Jira workflow?
a) Approved
b) In Progress
c) Completed
d) Delayed - What is the purpose of a transition in a Jira workflow?
a) To mark an issue as complete
b) To move an issue from one status to another
c) To assign an issue to a person
d) To delete an issue - How can you customize the resolution field in Jira?
a) By modifying the workflow resolution settings
b) By creating custom workflows for each issue type
c) By setting resolution options in the project settings
d) By creating custom issue types - Which of the following is true about Jira workflow statuses?
a) Statuses must always be sequential
b) Statuses can be customized but cannot be deleted
c) Statuses are fixed and cannot be customized
d) Only one status can be active at any time - What does the “Done” status in a Jira workflow usually indicate?
a) The issue is still under review
b) The issue has been completed and verified
c) The issue has been temporarily suspended
d) The issue is being worked on by a different team - What happens when an issue is transitioned to the “In Progress” status?
a) The issue is removed from the backlog
b) The issue is considered blocked
c) The issue starts being worked on
d) The issue is closed - Which of the following is the most common reason for configuring custom workflow transitions in Jira?
a) To manage issue priorities
b) To define which issues are visible in reports
c) To reflect business-specific processes
d) To set user permissions - How does the “Resolution” field function in a Jira issue?
a) It indicates the steps needed to complete the task
b) It reflects the cause of an issue’s closure
c) It stores the status of the issue
d) It tracks the estimated time for the issue - What does the “In Review” status typically mean in a workflow?
a) The task is in progress
b) The task has been completed and is waiting for verification
c) The task is blocked due to external dependencies
d) The task is in the backlog awaiting attention
Linking and Bulk Operations on Issues
- How can you link two issues together in Jira?
a) By using the “Link Issue” function
b) By creating a subtask for the second issue
c) By assigning the same person to both issues
d) By using a common component - Which of the following is an example of a valid issue link in Jira?
a) Blocked By
b) Work In Progress
c) In Review
d) Issue Linked - What is the purpose of the “Bulk Change” feature in Jira?
a) To delete multiple issues simultaneously
b) To assign multiple issues to a single user
c) To edit multiple issues at once
d) To change the issue type in bulk - Which action can be performed using Jira’s bulk operations?
a) Change issue priority for multiple issues
b) Change issue types for all issues in a project
c) Delete issues in bulk
d) All of the above - When performing a bulk operation, which permission is required?
a) Admin permissions only
b) Bulk change permissions
c) Project management permissions
d) Custom issue editing permissions - What does the “Linked Issues” section in Jira show?
a) A list of all issues assigned to the same user
b) A list of all issues related to a parent issue
c) A list of issues that are connected to the current issue
d) A list of issues within the same project - How can you edit multiple issues at once in Jira?
a) By selecting issues and clicking the “Bulk Change” option
b) By using the “Quick Edit” mode
c) By selecting multiple issues and using “Link Issue”
d) By editing the project settings - What does the “Resolve” option do in a bulk operation?
a) It marks all selected issues as completed
b) It links issues to other issues
c) It deletes the issues from the system
d) It assigns issues to a user - How can you automate the linking of issues in Jira?
a) By using custom scripts in Jira
b) By configuring workflow triggers
c) By creating custom issue types
d) By using the “Bulk Link” feature - Which Jira feature allows for executing actions on many issues at once?
a) Issue Linking
b) Bulk Change
c) Issue Search
d) Workflow Automation
Answer Key
| QNo | Answer (Option with the text) |
|---|---|
| 1 | a) To track user stories related to a feature |
| 2 | b) Epic |
| 3 | b) Epic |
| 4 | a) By linking the issue to the Epic |
| 5 | a) Task |
| 6 | a) Task |
| 7 | a) Parent-Child |
| 8 | a) To split large tasks into manageable pieces |
| 9 | a) Assignee |
| 10 | a) The release version of a feature or bug fix |
| 11 | b) A process through which an issue progresses |
| 12 | b) In Progress |
| 13 | b) To move an issue from one status to another |
| 14 | c) By setting resolution options in the project settings |
| 15 | b) Statuses can be customized but cannot be deleted |
| 16 | b) The issue has been completed and verified |
| 17 | c) The issue starts being worked on |
| 18 | c) To reflect business-specific processes |
| 19 | b) It reflects the cause of an issue’s closure |
| 20 | b) The task has been completed and is waiting for verification |
| 21 | a) By using the “Link Issue” function |
| 22 | a) Blocked By |
| 23 | c) To edit multiple issues at once |
| 24 | d) All of the above |
| 25 | b) Bulk change permissions |
| 26 | c) A list of issues that are connected to the current issue |
| 27 | a) By selecting issues and clicking the “Bulk Change” option |
| 28 | a) It marks all selected issues as completed |
| 29 | b) By configuring workflow triggers |
| 30 | b) Bulk Change |