Getting Started with JIRA - Customizing Scrum Boards

What is the primary function of a filter in a Scrum board?

• To add new issues to the board

• To determine which issues are visible on the board

• To delete completed issues

• To assign tasks to team members

How does a backlog relate to the issues displayed on a Scrum board?

• Backlog issues are automatically marked as completed

• The board displays issues based on the filter, which may include backlog issues

• Backlog issues are never displayed on the board

• Backlog issues are always displayed on the board

Why is it important to save the filter after making changes?

• To ensure changes are applied to the board

• To lock the board from further changes

• To delete all issues

• To reset the board to default settings

What happens when you drag an issue to a different column on the board?

• The issue is deleted

• The issue's status is updated

• The issue is duplicated

• The issue is assigned to a new team member

What can be customized on a Scrum board to better manage issues?

• The number of team members

• The color scheme

• The project budget

• The columns and statuses

What is a key benefit of company-managed projects in JIRA?

• They provide free access to all JIRA features

• They allow for unlimited issue creation

• They enable viewing issues from multiple projects on one board

• They automatically resolve all issues

How does changing the status of an issue on one board affect other boards?

• It changes the status of the issue on all boards where it appears

• It duplicates the issue on other boards

• It deletes the issue from other boards

• It has no effect on other boards