Planning Poker is an Agile estimation technique where team members assign relative values, usually in the form of story points, to user stories or tasks based on their complexity and effort required.

The correct option is "1. Bug." A bug issue type is used to track defects or issues found during testing or reported by customers. It is specifically designed to capture information related to the problem, such as steps to reproduce, environment details, and severity. Using the bug issue type ensures that the issue is appropriately categorized and addressed by the development team.

The purpose of a screen in JIRA is to display issue details to users. Screens define the fields that appear when users view or edit an issue, providing them with the necessary information to understand and manage the issue effectively. Screens are associated with issue operations such as create, edit, view, and transition, ensuring that users can interact with issues appropriately based on their context.

When stakeholders express dissatisfaction with the functionality delivered during the Sprint Review meeting, the Scrum Team should acknowledge the feedback and incorporate it into future Sprint planning. This demonstrates responsiveness to stakeholder needs and a commitment to continuous improvement. Ignoring or dismissing feedback can undermine trust and hinder the team's ability to deliver value effectively. Embracing feedback fosters a culture of learning and adaptation within the Scrum framework.

JIRA Automation Rules primarily serve to automate repetitive tasks and workflows within JIRA. They enable users to streamline processes by automatically executing actions based on predefined triggers and conditions. This helps in improving efficiency and reducing manual effort in managing JIRA projects.

Routine system maintenance tasks for a JIRA instance include regular backup to safeguard data integrity, upgrading the software to access new features and security patches, and performance tuning to optimize system responsiveness. These tasks are essential to ensure the stability, security, and efficiency of the JIRA environment, thereby supporting uninterrupted workflow and user satisfaction.

Using Workflow Schemes allows you to associate a workflow with a project. This way, each project can have its own unique workflow while managing multiple projects efficiently.

Kanban boards focus on visualizing and managing flow, allowing teams to control work-in-progress (WIP) limits effectively, making them ideal for projects with varying workloads where priorities might change frequently. Scrum boards, on the other hand, are more structured for time-bound iterations, making them suitable for projects with fixed sprint durations and clearer priorities.

Backlog grooming ensures that backlog items are well-defined by including acceptance criteria, which are specific conditions that must be met for a user story to be considered complete. This clarity aids the development team in understanding and implementing the requirements effectively.

Yes, you can customize the layout and appearance of gadgets on a JIRA Dashboard by rearranging and resizing gadgets according to user preferences. This flexibility allows users to organize the dashboard in a way that best suits their workflow and priorities. However, it's important to note that while users can customize the layout within the constraints of the dashboard layout, extensive customization options such as applying custom CSS styles are typically restricted to JIRA administrators.