Index
General concepts
Troubleshoot board and filter configurationsWhat is a project schemes?
What is a Jira Filterfield?
What is a board?
What is a dashboard?
Board configurations
Given a scenario, recommend an appropriate board type
Configure boards across multiple teams and projects
Configure board columns to match a workflow process
board filters, sub-filters, and quick filters
Estimation and time tracking on Scrum boards
Swimlanes, card colors, card layout, working days, and issue detail view
Jira custom field?
Jira Screens, field Layouts, cards
Managing projects
Project permissions
Project roles
Versioning and manage releases
Sub-categorize issues
Component and auto assignment
Issue field Layouts
Enrich issues
What is a Jira Project?
| Drawio | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
What is a Jira Filter?
| Drawio | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
What is a board?
| Drawio | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
What is a dashboard?
| Drawio | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
What is a JQL?
JQL Examples
All tasks Jay has been working
| Code Block |
|---|
assignee = Jay |
All tasks Jay is working and still not completed
| Code Block |
|---|
assignee = Jay AND resolution is Empty |
All tasks Jay is working and still not completed or Frank is working and still not completed
| Code Block |
|---|
assignee = Jay AND resolution is Empty or assignee = Frank AND resolution is Empty |
All tasks Jay and Frank are working and still not completed
| Code Block |
|---|
( assignee = Jay or assignee = Frank ) and resolution is Empty |
Board configurations
Given a scenario, recommend an appropriate board type
Scenario 1
A software development team is launching a new mobile application. They plan to work in time-boxed intervals, addressing a prioritized list of features and bugs. They need to commit to specific tasks for each interval and review their progress at the end.
Answer: Scrum Board
A software development team working on a new project often operates in sprints or time-boxed intervals. The Scrum methodology is designed to address prioritized tasks within these intervals. A Scrum board is thus perfect for this setup, allowing the team to plan their sprint by selecting tasks from the backlog, tracking their progress during the sprint, and then reviewing and reflecting at the end of the sprint. It provides structure to iterative development and helps ensure that tasks are completed within the set timeframe.
Scenario 2
The customer support team handles incoming issues and queries from users. The team wants to visualize their workflow, manage the constant flow of tasks, and ensure that no ticket remains unaddressed for too long.
Answer: Kanban Board
Justification: For teams like customer support, work arrives unpredictably and doesn't fit neatly into time-boxed intervals. Instead, the emphasis is on fluidity and ensuring a steady flow of work. A Kanban board offers a visual representation of this workflow, enabling team members to pick tasks based on priority and availability. It's ideal for managing ongoing and variable tasks by visually identifying bottlenecks and ensuring consistent delivery.
Scenario 3
A product management team is collecting ideas and feedback for product enhancements. They want a space to store and prioritize these ideas (backlog) while also having a flow to address and implement the top priorities, transitioning them through different stages until completion.
Answer: Kanban with Backlog:
Justification: The product management team's work involves both collecting ideas (which may not be immediately actionable) and transitioning prioritized ideas through various stages. A Kanban board with a backlog allows the team to maintain a repository of ideas and feedback while also actioning top priorities. The backlog offers a space for ideas to be stored, discussed, and prioritized, while the Kanban board visualizes the progression of these ideas from conception to completion.
Practica examples
Configure boards across multiple teams and projects
Configure board columns to match a workflow process
Board filters, sub-filters, and quick filters
Estimation and time tracking on Scrum boards
Swimlanes, card colors, card layout, working days, and issue detail view