B. Users can move them to the next sprint.

If another sprint is already planned, the incomplete issues can be moved to that sprint.

E. Users can move them to their backlog.

If there is not a sprint already planned, or if it’s uncertain when the team will work on these issues, they can be moved back to the backlog.

The other options (A. Unresolved issues will be removed, C. Users can move them to the other active sprints, D. Unresolved issues will be archived) do not typically occur in standard usage of Jira’s Scrum boards. Active sprints are typically unique to each Scrum board and not shared among multiple teams, and unresolved issues are not automatically removed or archived when a sprint is completed. The exact behavior may depend on your specific Jira configuration and workflows.

B. By default, any licensed users can create and maintain team-managed projects.

Team-managed projects are designed to be easy to set up and manage, and by default, any licensed user can create one. The user who creates the project becomes the project’s administrator.

C. Users can create multiple team-managed projects and run parallel sprints.

Each team-managed project has its own independent configuration, including sprints. This allows multiple team-managed projects to operate in parallel, each with its own sprints.

E. Users can allow anonymous access to a team-managed project.

Project permissions in team-managed projects are simplified compared to company-managed projects, and include the ability to allow anyone on the internet (anonymous users) to view the project.

Please note, in team-managed projects, settings are unique to each project and can’t be shared with other projects (D). Similarly, there is no facility to create new project roles (F), and the board filters are not limited to standard ones (A). As always, check the most recent Atlassian documentation for the most accurate information.

C. Update the board column.

Jira boards are configured to map each column to one or more statuses. If a status used in either of the two projects’ workflows is not mapped to a column in this board, issues with that status will not appear. Nash can solve this problem by adjusting the column configuration to ensure all statuses used in these projects are mapped to a column.

D. Update the board filter.

While Nash has included both projects in his filter, there might be other criteria in the filter that are excluding the missing issues. Nash should review the filter query to ensure it includes all the necessary criteria to capture all relevant issues from both projects.

Please note, Updating the quick filter (A) would only affect the issues displayed temporarily, it wouldn’t solve the issue of missing tasks. Updating the Jira workflow (B) is a more substantial change that should not be necessary in this case, as the issue is likely with the board’s configuration rather than the workflows of the individual projects.

B. Users can change the view setting to customize their roadmap’s view. The changes will apply to all users that have access to that project.

In fact, the roadmap view settings are user-specific. This means if one user changes their view setting, it will not apply to all users that have access to the project. Each user can customize their own view.

C. Schedule bars for child issues are currently available for scrum teams only.

This is false. Schedule bars for child issues (like stories or tasks under an epic) are not available in the roadmap, regardless of the team type (Scrum or Kanban). The roadmap generally focuses on the epic level.

E. Users can change the epic bar timeline to weeks, months, quarters, or yearly.

This statement is also false. As of my last update, the roadmap view in Jira does not provide options to change the time scale of the roadmap to weeks, months, quarters, or yearly.

Remember to always refer to the most recent Atlassian documentation to confirm whether these capabilities have been added or changed since my last update.

B. Sub-tasks will have a different rank than the parent issues.

Sub-tasks can have their own independent ranking different from their parent issues. This allows sub-tasks to be ordered separately, and it’s not required to follow the ranking of the parent issue.

D. Sub-tasks can be ranked in relation to their sibling issues.

Sub-tasks can indeed be ranked in relation to their sibling issues. This means that sub-tasks within a parent issue can be ordered based on their own priority or importance.

Please note, while the ranking of a parent issue can influence the overall priority of the work, it doesn’t directly determine the ranking of the sub-tasks (A). Similarly, it’s not necessary to rank all of the sub-tasks before ranking the parent issue (C).