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

An epic burndown chart shows the progress towards completing an epic over time. It is useful for tracking how much work is left to be done and predicting when it will be completed. The epic burndown chart is based on the estimation statistic that is configured for the board (either story points or issue count) and shows the total amount of work remaining in the epic at the end of each sprint. You can use this chart to estimate how many additional sprints will be needed to complete an epic.Reference:: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-epic-burndown-chart/

The correct JQL query to find issues reported by either Paul or Tessa that are still unassigned is: Reporter IN (Paul, Tessa) AND Assignee IS EMPTY. This query uses the IN operator to specify a list of values for the Reporter field, and the IS EMPTY operator to check if the Assignee field has no value. The other options are incorrect because they use invalid syntax or operators, such as ''-'', NULL, or Unassigned. For more information on JQL syntax and operators, seeJQL operatorsandUse advanced search with Jira Query Language (JQL).Reference:JQL operators,Use advanced search with Jira Query Language (JQL)

Based on the report shown, which is a Velocity Chart, the only statement that is definitely true about the team's performance is that they sometimes commit more work than they can complete in an iteration. This can be seen by comparing the green bars (completed work) and the gray bars (estimated work) in each sprint. For example, in Sprint 4, the team committed 10 story points but only completed 8 story points. The other statements are not necessarily true based on the report alone. For example, the team may be estimating their work accurately, but facing other challenges or impediments that prevent them from completing their work on time. Or, the team may not be committing unestimated work to an iteration, but rather re-estimating some issues during the sprint. Or, scope change may not be affecting the team's ability to complete work on time, but rather reflecting changes in priorities or requirements. Or, the team may be using sprint duration consistently, but varying the amount of work they commit to each sprint based on their capacity or velocity. For more information on how to interpret and use the Velocity Chart, seeVelocity Chart.Reference:Velocity Chart

The report that can provide an instant progress overview of all fix versions across all projects is the Pie Chart Report. This report allows you to create a pie chart based on any statistic type, such as Fix Version, Project, Issue Type, etc. You can use this report to compare the relative proportions of issues in different fix versions across different projects. For example, you can create a pie chart based on the Fix Version statistic type, and select all the projects that you are responsible for. This will show you how many issues are assigned to each fix version in each project, and what percentage they represent of the total issues. You can also filter the issues by status, priority, assignee, or any other criteria. This report can help you monitor the progress of your releases and identify any potential risks or delays. To generate a Pie Chart Report, follow these steps1:

Navigate to the project that you want to report on.

From the project sidebar, select Reports.

Select Pie Chart Report from the list of reports.

Select the statistic type that you want to base your pie chart on. In this case, select Fix Version.

Select the projects that you want to include in your report. You can select multiple projects by holding down the Ctrl key (Windows) or Command key (Mac) while clicking on the project names.

Optionally, select a filter to narrow down the issues that you want to include in your report. You can use an existing filter or create a new one.

Click View to generate the report.

You can also access the Pie Chart Report from your dashboard by adding the Jira Chart gadget2. This gadget allows you to display any Jira report on your dashboard. To add the Jira Chart gadget to your dashboard, follow these steps2:

Navigate to your dashboard and click Add gadget.

Search for Jira Chart and click Add gadget.

Configure the gadget settings as follows:

Select Pie Chart as the chart type.

Select the project or filter that you want to use as the data source.

Select Fix Version as the statistic type.

Optionally, select a series to further break down the data by another statistic type, such as Status or Priority.

Click Save.

You can also edit or delete the gadget at any time by clicking on the menu icon at the top right corner of the gadget.

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

The correct JQL query to find all issues that were in the Closed status at some point in their lifecycle is: status WAS Closed. This query uses the WAS operator to check the previous values of the status field. The other options are incorrect because they either use invalid syntax, such as CHANGED FROM or -, or they do not capture all the issues that were ever closed, such as status = Closed or status CHANGED TO Open. For more information on JQL syntax and operators, seeAdvanced searching - operators referenceandAdvanced searching - fields reference.Reference:Advanced searching - operators reference,Advanced searching - fields reference

The only field that can definitely be set by all project team members is Labels. Labels are a system field that can be edited by any user who has the Edit Issues permission in the project, regardless of the screen configuration. The other fields may or may not be editable by the project team members, depending on how they are configured in the screen scheme, field configuration scheme, and permission scheme of the project. For example, Attachment requires both the Edit Issues permission and the Create Attachments permission, Assignee requires both the Edit Issues permission and the Assignable User permission, Fix Version/s requires both the Edit Issues permission and the Resolve Issues permission, and Issue Type requires both the Edit Issues permission and a compatible issue type scheme. For more information on how to configure fields in Jira, seeConfiguring fields and screens.Reference:Configuring fields and screens