The Velocity Chart is the best report to compare work committed and work completed in sprints over time. It shows the average amount of work that a team can complete in a sprint, based on the historical data of previous sprints. It also shows how much work was planned and how much was actually completed in each sprint. By looking at the Velocity Chart, a team can see if they are overestimating or underestimating their capacity, and adjust their planning accordingly. Therefore, option E is correct.Reference:Velocity Chart,Managing Jira Projects Data Center and Server: Certification Bundle

A Control Chart is the best report to provide the information that Darren wants. A Control Chart shows the cycle time or lead time for your team's issues, broken down by the time spent in each status. It helps you identify whether data from the current process can be used to determine future performance. Less time in the Waiting for Support status indicates optimal team performance, as it means that the issues are being addressed promptly and efficiently. A Control Chart also provides a way to dynamically analyze not only specific days but also specific time frames, by using the date range selector and the zoom feature. You can also filter the chart by issue type, assignee, label, or any other field.Reference:Managing Jira Projects Data Center and Server: Certification Bundle, [Control Chart | Jira Software Cloud]

Jon needs Move Issues and Create Issues permissions to move an issue from project A to project B. Move Issues permission allows him to initiate the move operation, while Create Issues permission allows him to create the issue in the destination project. Transition Issues permission is not relevant for moving issues, as it only affects workflow transitions. Administer Projects permission is not required for moving issues, unless the issue type or workflow needs to be changed during the move. Assign Issues permission is not required for moving issues, unless the assignee needs to be changed during the move.Reference:[Moving an issue], [Managing Jira Projects Data Center and Server: Certification Bundle]

One difference between Scrum and Kanban boards is that only Scrum boards support selecting an estimation method. Estimation is a way of measuring how much work is required to complete an issue or a sprint. Scrum boards allow you to choose between story points, original time estimate, or issue count as estimation methods. Kanban boards do not have estimation methods, as they focus on managing the flow of work rather than planning sprints.Reference:Configuring estimation and tracking, Estimating an issue

This JQL query is always correct because it uses theduedatefield, which is a date picker that stores a date value without a time component, and thestartOfDay()function, which returns the start of the current day (i.e., midnight). This query will return all issues that have a due date before today and are assigned to either Adam or Eve. The other queries are either incorrect or unreliable because they use different fields or functions that may not work as expected. For example, theduefield is a date time picker that stores both a date and a time value, and thecurrentLogin()function returns the date and time of the current user's last login, which may vary depending on the user and their timezone.Reference:: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/#Advancedsearchingfieldsreference-DuedateDuedate https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/#Advancedsearchingfunctionsreference-startOfDaystartOfDay