Global automation rules in JIRA apply to all projects within a JIRA instance, allowing administrators to set up automation that spans across the entire system. On the other hand, project-level automation rules are specific to individual projects, giving project administrators control over automation within their projects without affecting others.

Planning Poker is a collaborative technique where team members individually estimate the effort required for a user story, and then discuss their estimates. This helps to improve accuracy by leveraging the collective wisdom of the team and fostering discussions to uncover different perspectives and insights. Daily Stand-ups are more focused on tracking progress and identifying impediments, while the Waterfall Model and Fishbone Diagram are not directly related to Agile estimation practices.

Items in the product backlog are usually prioritized based on the value they bring to the product and the effort required to implement them. Hence, estimating the effort required is a common method for prioritization.

When creating an issue in JIRA, the 'Summary' field is mandatory as it provides a concise description of the issue. This field typically includes a brief overview of the problem or task being addressed by the issue.

Detailed Acceptance Criteria for backlog items provide clear guidelines for the development team on what needs to be achieved. These criteria define the conditions that must be met for a user story or backlog item to be considered complete and ready for delivery. Clear acceptance criteria help prevent misunderstandings and ensure that the development work meets the stakeholders' expectations.

Rules in JIRA Automation enable users to define conditions and actions to automate tasks on issues. These rules can be customized to suit specific requirements, allowing for efficient and consistent handling of repetitive processes. Workflows define the lifecycle of an issue, while triggers initiate actions based on events.

JIRA stands for "Java Integrated Reporting Application." It is a widely-used project management and issue tracking tool. While some people might have humorous interpretations, it officially does not stand for anything.

Backlog grooming meetings, also known as Backlog Refinement meetings, are essential in Agile development. These meetings involve the Product Owner and the development team reviewing and refining the items in the product backlog. The aim is to ensure that the backlog items are well-defined, estimated, and prioritized for upcoming sprints.

Collaborating with the team lead to understand their unique process is crucial in creating a custom workflow that accurately reflects their requirements. This ensures that the workflow effectively supports the team's way of working, leading to improved productivity and efficiency.

Breaking work into small, manageable pieces, typically done within a time-boxed iteration or sprint, is a core practice of Agile methodologies like Scrum, facilitating faster feedback and adaptation.