Using specific terms in issue names reduces confusion and ensures clarity in understanding the purpose or nature of the issue being addressed.

The ability to restrict issue transitions based on conditions can be achieved through JIRA Workflows. Workflows in JIRA define the series of steps an issue goes through during its lifecycle and can include conditions to control when transitions between steps are allowed. By configuring workflows effectively, organizations can enforce business rules and streamline their processes. Thus, option 1 is correct.

Velocity is the metric used in Agile to measure the amount of work completed by a team in a fixed time frame, typically a sprint. It helps teams understand their capacity and predictability.

In Kanban, when a task is in the "Done" column, it means that the task is completed and ready for deployment. This signifies that all the necessary work on the task has been finished, and it's now ready to be delivered to the customer or integrated into the product.

You can create a custom field specifically for use on your Agile board by navigating to the JIRA settings and accessing the "Custom Fields" section. From there, you can define the field's name, type, and other properties to tailor it to your board's requirements.

In a JIRA workflow, a "post function" is a feature that performs automated actions after a transition is executed. These actions can include updating fields, sending notifications, or triggering additional transitions, streamlining the workflow process.

JIRA utilizes webhooks to handle real-time updates when integrated with external tools. Webhooks allow external systems to receive real-time notifications from JIRA whenever certain events occur, such as issue creation or status changes. This ensures timely updates and synchronization between JIRA and other tools.

The purpose of JIRA's "Issue Navigator" is to filter and search for specific issues based on various criteria such as project, issue type, status, priority, assignee, and more. It allows users to create complex queries to generate custom reports for advanced reporting needs.

JQL (JIRA Query Language) allows users to create custom queries to find issues based on various criteria, including resolution date. This functionality enables the team member to specify the resolution date range and retrieve the desired issues.

The main difference between Kanban and Scrum boards lies in their approach to workflow management. Kanban boards emphasize continuous delivery, allowing tasks to be pulled as capacity allows, while Scrum boards operate within fixed-length iterations called sprints. This influences how work is planned, executed, and monitored throughout the development process.

Collaboratively re-prioritizing tasks allows the team to focus on completing the most valuable user stories within the Sprint, ensuring that they deliver incremental value to stakeholders. Extending the Sprint duration contradicts the time-boxed nature of Agile Sprints and can lead to other planning issues. Decreasing Sprint quality compromises the integrity of the product and violates Agile principles. Blaming the Product Owner is unproductive and undermines teamwork.

The Definition of Done (DoD) in Agile serves to clearly define when a user story or task is considered complete and ready to be shipped or released. It typically includes criteria such as code review, testing, documentation, and acceptance criteria. Having a well-defined DoD ensures that there is a shared understanding among the team members regarding the completion criteria for each task or user story.