During a sprint a team member discovers an issue that the team member and product owner regard as more important than other sprint features, but it is not blocking sprint completion. What should the project lead ask the team to do?

The correct approach is to follow the sprint plan. In Scrum, a sprint backlog is fixed once the sprint begins to ensure focus and predictability. Introducing new work, even high-priority issues, during an active sprint disrupts this commitment. The issue should be added to the product backlog and prioritized by the Product Owner for a future sprint. Addressing it immediately would violate the sprint commitment and potentially jeopardize the completion of the current sprint's goals. Submitting it to a CCB is not typical for agile projects, which favor more adaptive planning. Avoiding the issue until the next sprint without formal prioritization is also not ideal, as it might delay critical work.