In Jira Cloud, you have company-managed kanban project, there are a total of seven statuses in the workflows. Which statement about the kanban board is true?
A. The board can include only statuses that are in every workflow
B. The board can have multiple in Progress statuses, from different workflows, mapped to the same column
C. The board must have the backlog and epic panel enabled
D. The board must have at least seven columns
The correct answer is:
B. The board can have multiple in Progress statuses, from different workflows, mapped to the same column
Explanation:
In your Jira Cloud kanban project with seven statuses, you have some flexibility in how you set up the board, and no single statement definitively captures the entire truth. However, based on the information provided, we can analyze each statement further:
The board must have at least seven columns: Not necessarily true. You can group the seven statuses logically into fewer columns if it makes sense for your workflow. Jira allows mapping multiple statuses to a single column.
The board must have the backlog and epic panel enabled: Depends on your setup. These are optional features. The backlog panel is typically used to store future work, while the epic panel organizes epic-related issues. Enable them only if you use them.
The board can have multiple in Progress statuses, from different workflows, mapped to the same column: Yes, this is true. Jira allows mapping different statuses with similar meanings across workflows to the same column for a simplified board view.
The board can include only statuses that are in every workflow: Highly unlikely. Different workflows often have unique statuses specific to their tasks. It's rare for all workflows to share identical statuses.
Therefore, the closest statement to being true is:
The board can have multiple in Progress statuses, from different workflows, mapped to the same column.
However, remember that:
The actual setup depends on your specific configuration. Consider workflow designs, customization choices, and chosen features when deciding on columns and mapping statuses.
Additional information would help for a more tailored answer. If you share details about your workflows and board setup, I can offer a more specific assessment.
Question #4
In Jira Cloud, new issue initiate in the To Do column of your Kanban board. The column has become very full. Additionally, the team is unable to focus on the prioritized issues they should be working on. What configuration adjustment will assist in resolving both issues?
A. Just use card colors to distinguish priorities
B. Just create a quick filter
C. Just add the Priority field to the card layout
D. Just enable the Kanban backlog
The correct answer is:
D. Just enable the Kanban backlog
Explanation:
To address the issues of a full To Do column and help the team focus on
prioritized issues in Jira Cloud, enabling the Kanban backlog would be a
beneficial configuration adjustment.
Here's why:
Enable the Kanban backlog:
The
Kanban backlog provides a separate space to manage and prioritize
issues that are not currently in progress on the main board.
It allows you to move excess issues out of the main board's To Do column, preventing it from becoming overly cluttered.
The team can then focus on the prioritized issues on the main board, while keeping track of other tasks in the backlog.
The other options may have their benefits, but they might not directly address both of the specified issues:
Adding
the Priority field to the card layout: While this provides visibility
into issue priorities, it won't directly address the issue of a full To
Do column or provide a dedicated space for managing the backlog.
Creating
a quick filter: Quick filters are useful for narrowing down the view of
issues on the board, but they may not directly solve the problem of a
full To Do column or provide a separate backlog for managing issues.
Using
card colors to distinguish priorities: While this can visually
highlight the priority of issues, it doesn't directly address the issue
of a full To Do column or provide a dedicated space for managing the
backlog.
In summary, enabling the Kanban backlog is a
comprehensive solution that addresses both the issue of a full To Do
column and assists in focusing on prioritized issues.