Your Scrum board has the following filter query:

Your Scrum board has the following filter query:

project in (ENG. DEV) and type in (Bug. Task) ORDER BY Priority ASC

You have the necessary permissions but you are unable to drag an issue into a future sprint in the backlog.

A. Identify the reason.

B. The filter should be in DESC order.

C. Stories are missing from the query.

D. Ranking is disabled.

E. The query should only have one project.

E. The active sprint has not yet been completed.

View Answer

Answer: C

Explanation:

A. Identify the Reason: The filter query you provided is project in (ENG, DEV) and type in (Bug, Task) ORDER BY Priority ASC. This query includes only Bugs and Tasks, and excludes Story issue types. In Scrum methodology, Stories are a primary issue type used for sprint planning. If your board’s filter query does not include Stories, you won’t see them in the backlog, and therefore, you cannot drag them into future sprints.

The other options are not correct because:

B. The filter should be in DESC order: The order of issues (ascending or descending) by priority does not impact the ability to move issues into sprints. It only affects the order in which issues are displayed.

D. Ranking is disabled: There is no indication that ranking is disabled in the scenario described. Ranking issues is a feature that is generally always enabled in Jira boards.

E. The query should only have one project: Having multiple projects in the filter query does not restrict the ability to move issues into sprints. It simply means the board is pulling in issues from multiple projects.

F. The active sprint has not yet been completed: Whether the active sprint is completed or not does not affect the ability to plan future sprints. You can still plan and allocate issues to future sprints regardless of the status of the current sprint.